If you create PostgreSQL or MySQL database clusters with the DigitalOcean API, Terraform, or doctl, you may need to update your code before these changes apply to your account. Updated reference documentation is coming soon.
PostgreSQL and MySQL Plan Changes Beginning 15 October 2026
Last verified 30 Sep 2026
The plans available for new PostgreSQL and MySQL database clusters change in two phases:
- Standard Edition: Beginning 15 October 2026 for accounts that have never created a PostgreSQL or MySQL database cluster, and beginning 30 November 2026 for all accounts:
- Plans with more than 4 GiB of RAM are no longer available for new clusters.
- New clusters do not support standby nodes or read-only nodes.
- Advanced Edition: Beginning 15 October 2026 for all accounts, Basic - Shared CPU plans with 8 GiB to 64 GiB of RAM become available.
If you need larger plans, read-only nodes, or standby nodes for high availability, use Advanced Edition.
Timeline
| Date | Change |
|---|---|
| 15 October 2026 | Restrictions on Standard Edition plan selection take effect for accounts that have never created a PostgreSQL or MySQL database cluster. Accounts that have created a cluster of either engine, even one that was later deleted, are not restricted until 30 November 2026. Support for Basic - Shared CPU plans on Advanced Edition becomes available for all accounts. |
| 30 November 2026 | Restrictions on Standard Edition plan selection take effect for all accounts creating new database clusters. |
Plans That Remain Available
Standard Edition keeps its Basic - Shared CPU plans with 1 GiB, 2 GiB, and 4 GiB of RAM, with Regular, Premium AMD, Premium Intel, and AMDv5 CPU options.
Advanced Edition keeps all of its current Dedicated CPU plans. Beginning 15 October 2026, it also supports Basic - Shared CPU plans with 8 GiB to 64 GiB of RAM, with Regular, Premium AMD, Premium Intel, and AMDv5 CPU options.
For the differences between editions, see PostgreSQL Advanced Edition and MySQL Advanced Edition. For pricing, see PostgreSQL pricing and MySQL pricing.
Existing Clusters
Clusters created before the restrictions apply to your account are not affected by these changes. You can continue to resize, fork, and restore these clusters from backups, including onto plans that are otherwise unavailable for new clusters, and add standby and read-only nodes. No action is required for these clusters. We will provide advance notice before making any future changes to plan availability for existing clusters.