ClusterControl’s point-and-click interface lets you flexibly scale your cluster via node actions, load balancers, and containers in any environment. Whether for resilience or scaling out for read-only alternatives, ClusterControl offers you everything you need for all your favorite databases.

Learn how to increase and decrease database resources and extend into the cloud as your application needs evolve.


We know polyglot environments

With support for 9 databases, including MongoDB and Elasticsearch, ClusterControl can handle anything.

Right-size your cluster

Avoid over-provisioning; you can shape your cluster to your evolving needs by adding and removing nodes.

Bring your load balancers

ClusterControl manages load balancers such as HAProxy, ProxySQL, and Maxscale at will.

Full-lifecycle operations for the most advanced databases

Bring clusters under ClusterControl’s “control” for completeness via the import process. “Cluster” is any replication environment or cluster using the most popular open-source solutions.

Seamless database scalability

Adding nodes to an existing cluster has always presented challenges that make the DBA team wary. ClusterControl automates all the tasks and actions, so you don’t have to worry about them. But that also includes removing nodes to re-assign resources to other environments.

See for yourself, demo scaling live!

Top rated Docs

Node actions documentation

ClusterControl nodes documentation

Cluster action docs

Top rated Blogs

Replicating MongoDB Across a Hybrid Cloud Environment

Challenges of Scaling the Moodle PostgreSQL Database

Scaling PostgreSQL Using Connection Poolers & Load Balancers

I don’t know what scalability my environment might need for now. Can I scale out when I need it with ClusterControl?

Add nodes as you see fit to whichever environment demands it. The database technology deployed and environment size will determine how fast that task takes.

Can I scale out and then scale back down again in an elastic fashion like DBaaS and cloud providers?

This mainly depends on the database vendor, but ClusterControl lets you add nodes and remove nodes accordingly, so you don’t have to read manuals and contemplate the details required.

Does scaling mean taking copies from the primary cluster or node, or can I do it from backups? Can I make changes while adding new nodes?

You’ll be offered a choice when adding a new node about how you want to provision the node, and one of those will be to choose from the list of backups available so you don’t impact the online activity on the other nodes.

6 easy steps to get started with ClusterControl