~/guides/SUPABASE.md

Guides / Build apps

Supabase's free plan is your whole backend: database, login and file uploads, with no server to run

Supabase's free plan gives your vibe-coded app a Postgres database, login and 1 GB of file storage; one URL and one key let the AI write to it. Limits included.

Watch the reel on InstagramComment #SUPABASE to get this guide

You vibe coded an app. Where does its data live? Rent a server and install Postgres yourself, and a 3 a.m. crash is your phone ringing. This is the full version of my SUPABASE reel: Supabase's free plan bundles the database, login and file uploads, with no server for you to run. Every number, limit and menu path was checked against Supabase's official pages on 2026-11-18.

01What you get: a free backend (database + login + files)

Reel frame: the free-plan list on supabase.com/pricing on the laptop, database, users and file storage ringed
Reel frame: the free plan's three pieces, database, login, file uploads.

When you finish this guide your app has:

  1. A full Postgres database (every Supabase project is a real Postgres).
  2. User sign-up and login (Auth), 50,000 monthly active users on the free plan.
  3. File uploads and storage (Storage), 1 GB on the free plan.
  4. One project URL plus one key to paste into Claude Code or Cursor, so the AI can write data straight into it.
Supabase pricing page, Free plan: $0/month, 50,000 monthly active users, 500 MB database, 1 GB file storage
The Free plan on the official pricing page (captured 2026-11-18).

02Why not self-host: the difference is who gets woken up

Reel frame (illustration): two paper doors, self-host and Supabase, Postgres behind both, a 3:00 alarm clock
Reel frame (illustration): Postgres behind both doors; the difference is who the alarm wakes.

Postgres itself is free; anyone can download it. The database was never the problem, keeping it alive is. Self-hosting means you:

  1. Rent a machine that never turns off and install Postgres.
  2. Set passwords, a firewall and encryption so strangers can't walk in.
  3. Run backups, or everyone's data dies with that one machine.
  4. Keep up with updates and security patches forever.
  5. Take the 3 a.m. call when it crashes, and you still haven't built login or file uploads.

Supabase takes all of that over: Postgres runs on their machines, locked down and updated, with login and file storage built in, and their engineers are the ones on duty.

Reel frame: the supabase.com homepage on the laptop, Start your project ringed, five chore stickies struck through
Reel frame: open a project, live in minutes, five chores crossed out.

03Step 1: open your first project

  1. Go to supabase.com, click Start your project at the top right and sign in with GitHub or email.
  2. Click New project, give it a name and wait for it to build (usually a few minutes).
  3. Once it's ready the left menu has Table Editor (tables), Authentication (login) and Storage (files).
Supabase homepage: Build in a weekend, Scale to millions, the Start your project button
The official homepage (captured 2026-11-18): every project is a full Postgres database.

04Step 2: connect your app or AI tool

An AI tool doesn't have to set up a server for you. It needs two things: the project URL and a key. The official docs say exactly where they are:

Supabase docs: the API URL is under Integrations > Data API, the API Keys under Settings > API Keys
Official docs (captured 2026-11-18): URL under Integrations › Data API, keys under Settings › API Keys.
  1. Project URL: Dashboard, Integrations › Data API.
  2. Key: Dashboard, Settings › API Keys (use the anon / publishable key for the front end; the service role key stays server-side only).
  3. Put the URL and key in your project's .env, then paste the prompt below into Claude Code or Cursor.
Prompt for Claude Code / Cursor (replace the [] parts)
I want to build a [habit tracker] app with Supabase as the backend. The project URL is [https://your-project.supabase.co] and the anon key is in .env as SUPABASE_ANON_KEY (never print it). Please:
1. Create a habits table (columns: id, user_id, name, created_at) with RLS on, so users can only read and write their own rows
2. Add email sign-up and login
3. Build one page that adds, lists and deletes habits
Show me each step working before starting the next.

05Free plan numbers and limits

Reel frame: the Free plan card on the laptop with $0, 500 MB database size and 50,000 monthly active users marked
Reel frame: the free plan's numbers, read straight off the official pricing page.
  1. $0/month, unlimited API requests.
  2. 500 MB database (Shared CPU, 500 MB RAM).
  3. 50,000 monthly active users.
  4. 1 GB file storage, 5 GB egress (plus 5 GB cached egress).
  5. Community support.

The limits are on the same page: free projects are paused after 1 week of inactivity, and you can have at most 2 active projects.

Reel frame: the pricing page small print in a paper browser, paused after 1 week, 2 projects, next to Pro backups
Reel frame: paused after a week unused; daily backups sit in the Pro column.
Supabase docs, Database Backups: automatic backups only for Pro, Team and Enterprise projects
Official docs (captured 2026-11-18): automatic backups are for Pro, Team and Enterprise projects only.

06Good to know

  1. The free plan has no automatic backups. The official docs recommend that free-tier projects export their data regularly with the Supabase CLI's db dump and keep a copy elsewhere.
  2. A week without traffic pauses the project; one click in the Dashboard restores it, but the app is down while it's paused.
  3. At most 2 active projects on the free plan. Pause or delete practice projects when you're done.
  4. Upgrade to Pro only once real users arrive (from $25/month: 100,000 monthly active users, 8 GB disk, daily backups kept for 7 days).
  5. The service role key is a master key to your database: server-side only. Front ends and AI tools use the anon key, with RLS switched on.
  6. Numbers and prices are as shown on the official pricing page on 2026-11-18 and may change; check supabase.com/pricing again before upgrading.

Sources

Related guides