Go from Supabase to Supabase (free tier)
The job: Backend as a service (Postgres database, Auth, File storage). Pick where you are today and where you want to land; the move below follows your pick.
Every way to do this job · pick one
Switch app
Open source
Keep it and pay less
The money
$25/mo today , then $0/mo
Supabase Pro
Modeled from public list prices, with your time at $50 an hour. Show the math
Does it do the job? 3 of 3 covered
- Covered: Postgres database
- Covered: Auth
- Covered: File storage
The work
- Setup
- About 15 min
- Upkeep
- None
- Watch out
- Check first: You only rely on: Postgres database, Auth, File storage
Make the move in four steps
Export from Supabase
The Postgres database (schema and data). Format: Logical backup made by the Supabase CLI
Export stepsCheck what Free plan keeps
500 MB database, 1 GB file storage, 50,000 MAU, 5 GB egress, 5 GB cached egress, shared CPU with 500 MB RAM, 500,000 Edge Function invocations…
DetailsSwitch to Free plan
Change the plan in Supabase's billing settings before your renewal date.
Check the next bill
Your next Supabase invoice should show the lower price. Check that your data and links still work.
The whole recipe: 3 ways out, best first
What you use
- Postgres database
- Auth
- File storage
Not covered
- Realtime
- Edge functions
- Vector (pgvector)
- Auto-generated APIs
- Daily backups
Check before switching
- You only rely on: Postgres database, Auth, File storage
- Export your data from Supabase before canceling
Agents: get_recipe("replace-supabase") on the Stackcut MCP server.
3 ways out, best first
How we got this
| You pay now: Supabase Pro | flat price | $25/mo |
|---|---|---|
| New cost: Supabase (free tier) | free plan | $0/mo |
| Difference each month | $25 − $0 | +$25/mo |
| Over 12 months | +$25 × 12 | +$300 |
| Setup, once | 0.25 h × $50/h | −$12 |
| Year one | +$300 − $12 | +$288 |
- Not counting your time (0.25 h in year one): saves $300 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How we got this
| You pay now: Supabase Pro | flat price | $25/mo |
|---|---|---|
| New cost: Neon (free tier) | free plan | $0/mo |
| Difference each month | $25 − $0 | +$25/mo |
| Over 12 months | +$25 × 12 | +$300 |
| Setup, once | 1 h × $50/h | −$50 |
| Year one | +$300 − $50 | +$250 |
- Not counting your time (1 h in year one): saves $300 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How we got this
| You pay now: Supabase Pro | flat price | $25/mo |
|---|---|---|
| New cost: Supabase (self-hosted) | a small server (modeled) | $5/mo |
| Your upkeep time | 2 h/mo × $50/h | $100/mo |
| Difference each month | $25 − $5 − $100 | −$80/mo |
| Over 12 months | −$80 × 12 | −$960 |
| Setup, once | 4 h × $50/h | −$200 |
| Year one | −$960 − $200 | −$1,160 |
- Not counting your time (28 h in year one): saves $240 in year one.
Year one = 12 × (what you pay now − the new cost − upkeep) − setup, with your time at $50/hour. Prices are public list prices; hours are Stackcut’s planning estimates. Price it for your team
How to leave Supabase
Export first
- Database: roles, schema and data: supabase db dump --db-url … with -f roles.sql --role-only, then -f schema.sql, then -f data.sql --use-copy --data-only (SQL). Storage objects aren't in the dump; move them separately. supabase.com
What you lose
- Daily backups, on Free
- Staying awake: Free projects pause after a week of inactivity
Cancel
- Back up first with the Supabase CLI (see export); Free projects get no automatic backups.
- Change the subscription plan in your organization's billing settings.
- Refunds
- The organization gets credits for unused time on the plan; they don't expire and can be used later.
- After you cancel
- You may see a charge for unbilled usage from the previous billing cycle. You get 2 active free projects; paused projects don't count.
Compare before you switch
Read the checked comparisons and workload guides for the tools this recipe replaces.
- Supabase vs Neon Checked comparison evidence, migration details, public switching accounts.
- Supabase alternatives in 2026: what to use instead, and what it really costs Compare the wider set of alternatives and their tradeoffs.
- Database and auth for an MVP: what it costs from 1,000 to 250,000 users Choose for a new project, using its workload and volume.
More Databases recipes
All 139 recipes · Savings leaderboard · Every vendor, with prices and cancel steps