Deploy a Managed Database

Create a fully managed, highly available database from the Deploy Managed Database page in my.cubepath.com. CubePath runs the infrastructure, replication and failover for you.

Note: Your account must be verified before you can deploy.

Deploy

### Pick engine and version
Choose **PostgreSQL**, **MySQL** or **Valkey**. Each engine ships a single pinned version (no in-place major upgrades).

### Name your database
Give it a name (lowercase letters, numbers and dashes), unique within your organization.

### Choose region and plan
Pick a **region**, then a **plan** — prices are per node, so the total scales with the replica count.

### Set replicas
Select the cluster size. PostgreSQL and Valkey start at 1 node; MySQL uses Group Replication and requires a quorum of at least 3 nodes.

### Configure and deploy
Optionally set a **backup schedule** (5-field cron) and retention under Advanced Settings, then click **Deploy Database**.

Important: Provisioning a database cluster can take 30–45 minutes. The connection endpoint and credentials become available once it finishes.

Connect

Open the database and go to the Credentials tab, then click Reveal credentials (each reveal is recorded in the activity log). You'll get the host, port, username, password and a ready-to-use connection URI. Point your application at the URI or the host/port pair — there is no SSH access.

Warning: Anyone with these credentials has full access to your data. Use the Rotate credentials action if they're ever exposed — the old password stops working as soon as the rotation completes.

Manage your database

Open a database to find these tabs:

TabWhat you can do
OverviewEngine, version, plan, replicas, endpoint, location and estimated cost; scale replicas or move to another plan.
ConfigTune engine configuration parameters.
CredentialsReveal the connection string and credentials, or rotate the admin password.
DatabasesCreate and delete logical databases inside the instance (not available for Valkey).
UsersCreate and delete database users with their own passwords.
MetricsConnections, CPU, memory and replication lag graphs over a chosen time range.
ActivityHistory of actions performed on the database.