ToolScore
Data & Files 4 min read

Managed Database Traps: Egress, Connections, and the M10 Cliff

6 traps, all verified the number that matters here

By Stan K.

The free tier disappears while you sleep (Supabase pauses at 7 days), connection limits force compute upgrades, and Atlas jumps $30 to $57 the month you cross 5 GB. Six verified traps between you and a predictable database bill.

Managed databases remove ops work and add fine print. Here are the six traps we verified against official pricing pages — each one sits between a “free” or “$5” entry point and the bill you actually receive.

1. Supabase pauses free projects after 7 idle days

Free-tier Supabase projects are paused after one week of inactivity (not deleted — but waking one takes minutes and manual intervention). The side effect nobody plans for: your hobby project’s cron job, webhook or weekend traffic pattern is what keeps the database “active.” Any demo, staging or weekend tool that goes quiet for 8 days greets its next visitor with a paused-project page. Pro ($25/month) is the always-on tier.

2. Egress is the silent multiplier

  • Supabase: 250 GB/month included with Pro, then $0.09/GB
  • MongoDB Atlas: internet egress past included allowances at $0.09/GB-class rates
  • Google Cloud/Firebase: $0.12/GB — the highest of the majors

Returning unpaginated JSON or base64 blobs from database rows is the classic trigger. The database bill is fine; the bandwidth the database generates is the invoice. (Same physics as the storage egress tax — the data layer has one too.)

3. Connection limits are priced in compute tiers

Serverless platforms open hundreds of concurrent TCP connections during spikes; a standard Postgres exhausts RAM at 60–200 direct connections. Supabase’s answer is a pooler (Supavisor on all plans; dedicated PgBouncer from Pro) — but the limits scale with compute add-ons, not your plan: Micro 60 direct/200 pooled, Small +$5/mo for 90/400, Medium +$50/mo for 120/600, Large +$100/mo for 160/800. The trap: a traffic spike that “requires” a bigger instance is often just a missing pooler configuration — fix the pool before paying the tier.

4. The MongoDB Atlas M10 cliff

Atlas’s ladder is smooth until it isn’t: M0 free (512 MB, 100 ops/sec, 500 connections), Flex tier ($8–30/month, auto-scaling, hard-capped at $30), and then — the moment you exceed 5 GB, want VPC peering, or need custom backups — the Dedicated M10 at $56.94/month. The jump from a $30 Flex cap to $57 dedicated is a 2× step function that arrives with a specific feature request, not with traffic. Plan the cliff into the roadmap before you hit it at 2am.

MongoDB Atlas — the ladder and the cliff
M0 free $0
Flex tier (hard cap) $30 cap
Dedicated M10 $56.94

5. Neon: compute you can’t see

Neon bills by Compute Unit-hours (1 CU ≈ 1 vCPU + 4 GB RAM; Launch at $0.106/CU-h). Scale-to-zero makes hobby bills near-zero — a 0.25 CU database running 4 hours/day is ~30 CU-hours. But an always-on production instance at 0.25 CU burns ~182 CU-hours ≈ $19+/month before storage. The trap: “serverless” pricing is only cheap for databases that sleep; production databases don’t sleep. Also billed: branch storage deltas — copy-on-write branches share the parent at first, then accumulate their own bill as they diverge.

6. The free tiers that already vanished

PlanetScale retired its free tier entirely — the floor is now the $5/month PS-5 single-node Postgres (HA at $15; the famous Vitess/MySQL line is now the legacy track from $39). Turso’s free tier is real and generous (500M row reads/month) but the company joined Supabase in October 2026 — when a provider consolidates, re-check the free tier quarterly. “Free tier” is a marketing line item, not a contract.

The pattern, one sentence

Every managed trap reprices something you can’t easily count at signup — idle days, connections, GB out, gigabytes stored, compute hours asleep — into something you pay for monthly. Whatever your architecture, name the six numbers before launch: idle policy, egress rate, connection ceiling, tier cliffs, sleeping compute, and free-tier status.

The counterweights

Numbers change — the math doesn't
Token prices and plan limits shift monthly; the structural arguments in this guide age slowly. For current per-tool numbers see the live rankings.