Broadcom's VMware licensing changes are pushing SMBs to look elsewhere
Ballast is a control plane and distributed agent for Hyper-V hosts and failover clusters — a cohesive orchestration layer that does for Hyper-V what vCenter does for vSphere, minus the licensing model that just changed under you.
Community tier is free. No account required to read the docs.
The centre-dependency model works until the centre is the problem. Ballast's agent holds a durable, last-honoured copy of its own desired state and never invents intent — it just keeps enforcing what it was told, whether or not anything is watching.
Declare hosts, storage and a witness, and Ballast coordinates with Windows Failover Clustering to bring the cluster up — no hand-run PowerShell sequence to keep in sync with reality.
A remote-office host or a two-node cluster appears in the same fabric-wide host list as the main datacentre cluster — one table, not a separate console per site.
A VM's replica shows up next to it, not in a separate tool — running/replicating state, target cluster and node, and which replicas have no live relationship and need attention.
A runbook is the order your site comes back in: directory and DNS first, the databases that need them next, then the applications on top — one tier at a time, never forty VMs booting at once.
Capture a powered-off VM as a template — hardware profile, guest customisation and a generalised disk image — and deploy it repeatably anywhere the centre reaches.
Register a VMware source, scan what it holds, and import a VM in a few clicks, with the console naming what needs attention — a raw device mapping, a blocked disk — rather than leaving you to work it out from a failed cmdlet.
Every VM and every host has an interactive console reachable straight from the centre — no client to install, no separate jump box. A host's console is clearly marked as affecting every guest on it, not just one.
Ballast is free to run on a single cluster, with no host limit and nothing held back. Additional clusters are licensed in packs that include vendor support. A deployment keeps the entitlement it was installed under for the life of the release line it was installed on — upgrading within a line never changes what you're entitled to.
Available now
Free
In development
Pricing TBC
Ballast Community includes one failover cluster (any size) plus unlimited standalone hosts. You only need a paid pack when you want to manage a second failover cluster or organisational features like SSO and audit logging.
Ballast is open-core, deliberately: the agent that runs on your hosts is open source and auditable, the centre is ours. Come look at the agent code, file an issue, or join the discussion.