Supabase

What it is

Supabase is an open-source Firebase alternative built on Postgres. You get a real Postgres database, plus auth (with social login, magic links, SSO), file storage, edge functions, realtime subscriptions, and a REST/GraphQL API auto-generated from your schema. It's a backend-as-a-service that takes Postgres seriously.

Who it's for

• Teams building full-stack apps who want to avoid writing auth from scratch
• Developers who want Firebase convenience but with SQL instead of NoSQL
• Projects that need realtime features (presence, live feeds) without custom WebSocket infra
• Open-source advocates who want to self-host their backend
• NOT for: apps that only need Postgres — Neon is cheaper ($19/mo vs $25/mo) and doesn't pause
• NOT for: teams new to Postgres who'll misconfigure Row Level Security policies

The good

The auth system is the best part. Row-level security (RLS) policies in Postgres, built-in user management, social providers, and magic links. This is the best out-of-the-box auth-plus-database combo for most apps.

Auto-generated APIs do what they promise. PostgREST turns your schema into a REST API. The JS client library is polished and reactive. Realtime is built on Postgres LISTEN/NOTIFY via websockets, no separate infrastructure required.

Actually open source. You can self-host the entire stack. This isn't "open core": the full product is Apache 2.0. The self-hosting path is documented and works.

Dashboard and Studio are well-built. The table editor, SQL editor, and log viewer are among the better tools for working with Postgres data. Supabase Studio would be a worthy product on its own.

The bad

Free tier pauses after 1 week of inactivity. This is a dealbreaker for side projects you revisit occasionally. Resume time is 15 to 30 seconds, which means users hit a slow cold start. Neon's free tier doesn't pause.

Pro tier at $25/mo per project. If you have multiple projects, costs stack fast. Neon's equivalent is $19/mo, and that's for pure Postgres without the bundled features you might not need.

RLS is powerful but sharp. Misconfigured row-level security policies are a real security risk that's easy to get wrong. The "all users can read everything" footgun is documented but still traps people.

Vendor lock-in risk beyond the database. The auth system, storage, and realtime are all Supabase-specific. Pure Postgres queries migrate fine, but your auth tables and storage references don't.

Onboarding experience

Dashboard-first and approachable. Creating a project and running your first query takes under 10 minutes. The auto-generated REST API is instant. Auth setup is self-serve but requires understanding Row-Level Security before you ship. This introduces a real learning curve for teams new to Postgres policies. Local development via supabase start is well-documented and reproducible. No sales call to evaluate; the free tier activates immediately.

Support reality

Free tier gets community Discord and GitHub Discussions, both active and monitored by the team. Pro tier includes email support with a 24 to 48 hour response time. Enterprise unlocks dedicated Slack. Supabase has one of the more responsive OSS communities in dev tools; most common issues get answered in Discord before a ticket is needed.

Migration and lock-in

Postgres data migrates easily with pg_dump. The database itself isn't the sticky part. The lock-in is everything built on top: auth users stored in Supabase-specific schema, storage bucket references, RLS policies, and Realtime subscriptions. Moving the database alone is a week's work. Moving the full backend platform is a multi-week project requiring schema rewrites and a careful auth migration.

Pricing reality

Free: real for development and new projects, but the pause-on-inactivity is a genuine production risk. Pro at $25/mo per project: reasonable for a single production app. If you only need Postgres, you're paying $25 for features you don't use. Neon costs $19/mo and doesn't pause. Use Supabase when you're actually using the auth, storage, or realtime features.

Vendor signals

• Fully open source (Apache 2.0). The entire platform is self-hostable.
• Public GitHub roadmap with issues and milestones visible
• Series C funded; stable company with no near-term acquisition signals
• Transparent about incidents; status page is kept current
• No pricing surprises since launch; free tier terms unchanged

Verdict

Supabase is the right choice when you're building an app and want the full backend (auth + db + storage + realtime) in one place without stitching it together. If you only need Postgres, Neon is cheaper, faster, and doesn't pause on you. The distinction matters.

Pick Supabase when the bundled platform saves you from wiring auth, storage, and realtime separately. Pick Neon when you just need a database. Don't let the Supabase free tier become a production footgun. Upgrade to Pro ($25/mo) before you ship anything that users will hit cold.

Would I recommend a colleague start here? Yes, if they're building a full-stack app. No, if they only need a database.