Published prices and connection limits
DigitalOcean's managed database pricing page listed these MySQL Standard plans on 29 October 2026. Extra storage is $0.215 per GiB per month in 10 GiB increments. The page offers 0, 1 or 2 additional nodes but did not show what each adds to the price, so get that figure from the control panel. Connection limits come from DigitalOcean's MySQL limits page.
| Memory | vCPU | Storage range | Monthly | Backend connections |
|---|---|---|---|---|
| 1 GiB | 1 | 10 to 30 GiB | $15.15 | 75 |
| 2 GiB | 1 | 30 to 60 GiB | $30.45 | 150 |
| 4 GiB | 2 | 60 to 120 GiB | $60.90 | 400 |
| 8 GiB | 4 | 140 to 280 GiB | $122.10 | 800 |
| 16 GiB | 6 | 290 to 580 GiB | $244.35 | 1,600 |
Managed MySQL against MySQL on the Droplet
| Concern | MySQL on your Droplet | DigitalOcean Managed MySQL |
|---|---|---|
| Backups | Droplet backups at 20% (weekly) or 30% (daily) of Droplet price, whole-server images | Daily full backups plus logs; restore to any point in the previous 7 days |
| Restores | Restore the whole Droplet image, or your own dumps | Restore goes to a new node; re-add standby or read-only nodes afterwards |
| Updates | You patch MySQL and the OS | You pick a weekly window; DigitalOcean applies OS and engine updates |
| Failover | None unless you build replication | Standby node takes over automatically; Standard Edition advertises failover in minutes |
| Connections | You set max_connections | Fixed by plan size: 75 on 1 GiB, 150 on 2 GiB |
| Network security | Local socket or localhost | Trusted sources allowlist; Cloud Firewalls cannot be used with managed databases |
| Control | Full, including root | No root user; connection pooling and query statistics not supported for MySQL |
Cost comparison for one course site
Using list prices from the Droplet and database pricing pages:
Option A, everything on one Droplet: a 4 GiB, 2 vCPU Droplet ($24) with daily backups ($7.20) is $31.20 a month. MySQL shares the 4 GiB with PHP.
Option B, split: a 2 GiB, 1 vCPU Droplet ($12) with daily backups ($3.60) plus a 1 GiB managed MySQL cluster ($15.15) is $30.75 a month. PHP gets 2 GiB to itself and the database gets its own 1 GiB node with point-in-time recovery, but there is no standby node at this price.
The two are close in cash. The split buys point-in-time recovery and a database you do not patch; the single Droplet buys more total RAM for PHP, no network hop between web server and database, and one machine to reason about. Adding a standby node to Option B adds cost the pricing page did not itemise.
Connection math for a busy LMS
Each PHP worker that is serving a WordPress request holds a database connection while it runs. Count the maximum: web servers times pm.max_children, plus cron runs, admin sessions and backup or reporting tools.
Example with assumed settings: two Droplets with 20 workers each is 40 connections, which fits the 1 GiB plan's 75. Three Droplets with 30 workers each is 90, which exceeds 75, so the 2 GiB plan with 150 is the minimum. Running out of connections shows up as database connection errors exactly when the most learners are online.
Who benefits and who should skip
- Benefits: sites with two or more web Droplets behind a load balancer, which need a shared database anyway.
- Benefits: courses selling access where losing a day of orders, enrolments or progress would be serious; seven days of point-in-time recovery narrows the loss window compared with a daily Droplet image.
- Benefits: teams that want database patching off their list but keep the web server themselves.
- Skip: a single small Droplet where the database is a few hundred MB; one size up of Droplet is simpler and similar in cost.
- Skip: teams that rely on direct root-level MySQL tuning or connection pooling, which the limits page says are not available.
- Plan carefully: anyone expecting to grow past 4 GiB or add standby nodes on Standard Edition after DigitalOcean's 30 November 2026 change; check what Advanced Edition costs before committing.
Checklist before moving the database
- Create the cluster in the same region as the Droplets; standby nodes must also be in the same region.
- Add the Droplets as trusted sources; the limits page notes VPC networks only reach resources in the same region, another reason to keep cluster and Droplets together.
- Expect daily backups to take a table lock that blocks schema changes; schedule plugin updates that alter tables away from the backup time.
- Remember point-in-time recovery only reaches back 7 days; keep your own longer-term dumps if you need older restores.
- Know that a restore creates a new node, so plan how you will update DB_HOST in wp-config.php.
- Rehearse the cutover on staging and test login, enrolment, checkout and progress saving.
Questions before you decide
How much does DigitalOcean Managed MySQL cost?
The pricing page listed $15.15 per month for 1 GiB, 1 vCPU and 10 to 30 GiB of storage on 29 October 2026, rising to $30.45 for 2 GiB and $60.90 for 4 GiB. Extra storage is $0.215 per GiB per month.
How long are Managed MySQL backups kept?
DigitalOcean's features page says daily backups and logs let you restore to any point within the previous seven days.
Does a single-node cluster fail over?
DigitalOcean describes automatic failover when a standby node is present; the documentation did not give a failover time for single-node clusters, so treat a standby node as the requirement for failover.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- DigitalOcean: Managed database pricing Accessed 29 Oct 2026
- DigitalOcean: MySQL limits Accessed 29 Oct 2026
- DigitalOcean: MySQL features Accessed 29 Oct 2026
- DigitalOcean: Managed MySQL product page Accessed 29 Oct 2026
- DigitalOcean: Droplet pricing Accessed 29 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.