ClusterControl Hosting on Your Own VPS
Deploy, monitor and fail over database clusters from one interface.
Size a server for ClusterControl
Every stop is a real configuration you can deploy. Priced per 30 days, billed by the hour, exclusive of 18% GST.
What ClusterControl is
ClusterControl manages database clusters. It deploys MySQL, MariaDB, PostgreSQL, MongoDB and Redis topologies, monitors them, schedules backups, and handles failover and recovery — the operational work that otherwise lives in a pile of scripts and tribal knowledge.
It is worth being clear about the architecture, because it is unusual among the tools on this page. ClusterControl runs on its own server and manages database nodes over SSH; it is a controller, not a database host. So a ClusterControl VPS is a control-plane machine, and the databases themselves live on other servers it reaches.
That means the sizing question is different too. The controller needs enough memory for its own database of metrics and enough disk for backup staging if backups pass through it — but the heavy resources belong on the nodes it manages, not on this one.
Why run ClusterControl on a VPS
Root on the controller and on the nodes, which ClusterControl needs to manage them.
Private networking between controller and database nodes, so replication traffic is not on the public internet.
Size the controller and the data nodes independently.
Snapshots on every machine in the topology, not just the primary.
ClusterControl features
Deployment of MySQL, MariaDB, PostgreSQL, MongoDB and Redis topologies
Replication and cluster monitoring with alerting
Automated failover and recovery
Scheduled backups with verification
Query and performance analysis
Configuration management across nodes
Topology visualisation
Recommended server
A starting point for ClusterControl, not a hard floor — size it on the sliders.
| Memory | 4 GB for the controller; 8 GB if it manages many nodes |
|---|---|
| CPU | 2 vCPU for the controller |
| Storage | 80 GB if backups stage through the controller, otherwise 40 GB |
| Operating system | Ubuntu 22.04 LTS, Debian 12 or AlmaLinux 9 |
How deployment works
ClusterControl is installed on a dedicated VPS acting as the controller, with SSH keys distributed to the database nodes it will manage. Those nodes are separate servers. Put the controller and the nodes on the same private network so replication and monitoring traffic stays off the public internet.
What people run it for
Running replication properly
Primary and replicas with monitored lag and tested failover, rather than a hopeful setup.
Backup you have verified
Scheduled backups with restore verification, which is the half people skip.
Managing several clusters
One controller across multiple database estates.
Reducing on-call load
Automated recovery for the failures that would otherwise page someone.
ClusterControl hosting questions
Related applications
Redis Hosting In-memory cache, sessions and queues, priced as memory rather than per gigabyte. 
Elasticsearch Hosting Full-text search and log analytics, with heap and retention under your control. 
Portainer Hosting A web interface for Docker — containers, images, volumes and networks, without living in the CLI. 
aaPanel Hosting A free web control panel for managing sites, databases and certificates on your own server. 
FastPanel Hosting A free control panel with per-site users, multi-PHP and one-click certificates. Deploy ClusterControl on your own server
Root access, your choice of size, and no container between you and the application.