Insights / October 25, 2026

What is Supabase? A plain-English guide for founders

Supabase is an open-source backend platform built on Postgres. Each project gets a full Postgres database plus sign-in (Auth), file storage, live updates (Realtime), server-side functions (Edge Functions) and APIs generated automatically from your tables, so an app can store data and sign users in without anyone writing a server.

If your app was built with Lovable or Bolt, it very likely runs on Supabase, even if you never opened a Supabase account. Knowing the parts tells you where your data lives, what your security depends on and what drives your bill.

How Supabase works

Most apps put a server between the browser and the database. The browser asks the server, and the server decides what each user may see.

Supabase removes the server you’d otherwise write for everyday reads and writes. It turns your database into an API, so the app’s code in the browser queries tables directly with a public key. Rules inside the database, called row-level security, decide which rows each signed-in user can read or change. Anything that needs a secret, like charging a card or calling OpenAI, runs in an Edge Function or on your own backend.

Each hosted project is its own Postgres server. That’s why Supabase bills compute per project, by the hour, and why your data is ordinary Postgres you can export with standard tools.

The building blocks, in plain English

These are the products listed in Supabase’s docs, with what each one usually does in an app.

Part What it is What it does in a typical app
Database A full Postgres database, with extensions Stores users’ profiles, orders, projects, messages: everything the app keeps
Auth Email and password, magic links, OAuth (Google, Apple and others) and phone sign-in The sign-up and login screens, password resets, knowing who is signed in
Data API REST and GraphQL APIs generated from your tables Lets the app read and write rows without custom backend code
Storage File storage with access rules, compatible with S3 tools Profile photos and uploads. Private files are shared through signed links that expire
Realtime A WebSocket service for database changes, Broadcast messages and Presence (who’s online) Chat, dashboards that update on their own, “3 people viewing”
Edge Functions Server-side TypeScript that runs on Deno Stripe webhooks, calls to AI APIs with a secret key, sending email
Cron and Queues Scheduled jobs and message queues inside Postgres Nightly cleanups, reminder emails, background work
AI and Vectors Storage and search for embeddings (pgvector) Semantic search, “chat with your documents” features

There’s also a web dashboard, Studio, for browsing tables, running SQL, managing users and reading logs.

How Lovable Cloud and Bolt use Supabase

Lovable Cloud. Lovable’s docs say its built-in backend “utilizes Supabase’s open-source foundation”: a database, auth, storage, realtime and functions. Lovable manages it and bills it in Lovable credits, and you don’t get a Supabase dashboard or account for it. You can connect your own Supabase project instead, but moving an existing Cloud project is a manual migration. Our guide to Lovable Cloud vs Supabase covers when that’s worth it.

Bolt. Supabase’s launch post says every Bolt Cloud project that needs a backend is powered by Supabase. Inside Bolt it’s called Bolt Database: tables, authentication, file storage and server functions, created automatically when a project needs them. On Pro and Teams plans you can start a new project on your own Supabase project, or claim an existing Bolt Database into your own Supabase account.

Either way, the keys and row-level security below apply to your app; plans and limits are set by Lovable or Bolt, not Supabase.

The two keys, and why row-level security matters

Every Supabase project has two kinds of API key:

  • The publishable key (older projects call it the anon key). It’s meant to ship in your web or mobile app, and Supabase says it’s safe to expose. Requests made with it are limited by row-level security.
  • The secret key (the older version is the service_role key). It bypasses row-level security completely, so anyone holding it can read and change every row. It belongs only in server code. Supabase rejects the new secret keys when they’re sent from a browser, but a legacy service_role key pasted into frontend code still works for whoever finds it.

Supabase is phasing out the legacy keys in favor of the new ones. Creating new keys doesn’t disable the old ones; you turn those off yourself in Settings → API Keys.

Because the publishable key is public, row-level security is the only thing between one user and everyone else’s data. A table with security switched off, or a rule that just says true, can be read by anyone with your app’s key. It’s the first thing we check in every AI-built app. Our guide to Supabase row-level security explains how to check yours.

What Supabase costs

The Free plan gives you two active projects, a 500 MB database and 50,000 monthly active users, and pauses projects after 7 days of low activity. Paid plans start at $25 a month for Pro and $599 for Team, according to Supabase’s pricing page. Paid plans include $10 of monthly compute credit, enough for one small project; beyond that you pay hourly compute for each project and any usage over the included quotas.

For a growing app, the bill usually moves with usage, especially Realtime messages and egress (data sent out), rather than with the database. Our Supabase pricing guide breaks down every line from real bills, and Supabase free tier limits covers what you can run for nothing.

What Supabase is good at

  • It’s real Postgres. You get SQL, relations between tables, transactions and the whole Postgres ecosystem. Any Postgres tool can connect to your own Supabase project, and leaving is a data migration, not a rewrite of your data model.
  • It’s fast to build on. Sign-in, file uploads and a typed API exist from day one, which is why AI app builders use it.
  • Security lives in one place. Row-level security rules apply to every request made with the public key, whether it comes from your app, a script or someone poking at your API.
  • It scales a long way. Compute goes from Micro up to 16XL, and most apps never outgrow it.

Where its limits show up at scale

We build and run production apps on Supabase, including a real-time trading platform and a media delivery app on Lovable Cloud. The limits we see are specific and predictable:

  • Edge Functions are for short, light work. Each one gets 256 MB of memory and 2 seconds of CPU time per request, on every plan. On the media delivery app, ZIP downloads are built by a separate streaming service, and the edge function only coordinates the job. More in Supabase edge function limits.
  • Realtime is billed per delivery. One change sent to 50 listeners counts as 50 messages. The trading platform’s hosted Realtime reached roughly $640 a day before we moved it to our own Realtime server. On the media delivery app, narrowing subscriptions cut the Realtime line by about 90%. See Supabase Realtime pricing.
  • One database per project. Scaling mostly means a bigger compute size, billed every hour. Launch load took the trading platform’s database from Medium to XL in two days, and the lasting fix was in the queries that overloaded it, not more compute.

None of these are reasons to avoid Supabase. They’re reasons to keep heavy work out of Edge Functions and to design live updates around who actually needs them.

Open source and self-hosting

Supabase’s main repository is Apache 2.0 licensed, and it’s assembled from open-source parts: Postgres, PostgREST for the API, its own Auth, Realtime and Storage servers, and a Deno runtime for functions. Supabase’s architecture page lists each component and its license.

You can self-host it with Docker Compose. A self-hosted install runs a single project and leaves out managed features such as branching, managed backups and point-in-time recovery. You also take on security, upgrades, backups and monitoring.

You don’t have to move everything. Because each part is open source, you can run one piece yourself and keep the rest on Supabase. That’s what we did with Realtime for the trading platform: Supabase’s daily cost fell by about 95%, and the database, auth and storage stayed where they were.

How to check what your app runs on

  1. Look for a Supabase URL. Search your code or .env for supabase.co, or for @supabase/supabase-js in package.json.
  2. Find out who owns the project. If it’s Lovable Cloud or Bolt Database, the platform manages it. If it’s your own Supabase account, make sure more than one person can sign in to it.
  3. Check the keys. Only the publishable or anon key should appear in frontend code. Search for service_role and sb_secret_.
  4. Run the Security Advisor in the Supabase dashboard, or your app builder’s security scan, and fix any table without row-level security.
  5. Open the usage page and note your biggest cost line before it grows.

FAQ

Is Supabase a database?

It’s a Postgres database plus the services around it: Auth, Storage, Realtime, Edge Functions and auto-generated APIs. The database is the core: Auth and Storage keep their records in it, and the APIs are generated from its tables.

Is Supabase free?

There’s a free plan with two active projects, a 500 MB database and 50,000 monthly active users, and projects pause after 7 days of low activity. Most live products move to Pro, from $25 a month.

Supabase vs Firebase: what’s the difference?

Supabase uses Postgres, a relational SQL database, and is open source, so you can self-host it or take your data elsewhere. Firebase is Google’s platform built around a NoSQL document database. Our Supabase vs Firebase comparison goes further.

Can I move my app off Supabase later?

Yes. Your data is standard Postgres, so it exports with standard tools. The work is in replacing the services your code calls directly, mainly sign-in, storage and Realtime.


If you’re planning a new product on Supabase and want it built for real users from the start, see our custom software development service.

LET’S TALK.

Book a free 30-minute call with Virgil

Pick a time that suits you. You’ll get a straight answer on what you need, what it should cost and the fastest path to launch.

Loading available times…

Open the calendar in a new tab

Send us your project

Virgil replies personally within one business day.

Book a free strategy call