Up to two active projects, each with a 500 MB Postgres database, plus 50,000 auth MAU, 1 GB file storage and 500,000 Edge Function invocations; idle projects pause after a week. Realtime adds 200 concurrent connections and 2 million messages a month.
Free allowance
What the free plan includes, as the provider states it.
- database size · Postgres
- 500 MB
- Per project; the project enters read-only mode above 500 MB of database size.
- file storage · Object storage
- 1 GB
- Per organization.
- monthly active users · Authentication
- 50K
- Distinct users who sign in or refresh a token during the billing cycle.
- Edge Function invocations / month · Serverless functions
- 500K
- Per organization, per billing cycle.
- egress / month
- 5 GB
- Unified uncached egress across Database, Auth and Storage, per billing cycle; a separate 5 GB applies to cached egress.
- projects
- 2
- Active free projects across all organizations where you are Owner or Administrator; paused projects do not count.
- Realtime concurrent connections · Realtime messaging
- 200
- Counted as each project's peak in the billing cycle, summed across the organization; going over brings an email and a grace period, then service restrictions if it continues. Each project is also capped at 200 at once, and Realtime refuses new channel joins beyond that (too_many_connections).
- Realtime messages / month · Realtime messaging
- 2M
- Per organization, per billing cycle; covers database changes, Broadcast and Presence. A broadcast counts once when sent plus once per receiving client, and a database change counts once per listening client. Going over brings an email and a grace period, then service restrictions if it continues.
- Realtime messages per second / second · Realtime messaging
- 100
- Per project; counts WebSocket messages sent to or from clients. If a project generates more, Realtime disconnects its connections (tenant_events), and supabase-js reconnects once throughput drops below the limit.
Before you rely on it
Read with the default assumptions: a project that may grow and may make money.
- Notice: Pauses after 7 days without activity
The fine print
Each verdict links to the quote it rests on.
- Free for
- As long as you stay within the limits
- At the limit
- Anything over the limit is refused until the next period
- Spending cap
- None needed: the free plan cannot bill you
- Idle projects
- Paused after 7 days without activityProjects with low database activity over 7 days are paused after an email warning; a paused project can be restored from the dashboard for up to 1 year.
- Data retention
- No deletion rule documented
- Card at sign-up
- Not documented
- Identity check
- An email address
- Commercial use
- Not stated
- Mainland China
- Partly reachableGreatFire rates supabase.co as mixed: most tested project API hosts (*.supabase.co) are disrupted some of the time, the rest load normally and none is blocked. Direct Postgres connections were not tested.
- Sign-up regions
- No restrictions documented
- Quotas apply per
- Organization
Alternatives
Other free plans for the same need, ranked by the same neutral rules.
Changes
- Correction
Better: Mainland China reachability corrected: not verified → partly reachable
- Correction
Worse: Free connections corrected: not listed → 200 / concurrent
- Correction
Worse: Free messages corrected: not listed → 2M / month
- Correction
Worse: Free messages corrected: not listed → 100 / second
- Oct 15, 2026
- Awaiting review
- Free