PlanetScale SKUs
Here you'll find a complete list of all the database sizes available to you on PlanetScale. If your needs exceed what is available here, we also support sharding.
Network-attached storage
Network-attached storage databases come with autoscaling storage and have varying levels of compute power.
| Processor | Memory | Transactions* | |
|---|---|---|---|
| PS-10 | 1/8 vCPU | 1 GB RAM | 70 |
| PS-20 | 1/4 vCPU | 2 GB RAM | 75 |
| PS-40 | 1/2 vCPU | 4 GB RAM | 75 |
| PS-80 | 1 vCPU | 8 GB RAM | 110 |
| PS-160 | 2 vCPUs | 16 GB RAM | 158 |
| PS-320 | 4 vCPUs | 32 GB RAM | 211 |
| PS-400 | 8 vCPUs | 32 GB RAM | 211 |
| PS-640 | 8 vCPUs | 64 GB RAM | 281 |
| PS-700 | 16 vCPUs | 32 GB RAM | 211 |
| PS-900 | 16 vCPUs | 64 GB RAM | 281 |
| PS-1280 | 16 vCPUs | 128 GB RAM | 375 |
| PS-1400 | 32 vCPUs | 64 GB RAM | 281 |
| PS-1800 | 32 vCPUs | 128 GB RAM | 375 |
| PS-2100 | 48 vCPUs | 96 GB RAM | 328 |
| PS-2560 | 32 vCPUs | 256 GB RAM | 500 |
| PS-2700 | 48 vCPUs | 128 GB RAM | 438 |
| PS-2800 | 64 vCPUs | 128 GB RAM | 375 |
* Transactions refers to the number of simultaneous transactions your database can process, which is different than simultaneous connections. This is also known as the transaction pool.
Metal
Metal databases are backed by locally-attached NVMe drives for storage, unlocking incredible performance and cost-efficiencies. Because the drives are locally-attached, you need to choose both your compute and storage resources when you create your database. The storage options vary by cloud provided, so we break out the options into AWS and GCP sections.
Metal options on AWS
| Processor | Memory | NVMe Storage options | Transactions* | |
|---|---|---|---|---|
| M-160 | 2 vCPUs | 16 GB RAM | 110 GB | 158 |
| M-160 | 2 vCPUs | 16 GB RAM | 460 GB | 158 |
| M-160 | 2 vCPUs | 16 GB RAM | 1,241 GB | 158 |
| M-320 | 4 vCPUs | 32 GB RAM | 229 GB | 211 |
| M-320 | 4 vCPUs | 32 GB RAM | 929 GB | 211 |
| M-320 | 4 vCPUs | 32 GB RAM | 2,490 GB | 211 |
| M-640 | 8 vCPUs | 64 GB RAM | 466 GB | 281 |
| M-640 | 8 vCPUs | 64 GB RAM | 1,866 GB | 281 |
| M-640 | 8 vCPUs | 64 GB RAM | 4,992 GB | 281 |
| M-1280 | 16 vCPUs | 128 GB RAM | 942 GB | 375 |
| M-1280 | 16 vCPUs | 128 GB RAM | 3,739 GB | 375 |
| M-2560 | 32 vCPUs | 256 GB RAM | 1,891 GB | 500 |
| M-2560 | 32 vCPUs | 256 GB RAM | 7,492 GB | 500 |
Metal options on GCP
| Processor | Memory | NVMe Storage options | Transactions* | |
|---|---|---|---|---|
| M-160 | 2 vCPUs | 16 GB RAM | 367 GB | 158 |
| M-160 | 2 vCPUs | 16 GB RAM | 742 GB | 158 |
| M-160 | 2 vCPUs | 16 GB RAM | 1,492 GB | 158 |
| M-160 | 2 vCPUs | 16 GB RAM | 2,992 GB | 158 |
| M-160 | 2 vCPUs | 16 GB RAM | 5,992 GB | 158 |
| M-160 | 2 vCPUs | 16 GB RAM | 8,992 GB | 158 |
| M-320 | 4 vCPUs | 32 GB RAM | 367 GB | 211 |
| M-320 | 4 vCPUs | 32 GB RAM | 742 GB | 211 |
| M-320 | 4 vCPUs | 32 GB RAM | 1,492 GB | 211 |
| M-320 | 4 vCPUs | 32 GB RAM | 2,992 GB | 211 |
| M-320 | 4 vCPUs | 32 GB RAM | 5,992 GB | 211 |
| M-320 | 4 vCPUs | 32 GB RAM | 8,992 GB | 211 |
| M-640 | 8 vCPUs | 64 GB RAM | 367 GB | 281 |
| M-640 | 8 vCPUs | 64 GB RAM | 742 GB | 281 |
| M-640 | 8 vCPUs | 64 GB RAM | 1,492 GB | 281 |
| M-640 | 8 vCPUs | 64 GB RAM | 2,992 GB | 281 |
| M-640 | 8 vCPUs | 64 GB RAM | 5,992 GB | 281 |
| M-640 | 8 vCPUs | 64 GB RAM | 8,992 GB | 281 |
| M-1280 | 16 vCPUs | 128 GB RAM | 742 GB | 375 |
| M-1280 | 16 vCPUs | 128 GB RAM | 1,492 GB | 375 |
| M-1280 | 16 vCPUs | 128 GB RAM | 2,992 GB | 375 |
| M-1280 | 16 vCPUs | 128 GB RAM | 5,992 GB | 375 |
| M-1280 | 16 vCPUs | 128 GB RAM | 8,992 GB | 375 |
| M-2560 | 32 vCPUs | 256 GB RAM | 1,492 GB | 500 |
| M-2560 | 32 vCPUs | 256 GB RAM | 2,992 GB | 500 |
| M-2560 | 32 vCPUs | 256 GB RAM | 5,992 GB | 500 |
| M-2560 | 32 vCPUs | 256 GB RAM | 8,992 GB | 500 |
Need help?
Get help from the PlanetScale Support team, or join our GitHub discussion board to see how others are using PlanetScale.