Supabase
Supabase · databases · reviewed by Stan K. · Source: data snapshot · data as of 2026-11-12
The BaaS whose exit is pg_dump — Supabase → any Postgres in 1–5 days, zero schema change — $25/mo Pro with $10 of it compute credits, and a free tier that pauses (not deletes) after 7 idle days.
#3 of 9 in Databases
ToolScore breakdown — why 84/100
10 criteria × 10 points. Low pillars are visible on purpose — that's the point of a score you can audit. Methodology →
What it does well
- ▸Exit is pg_dump: Supabase → any Postgres in 1–5 days ($500–3K), zero schema change — the cleanest exit in the managed table
- ▸Free projects PAUSE after 7 idle days — they are not deleted; unpause on demand, unlimited paused projects
- ▸The only managed provider here publishing connection counts: 60 direct / 200 pooled on Micro
- ▸Pro’s $25 includes $10 compute credits (one Micro instance) — the compute subsidy is disclosed on the page
- ▸The consolidator: “Turso is joining Supabase” (official blog, 02.10.2026)
Where it costs you
- ▸1GB of data outgrows the 500MB free tier — the hero workload starts at $25/mo, not $0
- ▸Egress: $0.09/GB past 250GB on Pro, plus compute add-ons — the bill scales on two axes, not one
- ▸60 direct / 200 pooled connections on Micro is a ceiling a busy app hits before it expects to
Hidden traps — the stuff the pricing page doesn't say
Pro’s $25 includes $10 of compute credits — exactly one Micro instance. Past that, compute add-ons are the scale driver: the $25 you budgeted is the floor, not the ceiling.
On Pro, egress is $0.09/GB past 250GB. For read-heavy APIs the operation bill is joined by a traffic bill — the same axis that makes self-hosting win at 50GB+ in our hub’s callouts.
They are not deleted — unpause is on demand and paused projects are unlimited — but a paused project serves nothing until you act. Anything scheduled against a free database needs a weekly heartbeat.
Know the limits before you pay: read the traps above, then decide with eyes open.
Visit official siteAffiliate link where available — never affects the score.
- official Supabase pricing — official, checked 2026-11-12 verified
- official “Turso is joining Supabase” — official Turso blog, 02.10.2026 verified
Data as of 2026-11-12. Prices and limits change monthly — report anything stale. How we verify: methodology.
Closest alternatives
Postgres on a Hetzner CX23 (2 vCPU / 4GB / 40GB, 20TB traffic) at €5.99/mo ex. VAT — the box that be
Row-based pricing with the largest free cap in the table — 500M reads + 10M writes/mo covers our her
Compute billed in CU-hours with scale-to-zero after 5 min — $0 for idle, ≈$19.35/mo always-on (0.25
Supabase review
In-depth analysis · last updated 2026-11-12
The managed row you can always leave
Supabase prices as an instance-plus-egress backend-as-a-service, and at our hero workload (1M reads + 100K writes, ~1GB, 5GB egress) the month costs $25 on Pro — because 1GB of data outgrows the 500MB free tier on day one. What buys the second place in the managed table isn’t the price, it’s the shape: the exit is pg_dump, Supabase → any Postgres in 1–5 days ($500–3K), zero schema change. In a market where the nearest per-document rival (Firestore) exits through a 2–6 week, $5–25K+ rewrite, that single fact carries the score.
The free tier that pauses instead of deleting
The free plan is 500MB DB + 1GB files + 5GB egress, and its idle behavior is the most forgiving in the table: free projects PAUSE after 7 idle days — they are not deleted. Unpause is on demand, and paused projects are unlimited. The caveat writes itself: a paused project serves nothing, so anything hitting a free database on a schedule needs a heartbeat.
What the $25 contains
Pro’s $25 includes $10 of compute credits — exactly one Micro instance — and the connection ceilings are published: 60 direct / 200 pooled on Micro. Supabase is the only managed provider in this comparison that publishes connection counts at all. Past 250GB, egress bills at $0.09/GB, and compute add-ons stack on top: two axes of scale, both disclosed.
How the pillars land
Price/Value 9.5: $25 buys the whole BaaS month with $10 of it compute credits, and a real free tier below — at the hero workload only Turso, Neon and Firestore bill $0. Real limits 9: 500MB/1GB/5GB free caps and 60/200 connections published. Latency & cold starts 7, neutral band: no query-latency facts in this snapshot — the only cold-start-shaped fact is the pause/unpause cycle, a cold start you can schedule around. Data handling sits at the neutral 5 — no data-handling facts in this snapshot. Portability & export 10: pg_dump, 1–5 days, zero schema change. Feature set 9.5: database, files and egress in one instance model. Track record 9.5: the consolidator — Turso is joining Supabase (02.10.2026). Ease of use 9: paused ≠ deleted, unpause on demand, unlimited paused projects. Pricing transparency 9.5: credits, egress rate and connection counts all on the page. Support & docs sits at the neutral 5 — nothing support-related was verifiable from the official pages in this snapshot.
Verdict — CLEANEST EXIT, 84/100
Pick Supabase when the architecture may outlive the vendor relationship: every table leaves as standard Postgres, and the $25 month is priced in credits you can audit. Watch the two-axis bill (egress past 250GB, compute add-ons) and the Micro connection ceiling — 60 direct is a number a busy weekend finds.