Solution · Platform

Managed Proxmox clusters in German data centers

In brief

A managed Proxmox cluster is a group of Proxmox VE servers, three as standard, that we build, operate and monitor 24/7 for you. If a node fails, the HA Manager restarts its virtual machines on another node, and Ceph keeps three copies of every block. You handle your application; we handle everything beneath it, from €449.99 net per month.

Scope

What a managed Proxmox cluster includes

A managed Proxmox cluster includes three nodes with quorum as standard, automatic VM restarts through the HA Manager, redundant storage and a redundant network. We handle updates, 24/7 monitoring with on-call duty and backups on separate infrastructure. Renting a Proxmox cluster from us gets you Proxmox cluster hosting in Germany and its operation for one fixed monthly price.

  • Three nodes as standard: quorum via Corosync keeps the cluster able to make decisions after a node fails.
  • Proxmox HA Manager: if a node fails, it automatically restarts the affected virtual machines on an available node.
  • Live migration: virtual machines move to another node while running, for example before we work on a node.
  • Rolling updates: we patch node by node while your systems keep running, critical vulnerabilities first (rolling updates and patch management). Exceptions such as a major database upgrade are announced in advance and scheduled in a window you choose.
  • Redundant storage: the Essentials and Business packages use Ceph clusters for Proxmox with three replicas per block. We use ZFS replication in individually designed, more compact setups.
  • Redundant network: bonding/LACP on every node, separate networks for management, storage and public traffic, firewalling at every layer.
  • Round-the-clock monitoring: 24/7 monitoring and on-call duty with escalation paths, including nights and weekends; after an incident, you receive a post-incident report on cause and corrective actions.
  • Backups outside the cluster: separate backups with restore tests on backup infrastructure separate from the cluster, with defined retention periods. An HA cluster is no substitute for a backup.

Responsibilities

Who does what in a managed Proxmox cluster

With managed Proxmox hosting from us, we are responsible for everything beneath your application: hardware, network, firewall, Proxmox VE and the cluster itself, storage, backup infrastructure, monitoring with on-call duty and platform updates; the operator, Maincubes, provides the building, power and cooling of the data center. You are responsible for your application. The table shows what this split means in day-to-day operations.

Who does what Division of responsibilities in a managed Proxmox cluster
AreaResponsibleWhat it means in operations
HardwareUsServers for the cluster nodes, sized in the design. In the FRA01 data center, failed components are replaced around the clock via remote hands.
Data centerOperatorPrimary site Maincubes FRA01. The operator, Maincubes, provides the building, power, cooling and physical access control; according to the operator, the data center is certified to ISO/IEC 27001 and ISO 9001.
NetworkUsConnectivity via AS47263 with our own BGP routing, redundant core routers, switches and uplinks, network-level DDoS protection.
Firewall and load balancerUsRedundant firewall and load balancer layer with health checks and a floating IP.
Proxmox VE and clusterUsSetup and configuration, quorum via Corosync, HA Manager and live migration.
StorageUsCeph with three replicas per block on different nodes, a dedicated storage network, disk replacement documented in a post-incident report.
Backup infrastructureUsSeparate backup systems with defined retention periods; every backup is checked and restore tests run regularly.
Monitoring and on-call dutyUsHardware, virtualization, services and network monitored around the clock. Critical alerts reach on-call duty immediately.
Platform updatesUsSecurity patches for the platform's operating system, virtualization and services, applied node by node.
Your applicationYouYou look after your application. Our monitoring uses health checks from the user's perspective to verify that it responds.

You have a dedicated contact who knows your cluster.

Architecture

Reference architecture: a three-node Proxmox HA cluster

Our managed Proxmox clusters consist of three layers, each built redundantly: a firewall and load balancer layer with health checks, three Proxmox VE nodes that form a quorum via Corosync, and Ceph storage that spreads every data block across three nodes. Management, storage and public traffic run on separate networks.

Diagram 02 Access, nodes, storage
  • Traffic
  • Cluster network (Corosync)
  • Ceph replication
  • external
  • Node active
Diagram as text
  1. Requests from the internet reach the cluster via our network, AS47263.
  2. The redundant firewall and load balancer layer with a floating IP distributes requests to nodes 1, 2 and 3 based on health checks.
  3. The three nodes run Proxmox VE with KVM and are connected via Corosync. If one node fails, the remaining two keep quorum.
  4. The nodes store their data in Ceph; every data block exists as three replicas on different nodes.
  5. Management, storage and public traffic run on separate networks (VLANs).
If a node fails, the Proxmox HA Manager automatically restarts the affected virtual machines on another node. Services running on several nodes behind the load balancer remain available.

The load balancer removes a failed node from rotation within seconds. The node's virtual machines restart on another node after fencing; how long that takes depends on fencing and on the guest system's boot time. How we deliver high availability by design at every layer is covered on our high availability cluster page.

If a disk or an entire node fails, no data is lost: Ceph keeps every block in three copies on different nodes and restores the target redundancy on its own as soon as enough disks and nodes are available for it. Recovery increases I/O load; with several simultaneous failures, some data may be temporarily unavailable until recovery completes.

Proxmox in production

Managed Proxmox VE in production: licensing, support, quorum

Proxmox VE is an open-source virtualization platform based on Debian GNU/Linux, with KVM for virtual machines and LXC for containers. The software can be used without a license fee; the vendor offers support and the enterprise repository through optional subscriptions. The sections below explain what that means for cost, support and your independence.

Licensing and vendor support

According to Proxmox, the Proxmox VE source code is released under the GNU Affero General Public License, version 3. According to the vendor, subscription tiers differ only in support; high availability, live migration, clustering, backup and software-defined storage are available at every tier.

An open platform, your documentation

Documentation of the architecture, access details and emergency plans belongs to you, and the platform is built on Proxmox VE, KVM and Ceph. If you run VMware today, Proxmox and VMware compared sets out licensing and operations side by side.

Why three nodes

Only with three nodes does a majority remain after one node fails, so the cluster keeps quorum and can still make decisions; two nodes need an external quorum device for that. For business-critical applications we therefore recommend three or more nodes, and our guide explains why a cluster needs three nodes.

Sources

  1. Proxmox Server Solutions GmbH: Proxmox VE Administration Guide, chapter “Introduction”. pve.proxmox.com, retrieved October 9, 2026.
  2. Proxmox Server Solutions GmbH: Proxmox VE subscriptions. proxmox.com, retrieved October 9, 2026.

Proxmox VE licensing

Proxmox VE is open-source software and can be used without a license fee. The vendor offers optional subscriptions with access to the enterprise repository and vendor support, priced per CPU socket (source: proxmox.com, as of October 2026).

Existing clusters

Taking over existing Proxmox clusters

Already running a Proxmox cluster and looking for a provider to operate it? After an audit, we connect your cluster to our monitoring and take over operations, updates and on-call duty. Whether you then have it rebuilt step by step toward the target architecture is your decision.

  1. 1

    Audit

    Before taking over, we review your existing Proxmox cluster in an audit.

  2. 2

    Connection to our monitoring

    From then on, we monitor your cluster's hardware, virtualization, services and network around the clock.

  3. 3

    Operations, updates, on-call duty

    We apply updates, respond to alerts around the clock and report monthly on availability, incidents and utilization.

  4. 4

    Rebuild toward the target architecture

    On request, we rebuild the cluster step by step toward the target architecture, for example three nodes with quorum and Ceph storage.

Migration

Bringing VMs over from KVM and VMware environments

Virtual machines from KVM-based environments move to the Proxmox cluster directly. We convert VMware systems as part of the migration, including disk formats and VM configuration. Your existing environment stays untouched and ready to run until the cutover has succeeded, and you decide when the switchover happens.

Leaving VMware

From VMware to Proxmox VE

Analysis, sizing, a parallel build next to your existing environment, testing and a cutover with a rollback plan. After that, we take over managed operations.

Migrating from VMware

Price

Getting started with the Essentials package

Managed Proxmox clusters start with the Essentials package at €449.99 net per month. Besides the services listed on the package card, the fixed price also covers on-call duty and a dedicated contact.

The published prices apply to the Essentials and Business packages. We discuss the hardware of the cluster nodes (CPU, RAM, storage, network) individually and define it in the design proposal. We price Enterprise environments by data volume, recovery point objective (RPO) and switchover time and state the fixed price in the proposal.

Compare managed Proxmox cluster pricing

Essentials · Ceph HA

€449.99 / month, net

Your entry point to high availability: three nodes with Ceph, fully managed.

  • 3 nodes with quorum
  • Ceph HA storage: three-way replication, self-healing
  • 24/7 monitoring and alerting
  • Fully managed, including updates
  • Network-level DDoS protection
Request Essentials

All prices are net, plus VAT. As of .

FAQ

Managed Proxmox cluster FAQ

How does a Proxmox HA cluster work?

Through quorum, fencing and automatic restarts of virtual machines. Corosync connects the nodes; as long as a majority of them can reach each other, the cluster can make decisions. If a node fails, it is isolated (fencing) so that no virtual machine runs twice. The Proxmox HA Manager then restarts the affected VMs on another node; services running on several nodes behind the load balancer remain available. Our high availability page walks through the failover step by step.

Can you take over our existing Proxmox cluster?

Yes. After an audit, we connect your cluster to our monitoring and take over operations, updates and on-call duty. On request, we then rebuild it step by step toward the target architecture, for example three nodes with Ceph storage.

Can VMs be moved over from other environments?

Yes. VMs from KVM-based environments move over directly; we convert VMware systems from ESXi to KVM as part of the migration. Special cases such as appliances tied to specific hardware are clarified during the analysis. The process is described under migrating from VMware to Proxmox.

Which storage options does a Proxmox cluster offer?

Ceph and ZFS replication. The Essentials and Business packages use Ceph, which synchronously keeps three replicas of every block on different nodes. We use ZFS replication in individually designed, more compact setups; it replicates at intervals. For a decision aid, see Ceph or ZFS compared.

How many nodes does a Proxmox cluster need?

Three or more for business-critical applications, because only then does the cluster keep its majority after a node fails. Our guide to split brain, quorum and fencing explains why two nodes need an external quorum device.

How much does a managed Proxmox cluster cost?

From €449.99 net per month for the Essentials package with three nodes and Ceph storage. Our pricing overview compares all packages and services.

Next step

Which cluster size fits your workload?

Tell us about your application, load profile and availability target. You will receive a written design with an architecture diagram, a component list and a fixed price for setup and operations.

Discuss cluster sizing

Further reading