Building with Supabase
Every Supabase project is a full Postgres database. Around it, Supabase adds authentication, file storage, edge functions, and APIs generated from your schema, so you can work in SQL and still get a hosted backend.
What Supabase Is Good At
- Plain SQL, migrations, and Postgres extensions.
- Row-level security policies decide what each user can read and write.
- Client libraries query the database through the generated APIs.
- Open source, with a self-hosting option.
Common Use Cases for Supabase
- Apps with relational data and reporting queries
- AI features that store embeddings with pgvector
- Multi-tenant SaaS secured with row-level security
Launches Built with Supabase
No launches built with Supabase yet — be the first.
Every launch page on Hauntboard shows its traffic stats publicly. Free listings show the Hauntboard badge and get human review in about 72 hours; paid listings are reviewed within 24 hours.
Frequently Asked Questions About Supabase
Should I choose Supabase or Firebase?
Firebase's Firestore is a NoSQL document database; Supabase is Postgres. If your data is relational or you want standard SQL you can take elsewhere, Supabase is the closer fit.
Is row-level security hard to set up?
You write the policies in SQL. They're powerful but easy to get wrong, so test them as several different users before launch.