Which platform is right for you?
We answer it with your workloads and a five-year cost comparison, then deploy it and move you over.
Which platform fits your workloads
We inventory the workloads, shortlist two platforms that meet the requirements, and run both in our lab against your data before recommending one.
- 1Workload inventoryEvery VM, share, backup job and camera stream, with measured CPU, memory and IOPS rather than the numbers they were sized for.
- 2RequirementsAvailability targets, recovery time and point objectives, licensing constraints, budget, and who operates it day to day.
- 3Shortlist twoTwo platforms that meet the requirements, with the trade-offs documented.
- 4Lab validationBoth built in our lab with copies of your workloads. We pull a host, restore from backup and run an upgrade, and time each.
- 5Written recommendationOne platform, a bill of materials and a migration plan, in writing.
The shortlist shown is one outcome. Yours comes from the inventory.
Hardware, new or secondhand, compared on five-year cost
We do not resell hardware. We write the spec, price each option over five years including the renewal you would otherwise sign, and introduce you to the partners we buy from. You purchase direct; we take no margin.
New
Current-generation nodes on the platform’s hardware compatibility list, with manufacturer warranty. Required where the support contract or an audit depends on it.
We introduce an authorized resellerSecondhand
Off-lease servers and drives, burned in and warranted by the partner, at a fraction of list price.
We introduce a refurbisherExample proportions, not a quote. Yours is built from the inventory and partner pricing.
Build the new cluster, then move the workloads in waves
Shown: VMware to Nutanix. The target cluster is built and tested first. VMs move in waves inside scheduled windows using Nutanix Move, and vSphere stays live until every VM is verified on AHV. The same plan runs VMware to Proxmox, Hyper-V to Proxmox and Synology to TrueNAS.
Today · 16 VMsTarget · AHVWeeks are illustrative; the real plan comes out of the inventory.
Hardware and platform, designed together
Most virtualization problems are design conflicts between layers that were bought separately. We treat compute, storage, networking and configuration as one architecture.
Hardware
- Server selection and sizing
- CPU and memory planning
- Storage architecture
- Network design for virtualization
- Redundancy strategy
- Cluster node planning
- Hardware compatibility review
- Lifecycle and refresh planning
Hardware decisions set the ceiling on performance, resiliency and how maintainable the environment is in year four.
Software
- Cluster architecture
- Host configuration standards
- Storage configuration
- Virtual switch and network design
- Workload placement strategy
- HA and resiliency settings
- Performance tuning
- Operational standards and documentation
Configuration should match the infrastructure underneath it and the workload profile on top of it. Rarely does it match either by default.
What we do on each platform
Where each one fits, what it costs relative to the others, and the trade-offs we would raise before you buy.
- Clusters of any size where licensing has to stay near zero
- Ceph for distributed storage, or ZFS per node
- Integrated backup to Proxmox Backup Server
- Direct import of VMs from ESXi
- Support is a subscription from Proxmox, not a vendor field team
- HA works well; upgrades are less automated than Nutanix
- Fewer third-party integrations than vSphere
Free to run. Support subscription priced per CPU socket.
Talk to an engineer about your cluster.
A short call to see whether we are the right fit for the design or the migration.