Supabase Free pause and two-project caps: when indies should buy Pro

When indies stand up an MVP, Supabase Free is often treated as “ship free, think later.” The pain is rarely whether the API works. It is whether projects pause, whether you can keep more than two active projects, and when 500MB of database plus 1GB of file storage stops being enough. This page does not re-teach RLS checklists or Supabase versus Firebase. It freezes Free walls and the Pro starting price of $25 per month as shown on supabase.com/pricing on 2026-10-01, plus the signals that justify paying. Re-check the page before checkout; limits move.

Which Free numbers to freeze

Pricing labels Free at $0 per month for passion projects and simple sites. On the observation day, cards and comparison rows included unlimited API requests, 50,000 monthly active users, 500MB database per project, shared CPU with 500MB RAM, 5GB egress, 5GB cached egress, 1GB file storage, 50MB max upload, and community support. The same page states Free projects are paused after one week of inactivity and that there is a limit of two active projects. For indies those two sentences matter more than “unlimited API,” because a paused demo looks like a failed product to investors and customers.

Free can still power a serious prototype: auth, tables, buckets, and edge functions can all be proven. Treat it as a sandbox with pause and project ceilings, not as a production promise. Put “pauses after a week idle” into your ops notes so you do not remember only on launch day.

Which walls Pro mainly removes

Pro starts at $25 per month with the first project included and additional projects from $10 per month per the page. Versus Free, the page emphasizes production posture: 100,000 MAU then overage, 8GB disk per project then overage, larger egress bundles, and paid plans that are not paused after a week of inactivity the way Free projects are. Paid plans also include $10 in monthly compute credits toward a Micro instance. For a solo builder, the first payment usually buys “no surprise pause + more serious disk/egress headroom + production mindset,” not a totally different product.

If you need SOC2, finer org roles, or enterprise governance, keep reading Team or Enterprise instead of assuming Pro is a compliance suite. If your only issue is a second toy project counting against the active limit, delete or merge projects before you pay.

How to schedule pause risk, two projects, and storage

Treat active projects as scarce quota. A workable shape is one mainline production project and one staging or experiment project. Park extra ideas in branches, flags, or local mocks instead of creating a new Free project every weekend. If staging goes cold, accept that it may pause and document restore steps plus whether data is rebuildable. Point external demo links at environments that will not pause; if you must use Free, hit the project the day before and run a health check.

Budget the 500MB database and 1GB files. Log tables, bulk imports, and original uploads quietly exhaust space. Prefer object-storage lifecycle rules over database blobs; compress images; archive old attachments to your own object store early. Fifty thousand MAU is usually loose for early products, but if you ship a sticky consumer tool, read Pro’s 100k tier and overage unit prices before a campaign day forces the math.

When to buy Pro—and when not to

Buy Pro if these signals appear: a pause already hurt a customer or review; you need more than two stable active environments; 500MB/1GB still tips after cleanup; you already treat RLS, backups, and monitoring as production work. Also upgrade before the first paid customer if “will not pause after a week idle” is part of your delivery promise.

Stay on Free if the product is still internal, data is rebuildable, one project is enough, and you will calendar-nudge activity. After upgrading, do three things immediately: confirm pause policy no longer applies to that project, check disk and egress panels, and decide whether a second paid instance is truly required. Treat From $25/month as a floor; compute and overages can lift the invoice above the card price.

Keep this separate from checklist and comparison posts

Toolvori already publishes a Supabase RLS checklist and a Firebase comparison. Those answer secure defaults and tool choice. This tutorial answers only Free pause, project-count, and capacity walls. Paste the official sentences into your ops handbook with a date. When someone says “Supabase free is fine for production,” ask about pause and the two-project cap before celebrating unlimited API marketing.

Add the verification link for supabase-free-indie-pause-limits to your release checklist. Before a launch or fundraising demo, confirm the environment is not paused and that storage headroom remains. Limits change; the useful habit is a weekly usage glance, not reading docs after an outage. If what you actually need is a warehouse or dedicated object store, split that workload out instead of forcing the wrong shape onto Free disk.

Write upgrade triggers as a checklist: pause risk blocks revenue or reviews, two active projects are not enough after consolidation, storage still tips after cleanup, and Pro maps to the exact blocker. In the first week after paying, wire monitoring and backup expectations into the release flow so the subscription does not become shelfware.