1. Home
  2. Docs
  3. CCX
  4. Getting Started

Getting Started

CCX is a cloud-based automation tool for open-source database clusters. It acts as your virtual DBA that works 24x7x365 to ensure your clusters are always available, secure, operating at optimal performance, with backup and restore management to safeguard your data.

CCX can deploy, manage, and monitor the following open-source database cluster technology:

RDBMS Vendor/Supported Version Clustering Technology
 MySQL/MariaDB  Percona

  • Percona Server for replication
  • Percona XtraDB Cluster for multi-master
  • version 8.0
 Percona XtraDB Cluster + ProxySQL

  • version 10.6
 MariaDB Galera Cluster + ProxySQL
 PostgreSQL  PostgreSQL

  • versions 11, 14, 15
 PostgreSQL + HAProxy
 Redis  Redis

  • version 7
 Redis Sentinel
Microsoft SQL Server Microsoft SQL Server

  • Single Instance
  • Always On
  • version 2019, 2022
Microsoft SQL Server

To get started with CCX, you need to:

  1. Create an account with your email address here.
  2. You will be redirected to the billing information page to attach at least one credit card. You won’t be charged until you have a successful deployment of a data store. For EU countries, you may specify the EU VAT ID for the reverse charge rule.
  3. If you want to deploy on a private network (without public IP addresses), create a VPC first of your selected region.
  4. Create a data store. See Deployment.
  5. For private network deployment, you need to create a VPC peering to connect from your application to the database cluster. See VPC and Peering.
  6. Create access controls via firewall rules and trusted sources. See Trusted Source.
  7. Connect to the database cluster via the load balancer endpoints or directly to the server and start using your database.

CCX offers you a pay-as-you-go approach for pricing and you pay only for the individual services you need, for as long as you use them, and without requiring long-term contracts or complex licensing. You only pay for the services you consume, and once you stop using them, there are no additional costs or termination fees.

A deployed cluster is charged hourly, depending on the selected provider, region, cluster size, instance size, and any additional customization to the database instances like disk size, custom IOPS and availability zone. For more details, see CCX DBaaS Pricing Plans.


CCX supports two types of deployment environments for your database technology:

  • Development
  • Production

For development, a single node will be deployed with no redundancy which is recommended for development and testing. Every database instance comes with an accompanying load balancer that resides on the same host so you can test out database connections to the database or load balancer tier.

For production, CCX will deploy a fault-tolerant setup with a minimum of 3 nodes which is a recommended basic production setup. Similar to the development environment, every database instance comes with an accompanying load balancer. For instance, a 3-node MariaDB Cluster will also include a 3-node ProxySQL with native clustering enabled.

Cloud Providers

At the moment, the following cloud providers and regions are supported for both development and production environments:

Cloud Provider Continental Region
AWS US us-east-1 (North Virginia)
us-west-1 (North California)
Europe eu-north-1 (Stockholm)
eu-west-3 (Paris)
eu-west-2 (London)
eu-west-1 (Ireland/Dublin)
eu-central-1 (Frankfurt)
Asia Pacific ap-south-1 (Mumbai)
South America sa-east-1 (São Paulo)
Safespring Europe se-east-1 (Stockholm)
OpenStack All All

Instance Size

At the moment, CCX offers the following instance sizes:

Instance Size CPU Cores RAM (GB)
Tiny 2 4
Small 2 8
Medium 4 16
Large 8 32
X-Large 16 64
2X-Large 32 128
  • For instances X-Large and 2X-Large, this is disabled by default. To increase your account limits, you have to contact our Sales.
  • The instance size name for CCX does not correlate with the instance size offered by the selected cloud provider. For example, the CCX’s small instance is not equal to AWS’s small instance.



The instance size availability is subject to the selected region.


In CCX terms, Virtual Private Cloud, or VPC, is an isolated virtual network for your resources in the cloud service provider (CSP). For private network deployment, CCX will always deploy a data store in a VPC, regardless of the deployment environment chosen. Thus, the instances will have no public IP address assigned and VPC peering is necessary to connect the applications to the CCX data store. For example on how to peer the internal networks, see VPC and Peering.

For public network deployment, VPC is not compulsory.



The network type cannot be changed after deployment.

Was this article helpful to you? Yes No