Managed PostgreSQL configurations
Managed Databases for PostgreSQL® are configured from four components that you select separately:
- Compute: the CPU cores and memory of each node.
- Storage: the disk space for your data.
- Nodes: a single node, or a cluster of 2 or 3 nodes.
- Backups: how long backups are retained.
Database services are billed hourly according to the selected configuration until the service is deleted, including while it is stopped. See the pricing page for hourly and monthly costs.
Compute
Compute plans come in three families:
- Developer: single-node compute for development, testing, and small workloads.
- Standard: balanced CPU and memory for most production workloads.
- High Memory: extra memory per core for caching and memory-intensive workloads.
The storage column shows the range of storage you can select with each compute plan.
Developer
| CPU cores | Memory | Storage | Identifier |
|---|---|---|---|
| 1 | 1 GiB | 10–50 GiB | rdb.development.1CPU-1GB |
| 1 | 2 GiB | 10–400 GiB | rdb.development.1CPU-2GB |
| 1 | 4 GiB | 10–2,500 GiB | rdb.development.1CPU-4GB |
Each account can have up to 5 database services on 1 CPU and 1 GiB plans. This covers rdb.development.1CPU-1GB and the legacy 1x1xCPU-1GB-10GB plan, and the limit is shared with Managed MySQL and Managed Valkey. To raise the limit, contact support.
Standard
| CPU cores | Memory | Storage | Identifier |
|---|---|---|---|
| 2 | 8 GiB | 10–2,500 GiB | rdb.standard.2CPU-8GB |
| 4 | 16 GiB | 10–7,168 GiB | rdb.standard.4CPU-16GB |
| 8 | 32 GiB | 80–7,168 GiB | rdb.standard.8CPU-32GB |
| 12 | 48 GiB | 80–7,168 GiB | rdb.standard.12CPU-48GB |
| 16 | 64 GiB | 80–7,168 GiB | rdb.standard.16CPU-64GB |
| 24 | 96 GiB | 80–7,168 GiB | rdb.standard.24CPU-96GB |
| 32 | 128 GiB | 80–7,168 GiB | rdb.standard.32CPU-128GB |
| 48 | 192 GiB | 500–7,168 GiB | rdb.standard.48CPU-192GB |
| 64 | 256 GiB | 500–7,168 GiB | rdb.standard.64CPU-256GB |
| 80 | 320 GiB | 500–7,168 GiB | rdb.standard.80CPU-320GB |
High Memory
| CPU cores | Memory | Storage | Identifier |
|---|---|---|---|
| 2 | 16 GiB | 10–2,500 GiB | rdb.memory.2CPU-16GB |
| 4 | 32 GiB | 80–7,168 GiB | rdb.memory.4CPU-32GB |
| 8 | 64 GiB | 80–7,168 GiB | rdb.memory.8CPU-64GB |
| 12 | 96 GiB | 80–7,168 GiB | rdb.memory.12CPU-96GB |
| 16 | 128 GiB | 80–7,168 GiB | rdb.memory.16CPU-128GB |
| 24 | 192 GiB | 500–7,168 GiB | rdb.memory.24CPU-192GB |
| 32 | 256 GiB | 500–7,168 GiB | rdb.memory.32CPU-256GB |
| 48 | 384 GiB | 500–7,168 GiB | rdb.memory.48CPU-384GB |
| 64 | 512 GiB | 500–7,168 GiB | rdb.memory.64CPU-512GB |
Storage
The storage size you select applies to each node. For example, a 2-node cluster with 100 GiB of storage has 100 GiB on each node. The available storage range depends on the compute plan, as shown in the compute tables above, up to a maximum of 7,168 GiB.
Nodes
Developer compute plans run on a single node. Standard and High Memory compute plans can run on 1, 2, or 3 nodes. A cluster of 2 or 3 nodes has a primary node and standby nodes that take over automatically if the primary fails. See high availability for details.
Backups
| Backup tier | Retention | Available with |
|---|---|---|
| Mini | 3 days | Developer |
| Regular | 15 days | Standard, High Memory |
| Extended | 31 days | Standard, High Memory |
Extended retention has an additional monthly cost. See backups for how backups work.
Creating a database with the API
When you create a database with the UpCloud API, select the components with the plan_compute, plan_storage_gib, plan_node_count, and plan_backups fields. The list database plans endpoint returns the available compute plans and the storage and backup options for each.
Legacy plans
Legacy plans bundle CPU cores, memory, storage, and backups into fixed configurations. They remain available. To select one in the Control Panel, click Use legacy plans in the Compute section when creating a database.
Legacy 1-node plans
| Memory | CPU cores | Storage | Backups | Identifier |
|---|---|---|---|---|
| 1 GB | 1 | 10 GB | 3 days | 1x1xCPU-1GB-10GB |
| 2 GB | 1 | 25 GB | 3 days | 1x1xCPU-2GB-25GB |
| 4 GB | 2 | 50 GB | 3 days | 1x2xCPU-4GB-50GB |
| 4 GB | 2 | 100 GB | 3 days | 1x2xCPU-4GB-100GB |
The 1x1xCPU-1GB-10GB plan counts toward the per-account limit for 1 CPU and 1 GiB plans.
Legacy 2-node plans
| Memory | CPU cores | Storage | Backups | Identifier |
|---|---|---|---|---|
| 4 GB | 2 | 50 GB | 15 days | 2x2xCPU-4GB-50GB |
| 4 GB | 2 | 100 GB | 15 days | 2x2xCPU-4GB-100GB |
| 8 GB | 4 | 50 GB | 15 days | 2x4xCPU-8GB-50GB |
| 8 GB | 4 | 100 GB | 15 days | 2x4xCPU-8GB-100GB |
| 16 GB | 6 | 100 GB | 15 days | 2x6xCPU-16GB-100GB |
| 16 GB | 6 | 250 GB | 15 days | 2x6xCPU-16GB-250GB |
| 32 GB | 8 | 100 GB | 15 days | 2x8xCPU-32GB-100GB |
| 32 GB | 8 | 250 GB | 15 days | 2x8xCPU-32GB-250GB |
| 32 GB | 8 | 500 GB | 15 days | 2x8xCPU-32GB-500GB |
| 64 GB | 16 | 1 TB | 15 days | 2x16xCPU-64GB-1000GB |
| 64 GB | 16 | 1.5 TB | 15 days | 2x16xCPU-64GB-1500GB |
| 128 GB | 20 | 2 TB | 15 days | 2x20xCPU-128GB-2000GB |
Legacy 3-node plans
| Memory | CPU cores | Storage | Backups | Identifier |
|---|---|---|---|---|
| 4 GB | 2 | 100 GB | 31 days | 3x2xCPU-4GB-100GB |
| 4 GB | 2 | 200 GB | 31 days | 3x2xCPU-4GB-200GB |
| 8 GB | 4 | 100 GB | 31 days | 3x4xCPU-8GB-100GB |
| 8 GB | 4 | 200 GB | 31 days | 3x4xCPU-8GB-200GB |
| 16 GB | 6 | 200 GB | 31 days | 3x6xCPU-16GB-200GB |
| 16 GB | 6 | 500 GB | 31 days | 3x6xCPU-16GB-500GB |
| 32 GB | 8 | 200 GB | 31 days | 3x8xCPU-32GB-200GB |
| 32 GB | 8 | 500 GB | 31 days | 3x8xCPU-32GB-500GB |
| 32 GB | 8 | 1 TB | 31 days | 3x8xCPU-32GB-1000GB |
| 64 GB | 16 | 1 TB | 31 days | 3x16xCPU-64GB-1000GB |
| 64 GB | 16 | 2 TB | 31 days | 3x16xCPU-64GB-2000GB |
| 128 GB | 20 | 2 TB | 31 days | 3x20xCPU-128GB-2000GB |
PostgreSQL is a registered trademark of the PostgreSQL Community Association of Canada, and used with their permission.