What 1 TB of Postgres Storage Costs per Month: Supabase vs Neon vs Turso

Storage pricing is the quietest line on a database bill and the one that compounds. A product that grows from 10 GB to 1 TB does not notice for a year, then notices every month.

Here is what that terabyte costs on the three managed databases most side projects pick between, computed from the rates published on 2026-10-25.

The storage line at 1 TB

The arithmetic is 1,024 GB minus whatever the plan includes, times the rate. Supabase also bills file storage separately at $0.0213/GB beyond 100 GB, and Neon bills history storage at $0.20/GB-month on top of the database storage line.

What each vendor is actually selling

Supabase sells a provisioned disk attached to one Postgres instance. You choose the size, you pay for the size, and the number is predictable: the storage line moves in steps when you resize.

Neon sells storage in GB-months and separates the data from its history. The database itself is $0.35 per GB-month; the write-ahead log that makes instant restore work is $0.20 per GB-month, billed on whatever history window you configure. A team that keeps a 7-day restore window pays for seven days of writes on top of the data.

Turso stores a SQLite database per tenant rather than one big Postgres cluster. That architecture makes small databases nearly free to host and makes the per-GB rate the highest of the three, because each database carries its own overhead.

What 1 TB does to the rest of the bill

Storage is rarely what you notice first. On Neon, a database kept always-on at the minimum 0.25 CU burns about 182.5 CU-hours a month — roughly $19.35 at $0.106 per CU-hour — before any storage. On Supabase, the $25 Pro plan includes $10 of compute credit, and the next instance size up lists at $60/month, so compute can quadruple a bill while storage is still in single digits.

The crossover that matters: below about 50 GB, compute and fixed plan fees decide the bill. Above that, storage starts to dominate on Turso and Neon, and stays a rounding error on Supabase until the terabyte range.

How we measured it

We took the per-GB storage rates and included allowances from each vendor's pricing page on 2026-10-25 and multiplied by 1,024 GB. Nothing was provisioned and no benchmark was run, so these are list prices before negotiated discounts or annual commitments. Where a vendor bills a second storage-like line — Supabase file storage, Neon history storage — it is named in the table rather than folded into the total.

Bottom line

For a conventional Postgres application that will hold a terabyte, Supabase's $0.125 per GB is the cheapest of the three by a factor of nearly three. Neon's higher rate buys branching, scale-to-zero and per-branch storage that only counts changed data. Turso's price only makes sense when the database count is high and each one is small — at which point the included allowances, not the overage rate, are what you are buying.