Managed database or self-hosted: the real cost comparison

Von Rohit Athaide · Veröffentlicht am 3. Nov. 2026

You can run a database yourself on a virtual machine, or rent one as a managed service. The managed price looks higher, and often is. The comparison is not the two prices, it is the two total costs including the work.

What a managed database charges for

Using PostgreSQL as the example, a managed service usually bills for:

• The instance, per hour, by size.
• Storage, per gigabyte per month, by volume type.
• Performance above a baseline, such as provisioned operations per second.
• A standby copy, if you want automatic failover. See Multi-AZ and high availability.
• Backups beyond an included amount, and read replicas.
• Data transfer out of the cloud or between regions.

Our managed databases catalog lists the instance and storage prices we have read for AWS, and the PostgreSQL pricing guide compares the four clouds.

What self-hosting adds

On a plain server, the infrastructure is cheaper, because you pay for a VM and a disk. The rest is work and risk.

• Setup and patching. Installing, configuring and upgrading the database and the operating system.
• Backups and restores, and testing that a restore works. A backup you have never restored is a hope.
• High availability. Replication, failover and monitoring are yours to build and maintain.
• Monitoring and alerting for disk, memory, connections and slow queries.
• Security. Network rules, encryption, access control and audit.
• On-call. Someone has to be reachable when the database stops at night.

Each is a task with a cost in hours and a cost in the incidents that happen when it is done badly.

A way to compare

Add up, for each option, the monthly infrastructure, plus the hours per month your team spends, multiplied by what an hour of that person costs, plus a rough cost of the incidents you expect. For a small team with no database specialist, managed almost always wins, because the hours are the large number. For a team with deep database skills and a very large, steady, performance-critical database, self-hosting can save money.

When managed is clearly right

• The team is small, or no one is a database specialist.
• Downtime is costly and automatic failover matters.
• Compliance needs documented backups and patching.
• The database is small to medium.

When self-hosting is worth considering

• The bill for the managed service is very large and steady.
• You need a version, extension or setting the service does not allow.
• You already have the skills and the on-call practice.

A middle route

Some vendors offer a managed service on a cheaper compute type, or a version that runs on your own cloud account with the vendor’s tooling. These are worth comparing before you commit to running everything yourself.

What to do next

Price both options on the same workload, with the same storage and the same availability. Use the estimator, which includes a managed PostgreSQL line, and compare the totals. For the storage side, read block storage volume types.