Supabase
Supabase is an open-source, Apache-2.0 backend platform — an alternative to Firebase — that gives an application a Postgres database, authentication, file storage, realtime updates, and auto-generated APIs. It can run on Supabase’s cloud or be self-hosted with Docker. Because it is standard Postgres underneath, your data and queries stay portable.
- Replaces:
- Firebase
- Open source:
- Apache 2.0
Supabase in plain terms
Supabase bundles several open-source services around PostgreSQL: an auth service, PostgREST for instant REST APIs, a realtime server, S3-compatible storage, edge functions, and the Studio dashboard. Row-level security policies in Postgres control who can read and write what, which makes it a strong foundation for custom business apps and client portals.
A good fit when…
- Custom apps and portals that need a relational database, auth, and storage from day one
- Teams moving off Firebase who want SQL and fewer surprises in usage-based billing
- Projects where data must stay in a specific region or account (self-hosted)
- Products that may later need to move providers — it is plain Postgres underneath
Choose something else when…
- Teams without operations capacity who want to self-host — many services must be run and upgraded; Supabase Cloud is usually the pragmatic choice
- Apps whose data model is genuinely document-shaped and works well in Firestore already
What running it involves
- Docker Compose running Postgres, Studio, an API gateway, Auth (GoTrue), PostgREST, Realtime, Storage, postgres-meta, Edge Runtime, and Supavisor
- Minimum 4 GB RAM, 2 CPU cores, and 40 GB SSD (8 GB RAM and 4 cores recommended), per Supabase’s docs
- Your own SMTP provider for auth emails
Self-hosted Supabase excludes Logs & Analytics by default and needs manual SMTP setup, according to its docs. Unneeded services can be disabled to reduce resource use.
If you’d rather not self-host
Supabase Cloud lists a Free plan, Pro at $25 per month, and Team at $599 per month, as of September 2026. For most projects, starting on the cloud and self-hosting only when compliance or residency requires it is the sensible path.
Requirements and prices are from the project’s own docs and pricing pages as of September 2026 — see sources below.
Deploying and customizing Supabase
Schema design
A relational data model designed for your app, with migrations under version control.
Row-level security
Postgres policies so each user, client, or tenant can only reach their own data.
Auth flows
Email, magic link, OAuth, and SSO configured to how your users sign in.
Edge functions
Server-side logic for webhooks, payments, and integrations.
Storage and realtime
File uploads with access rules, and live updates where the UI needs them.
Firebase migration
Firestore data remodelled relationally and auth users migrated.
Migrating to Supabase
Moving from Firebase means remodelling Firestore documents into relational tables, migrating auth users, and replacing Firebase SDK calls in the app. The data move is mechanical; the modelling decisions are where the value is, because they determine how easy reporting and new features become later.
Supabase vs Firebase
Supabase vs Firebase compared on data model, pricing model, open source, and lock-in — for teams choosing a backend for a custom app.
Custom Client Portal Development
Custom client portals for document sharing, project status, approvals, invoices, and messaging — branded, secure, and owned by you.
Supabase — common questions
Is Supabase open source?+
What does it take to self-host Supabase?+
Should we self-host Supabase or use Supabase Cloud?+
Can Supabase replace Firebase?+
Sources
The Best Tech Stack for a New B2B Product in 2026
A pragmatic 2026 tech stack for a new B2B product — what to choose for frontend, backend, auth, and hosting to ship fast, stay cheap, and avoid lock-in.
Self-Hosting on AWS: Own Your Software Instead of Renting It
What it means to self-host open-source software on AWS — the benefits, the real responsibilities, and how a managed setup gives you ownership without the headache.
Why API-First Architecture Saves Money Long Term
What API-first architecture means, why it lowers long-term cost and risk, and how building behind your own API layer keeps your software flexible and lock-in free.
Thinking about Supabase?
Tell us what you use today and what you need. We'll tell you honestly whether Supabase fits, and scope it if it does.