Database Cost Comparison
Compare Database Costs
Across Every Provider
No polished comparison tool for managed databases exists. DBCost shows price but no performance. DBench runs fixed benchmarks, not your workload. benchANT publishes research papers, not self-service results. Teams copy-paste numbers from eight different pricing pages and still miss I/O charges, egress fees, and monitoring costs. SelfHost gives you one place: define your workload, get a full cost and performance breakdown across every major provider.
0
tools that combine workload-specific benchmarks, live pricing, and feature comparison for managed Postgres in one place.
2.7x
TCO gap between the most and least expensive managed Postgres setup for the same production workload
8 pages
a team manually cross-reference to compare major managed Postgres providers, none showing the full bill pre-hand
What comparing Postgres providers actually looks like
4 vCPU / 16 GB RAM / 200 GB SSD / production HA / us-east-1 or equivalent region.
Eight tabs. Eight formats. Eight ways to miss the same hidden fees.
One page. One tab. Easy comparison.
What you're actually fighting against
Every team making a provider decision faces the same information problem. The tools that exist are either incomplete, stale, or not built for your actual workload.
Existing Tools
- Tab-hop across 8 pricing pages, each in a different format
- Miss Aurora I/O charges, RDS Proxy fees, GCP egress tiers - line items that routinely double the instance price
- Rely on blog posts from 2022 with stale numbers
- End up comparing instance price only - not what the bill actually looks like
- No way to account for your specific read/write ratio or connection count
- Still make the wrong call, then discover the real cost 30 days later on the bill
After SelfHost
- One workload input drives the entire comparison
- Every line item included, compute, storage, I/O, egress, backup, monitoring
- Pricing refreshed daily from provider APIs
- Performance data alongside cost, not just the price tag
- See which providers get expensive as you scale, not just today's number
- Shareable link, send it to your team or use it in a vendor conversation
How SelfHost is planning to solve this
Three layers. Every signal is actionable.
Layer 1 of 3
Your Real Numbers
Not a generic slider.
- vCPU, RAM, storage, growth rate, queries/sec, read/write ratio, connections, region, and HA preference - all as inputs, not approximations
- Determines which instance families get selected per provider
- Accounts for how I/O-heavy workloads get priced differently - Aurora bills per million I/O ops, GCP bundles it, RDS hides it until the bill arrives
What all is included
The full capability set, end to end.
Additional capabilities:
Help this reach further.
The more input we get, the better we build. Share this idea and bring in more voices.
25 votes so far
Vote if this is something you'd genuinely use and wouldn't mind paying a small fee for.
Browse
Other ideas to
explore.
Database Storage Downsizing
AWS locks storage at its peak - once autoscaling bumps up your volume, you pay for that size forever. SelfHost can shrink it back transparently, something RDS structurally cannot do.
Auto Indexing
Every managed Postgres provider stops at recommending indexes. SelfHost shadow-tests and executes them, with automatic rollback if query performance drops after creation.
Cost Monitoring
AWS Cost Anomaly Detection waits up to 24 hours. SelfHost flags active cost anomalies in 5-15 minutes, maps the likely culprit even with incomplete tags, and gives your team context to act before the bill compounds.