Supabase compute instances: the full price list from Micro to 16XL

Supabase's plan price and its compute price are two different lines, and the second one decides the bill. The Pro plan starts at $25 a month; the instance underneath it ranges from $10 to $3,730. Every paid plan carries a $10 monthly compute credit, so the question is not whether compute is included but how far that credit stretches.

A medium-sized application typically lands on Medium: 4 GB of RAM, shared CPU, $60 a month, of which $50 is left after the credit. The steps either side of it are where most of the pricing decisions actually sit.

The instance ladder

Connection limits scale with the instance: Micro allows 60 direct and 200 pooler connections, Medium 120 and 600, and 16XL 500 and 12,000. Compute is billed hourly, and the pricing page notes you can scale up or down at any time.

What the numbers actually mean

The ladder is not linear. Micro to Small is $5 for another gigabyte. Small to Medium is $45 for another two, and the price per gigabyte jumps from $7.50 on Small to $15 on Medium. That is not a rounding artefact: Medium is the first size meant for production traffic, and it is priced accordingly.

Above Medium the curve flattens again in per-gigabyte terms — Large is $13.75 per GB, XL $13.13, 2XL $12.81 — because those instances are sold on dedicated vCPU as much as on memory. 4XL reverses it at $15 per GB, which is the point where the shape of the offer changes from "database" to "dedicated server".

The credit is the one discount that applies to all of them. $10 a month covers a Micro instance exactly, and the pricing table marks the first instance as free on paid plans. It does not stack: it is one credit per organization per month, so a second project adds its own compute on top of the $10 per-project fee.

How we measured it

Every price, RAM figure and connection count is quoted from the Supabase pricing page on 2026-10-25. The hourly billing rule, the partial-hour rounding and the statement that credits reset monthly without accumulating come from Supabase's compute usage documentation on the same date. The "left after credit" column subtracts the published $10 credit from the published instance price and is labelled calculated where it appears as a total.

What changes in practice

The jump from Small to Medium is the single most common surprise. A side project on Pro with a Micro instance pays $25 and nothing more. The moment it needs 4 GB, the bill is $75, not $25 — three times the plan price for a change most teams make in a single click in the dashboard.

Partial hours matter less than they look but they do bite in the wrong direction. Supabase bills a full hour for any part of an hour used, so a project restarted five times in an afternoon is billed for five hours of whichever size was live. Resizing down after a load test does not refund the hours already spent at the bigger size.

The credit also hides a step. Because $10 covers Micro exactly, a team that moves to Small sees a $5 increase and concludes that compute is nearly free. Small is 2 GB of shared RAM; the next click is $45 more.

The connection counts are the second hidden step. Medium allows 120 direct and 600 pooler connections against Micro's 60 and 200, and a serverless app that opens a connection per invocation exhausts Micro's 60 long before it exhausts 1 GB of RAM. Routing through the pooler endpoint is the cheaper fix than buying a bigger instance.

Bottom line

Budget $25 a month for Pro plus a Micro instance, and expect the real bill to be $75 once the app needs 4 GB — that is Medium at $60 minus the $10 credit, on top of the plan. Stay on Small at $15 as long as 2 GB and 90 direct connections hold; the $45 step to Medium is the one worth measuring before you take it.