Database & Backend Platform · decision tool
Cheapest database for a side project
At side-project scale (a few thousand users, a GB or two) the winner is whichever free tier actually covers you — priced live from verified pages, with the first bill you'll hit when you outgrow it.
Prices verified 2026-07-15 against official pricing pages · fit weights are our estimates (see methodology) · share the URL to share your configuration
As of Jul 2026, with 1,000 monthly active users, 1 GB database size, 2 GB monthly egress, 1,000 db operations per user / month, 24 compute active hours / day, a $5 budget for this slot, Firebase (Firestore) ranks first for these inputs at 94% fit and a StackSays-estimated $0/month (Turso: 81% fit, $0/month). Fit weights are our estimates; prices trace to official pages. Change any input below and the verdict recomputes.
Your situation
The verdict updates as you move these.
Clear pick for your inputs
Google's document database with realtime sync and a huge mobile ecosystem
vs Turso: fit 94% against 81%, est $0 against $0 per month
The decision, in plain words
For a solo builder at 1,000 monthly active users and a $5.00/mo budget for the database slot, Firebase (Firestore) leads at 94% fit and $0/mo. The two rules doing the work: budget fit (Runs free at your usage — $0 vs your $5/mo budget); batteries included (Bundles auth, file storage, realtime — fewer services to glue at team size 1).
The gap to Turso (81% fit) is wide at these inputs — you'd need to change your requirements, not your taste, to flip it.
Honest weak spot of the pick: proprietary data model — leaving means rewriting the data layer.
Generated from the calculation above — every number traces to the sourced data; nothing here is written by an AI making things up.
Why Firebase (Firestore) scores 94%
How the $0/mo estimate is calculated
What could change this verdict
Cost risk
Official prices verified 2026-07-15; calculation is deterministic code over those prices.
At a glance
| Tool | Free tier | Paid entry | Verified |
|---|---|---|---|
| Supabase | 500MB database, 50K MAU, 1GB file storage, 5GB egress, 2 projects | Pro plan $25/mo | 2026-07-15 |
| Neon | 0.5GB storage + 100 compute-hours per project, 5GB egress, 60K auth MAU | Pay-as-you-go — Compute billed per CU-hour ($0.106); suspended compute costs $0; storage $0.35/GB-month | 2026-07-15 |
| Firebase (Firestore) | 1GiB Firestore, 50K reads / 20K writes / 20K deletes per day, 50K auth MAU, 10GiB egress | Pay-as-you-go — Firestore nam5 rates: $0.06/100K reads, $0.18/100K writes, $0.18/GiB storage; deletes ($0.02/100K) not modeled. Ops derived from your per-user activity input (80/20 read/write split, our estimate) | 2026-07-15 |
| Convex | 1M function calls, 0.5GB database, 1GB file storage, 1GB egress | Professional $25/mo | 2026-07-15 |
| Turso | 100 databases, 5GB storage, 500M rows read / 10M rows written per month | Developer plan $4.99/mo | 2026-07-15 |
| PlanetScale | No free tier | PS-5 HA cluster $15/mo | 2026-07-15 |
| MongoDB Atlas | 512MB storage, shared CPU/RAM, ~100 ops/sec cap | Flex tier $8/mo | 2026-07-15 |
Data sources
| Tool | Source | Verified |
|---|---|---|
| Supabase | Supabase pricing page | 2026-07-15 |
| Neon | Neon pricing page | 2026-07-15 |
| Firebase (Firestore) | Firebase pricing page | 2026-07-15 |
| Convex | Convex pricing page | 2026-07-15 |
| Turso | Turso pricing page | 2026-07-15 |
| PlanetScale | PlanetScale pricing page | 2026-07-15 |
| MongoDB Atlas | MongoDB Atlas pricing page | 2026-07-15 |
A monitor re-checks these pages for changes; when a vendor moves a price, the date updates and every verdict recomputes.