505 Networks
Proxmox

Virtualization without the licensing bill.

Proxmox VE, Backup Server and Mail Gateway — designed, migrated and supported. No per-socket agreements, no mandatory renewal negotiation, no surprise at the end of the quarter.

Why this is happening now

Broadcom repriced VMware, and a lot of businesses are quietly stuck.

Licensing changes since the Broadcom acquisition moved many small and mid-sized organisations from a predictable per-socket cost to multi-year bundles they cannot justify, on hardware they already own. Some renewed anyway. Many are still deciding, and the deadline does the deciding for them.

Proxmox VE is open-source, runs on the hardware you have, and is licensed per support subscription rather than per socket or per core. You can run it entirely free if you want no support contract at all. That is a genuinely different commercial structure from what most virtualisation vendors offer, and it is why the migration work has become continuous rather than occasional.

The honest caveat: Proxmox is not a drop-in clone of every vSphere feature. It is excellent at compute, storage and backup, and it lacks some of the orchestration tooling a large enterprise may already depend on. Part of an assessment is telling you which of those gaps actually affect you — usually fewer than expected, occasionally one that matters.

Proxmox VE

Clusters built to survive a node dying.

Cluster design

Corosync rings, quorum sizing and fencing configured so a failed node is evicted cleanly instead of splitting the cluster's brain.

High availability

HA groups with watchdog timers and fence devices, tested by actually pulling power rather than assuming it works.

Live migration

Move running virtual machines between hosts with no downtime — with shared storage or via local storage migration where it applies.

Storage

ZFS with snapshots and replication, Ceph for shared nothing clusters, LVM-thin, NFS and iSCSI — chosen for your hardware, not for a brochure.

LXC containers

Lightweight containers alongside full VMs, for services that do not need a kernel of their own.

Networking

Bridges, VLAN-aware bridges, bonds and SDN zones, matched to the switching you already run.

Proxmox Backup Server

Backups that deduplicate, encrypt, and get verified.

Proxmox Backup Server does incremental-forever backups with client-side deduplication, which means a twelve-month retention window often costs less space than a month of nightly fulls. Backups are encrypted, and verification jobs run on a schedule so you find out about corruption before you need the restore.

  • Incremental-forever with deduplication and compression
  • Client-side encryption — the backup server cannot read what it stores
  • Scheduled verify jobs, not just scheduled backups
  • Restore tested, documented, and repeated on a calendar
  • Off-site copies to a second site or object storage

Proxmox Mail Gateway

A mail filter that sits in front of whatever you already run.

Proxmox Mail Gateway is an anti-spam and anti-virus gateway that places in front of Postfix, mailcow, Microsoft 365 or Google Workspace. It quarantines, scores, and gives users a digest — which cuts the volume of "was this real?" emails that reach you.

  • Spam scoring, greylisting and reputation rules
  • ClamAV virus scanning with signature updates
  • Per-user quarantine and digest
  • TLS policy and attachment filtering
  • Works in front of mailcow, Exchange or a hosted provider

VMware exit

Move the workloads, keep the uptime.

Migration is a sequence, not a switch. The shape of the work is consistent even when the details are not:

  • Inventory and dependency mapping — what runs, what talks to what, what can move in one window and what cannot
  • Sizing — CPU, memory and storage profiled from actual usage rather than allocated figures
  • Conversion — VMDK to qcow2 or raw, virtio drivers on Windows guests, EFI and Secure Boot handled before boot, not after
  • Parallel running — Proxmox built alongside vSphere, workloads migrated in waves, rollback available at every step
  • Cutover — DNS and dependencies switched in a defined window, with the old environment retained until stability is proven
  • Decommission — licences retired, hardware repurposed or recycled

Small environments move in a weekend. Anything with domain controllers, databases or line-of-business applications gets a staged plan with a rollback path at each stage.

Support & operations

The part most projects skip.

Once it is running, someone still has to patch the hypervisor, review backup job results, replace a failed disk before redundancy is gone, and know what to do at 2am when a node will not rejoin quorum.

  • Subscription and repository management, including the free-no-support path
  • Patching windows with reboot planning
  • Monitoring of node health, storage capacity and replication lag
  • Disk and firmware lifecycle
  • Runbooks and documentation you keep
  • Break-fix support when something is down

Facing a VMware renewal you cannot justify?

Send over the current environment — host count, core count, storage and what the renewal quote looks like — and you will get a straight comparison against a Proxmox build on the same hardware.

Request a comparison