The premium is real and so is what it buys
A managed database typically costs somewhere between two and four times a self-hosted equivalent on the same specification. That is a genuine premium and worth being clear-eyed about.
What it buys is automated backups, point-in-time recovery, patching, monitoring, and in most cases automatic failover to a standby. Every one of those is something you can do yourself, and every one is something people intend to do and do not finish.
Backups are the deciding factor
The single most common serious failure in self-hosted database operations is not a crash. It is discovering, at the worst possible moment, that the backups were not running, or were running but cannot be restored.
A managed service takes backups, retains them, and lets you restore to a point in time. If you self-host, you must not only configure backups but rehearse a restore on a schedule. If you are not going to do that, the managed service is cheaper than it looks.
Where self-hosting genuinely wins
- You need an extension, engine version or configuration the managed service does not allow
- The database is small and non-critical, such as a development environment
- Cost at scale dominates and you have the operational skill in-house
- You need it co-located on the same machine as the application for latency
Where managed genuinely wins
- The data matters and downtime has a real cost
- The team is small and nobody owns database operations
- You need high availability, which is difficult to build correctly
- Compliance requires demonstrable backup and recovery procedures
Managed does not mean you can ignore it
You still own schema design, indexing, query performance and connection management. A managed service will happily run a badly indexed query slowly and charge you for the resources it consumes doing so.
Connection limits in particular catch people out on serverless architectures, where many short-lived functions can exhaust the connection pool. A connection pooler is usually necessary regardless of who runs the database.
A reasonable default
Self-host in development, use a managed service in production. It keeps costs low where failure is harmless and removes the highest-consequence operational risk where it is not.
Related accounts
Accounts on the platforms discussed here: Buy AWS Accounts, Buy DigitalOcean Accounts, Buy UpCloud Accounts.
Related cloud accounts
Accounts on the platforms discussed here, with every configuration and price published up front:
- Buy AWS Accounts — from $25.00. Over 200 services, from EC2 to Bedrock.
- Buy DigitalOcean Accounts — from $25.00. Droplets, managed Kubernetes and Spaces.
- Buy UpCloud Accounts — from $30.00. MaxIOPS storage and no egress charges.
Further reading
- UpCloud Accounts: What You Get and How to Choose a Configuration
- DigitalOcean vs Hetzner: Which Cloud Account Should You Buy?
- Hetzner vs UpCloud: Which Cloud Account Should You Buy?
- AWS vs Oracle Cloud: Which Cloud Account Should You Buy?
Official documentation
Provider behaviour, quotas and pricing are defined by the platform itself. These are the first-party references for the services discussed above:
Frequently asked questions
Typically two to four times a self-hosted instance on comparable specification, varying by provider and configuration.
No. Schema, indexes, queries and connection handling remain entirely yours.
Backups that were never tested. Configuring them is easy; verifying a restore works is the part that gets skipped.
