--- title: "Managed Databases – PostgreSQL, MySQL & Valkey | CubePath" description: "Managed PostgreSQL, MySQL and Valkey on one node or three for high availability, with TLS and daily backups. From $20.28/mo per node, billed hourly." language: en source: https://cubepath.com/managed-databases --- # Managed PostgreSQL, MySQL and Valkey Deploy a database from the panel or the API, on one node or three for high availability. Each node runs on its own server, every connection is encrypted, and you pay by the hour for each node. [Deploy a database](https://my.cubepath.com/deploy/managed-database) See plans per node, smallest plan $20.28/mo nodes per database at most 3 locations: Barcelona, Houston, and Miami 3 ## Plans and prices Each plan sets the size of one node, and the price is per node. A database costs the plan's price multiplied by its number of nodes. ### PostgreSQL plans 1 or 3 nodes per database [Deploy PostgreSQL](https://my.cubepath.com/deploy/managed-database) | Plan | vCPU | RAM | Storage | Per hour | Per month | Locations | | ------------------ | ---- | ----- | ------- | -------- | --------- | --------------------------- | | postgresql.micro | 2 | 4 GB | 60 GB | $0.0278 | $20.28 | Barcelona · Houston · Miami | | postgresql.starter | 4 | 8 GB | 80 GB | $0.0521 | $38.02 | Barcelona · Houston · Miami | | postgresql.small | 8 | 16 GB | 160 GB | $0.1007 | $73.51 | Barcelona · Houston · Miami | | postgresql.medium | 12 | 32 GB | 240 GB | $0.1910 | $139.42 | Barcelona · Houston · Miami | | postgresql.pro | 16 | 48 GB | 280 GB | $0.2708 | $197.71 | Barcelona · Houston · Miami | | postgresql.large | 24 | 64 GB | 320 GB | $0.3438 | $250.94 | Barcelona · Houston · Miami | ### MySQL plans 1 or 3 nodes per database [Deploy MySQL](https://my.cubepath.com/deploy/managed-database) | Plan | vCPU | RAM | Storage | Per hour | Per month | Locations | | ------------- | ---- | ----- | ------- | -------- | --------- | --------------------------- | | mysql.micro | 2 | 4 GB | 60 GB | $0.0278 | $20.28 | Barcelona · Houston · Miami | | mysql.starter | 4 | 8 GB | 80 GB | $0.0521 | $38.02 | Barcelona · Houston · Miami | | mysql.small | 8 | 16 GB | 160 GB | $0.1007 | $73.51 | Barcelona · Houston · Miami | | mysql.medium | 12 | 32 GB | 240 GB | $0.1910 | $139.42 | Barcelona · Houston · Miami | | mysql.pro | 16 | 48 GB | 280 GB | $0.2708 | $197.71 | Barcelona · Houston · Miami | | mysql.large | 24 | 64 GB | 320 GB | $0.3438 | $250.94 | Barcelona · Houston · Miami | ### Valkey plans 1 or 3 nodes per database [Deploy Valkey](https://my.cubepath.com/deploy/managed-database) | Plan | vCPU | RAM | Storage | Per hour | Per month | Locations | | -------------- | ---- | ----- | ------- | -------- | --------- | --------------------------- | | valkey.micro | 2 | 4 GB | 60 GB | $0.0278 | $20.28 | Barcelona · Houston · Miami | | valkey.starter | 4 | 8 GB | 80 GB | $0.0521 | $38.02 | Barcelona · Houston · Miami | | valkey.small | 8 | 16 GB | 160 GB | $0.1007 | $73.51 | Barcelona · Houston · Miami | | valkey.medium | 12 | 32 GB | 240 GB | $0.1910 | $139.42 | Barcelona · Houston · Miami | | valkey.pro | 16 | 48 GB | 280 GB | $0.2708 | $197.71 | Barcelona · Houston · Miami | | valkey.large | 24 | 64 GB | 320 GB | $0.3438 | $250.94 | Barcelona · Houston · Miami | Prices in USD, per node. Monthly prices are the hourly price × 730 hours. [View on the pricing page](https://cubepath.com/pricing/managed-databases) ## PostgreSQL, MySQL or Valkey You pick the engine when you deploy. The version stays fixed for the life of the database. PostgreSQL PostgreSQL 17 or 18, with Patroni handling failover on three nodes. Create databases and users from the panel or the API. See plans MySQL MySQL 8.4 or 9.7, both long-term support releases, run as an InnoDB Cluster on one node or three. See plans Valkey Valkey 8.1, an in-memory key-value store that speaks the Redis protocol, for caching, queues and sessions, with Sentinel for failover on three nodes. See plans ## What is included CubePath runs the servers, the network, the replication and the backups. You connect and work with your data. ### One node or three Start on one node, or deploy three for high availability: each node is a server of its own on a different physical host, and the primary fails over automatically. ### Write and read hosts Your application writes through one host that always points to the current primary. With three nodes, a read host answers on the replicas. ### Daily backups Backups are always on: one full backup a day at the hour you pick, kept 1 to 30 days. A restore creates a new database, to the exact second on PostgreSQL and MySQL. ### Encrypted connections Every connection uses TLS with a publicly trusted certificate, so clients need no CA file: sslmode=verify-full on PostgreSQL, rediss:// on Valkey. ### Scale nodes or plan Go from one node to three or back, or move to a bigger plan of the same engine. The disk never shrinks. ### Databases and users Create databases and users from the panel or the API. A new user's password is shown only once. ### Credentials and rotation Host, port, admin user, password and a ready-to-use connection URI. Rotate the admin password from the panel. ### Engine settings Tune a selected set of parameters per engine, such as max\_connections or timeouts. Most apply live; on PostgreSQL, max\_connections needs a brief restart. ### Deletion protection Turn on protection and the database cannot be deleted until you turn it off. ## Step-by-step guide Engines, plans, nodes, scaling and deletion, with screenshots of the panel. [Deploy a Managed Database](https://cubepath.com/docs/products/deployment/deploy-a-managed-database) ## Price a full setup Add databases, servers and the rest of your stack to the calculator and see the monthly total. [Open the calculator](https://cubepath.com/calculator) ## Frequently asked questions ### Which database engines and versions can I deploy? PostgreSQL 17 and 18, MySQL 8.4 and 9.7 (both long-term support releases) and Valkey 8.1\. You pick the version when you deploy and it stays for the life of the database: minor releases and security patches are applied automatically, but there are no in-place major upgrades, so moving to a new major version means deploying a new database and migrating your data to it. ### How do replicas and high availability work? You choose one node, or three for high availability. With three, each node is a separate server on a different physical host, with replication between them (InnoDB Cluster on MySQL, Patroni on PostgreSQL, Sentinel on Valkey), and if the primary fails another node takes over automatically. The write host always points to the current primary, and a read host answers on the replicas. You can move from one node to three, or back, later on. ### Are managed databases backed up? Yes. Backups are always on and cannot be turned off: one full backup a day at the UTC hour you choose, kept from 1 to 30 days (7 by default). PostgreSQL and MySQL also keep their transaction log, so you can restore to the exact second; Valkey restores the last daily backup. A restore always creates a new database and leaves the original as it is. ### How is a managed database billed? By the hour and per node, in USD: the plan's hourly price multiplied by the number of nodes. The monthly prices on this page are the hourly price × 730 hours. Provisioning time is not billed, and billing stops when you delete the database. ### Can I scale a database later? Yes, from the panel or the API, one change at a time: go from one node to three or back, or move to a bigger plan of the same engine. The disk never shrinks, so a plan with less disk than your database is not available. On one node, a plan change restarts the server for a minute or two. The engine, the version and the location stay the same. ### How do I connect to my database? The panel gives you the host, port, admin user, password and a connection URI (postgresql://, mysql://, or rediss:// for Valkey). Every connection is encrypted with TLS and a publicly trusted certificate. There is no SSH access to the nodes. Create a separate user for each application, and rotate the admin password whenever you need to. ### Where do the databases run? In Barcelona, Houston, and Miami. You choose the location when you deploy, and the database stays there: changing the plan later keeps the same location. ### Does Valkey use the Redis protocol? Yes. Valkey speaks the Redis protocol over TLS, so its connection URI is a rediss:// address. Valkey has numbered databases instead of named ones, so on Valkey you create users from the panel, not databases. ## Deploy your first managed database Choose the engine, location, plan and number of nodes in the panel. [Deploy a database](https://my.cubepath.com/deploy/managed-database)