Supabase

Three strengths

• Full database access. Supabase doesn't hide the database behind its own layer; you can access it and use it with full privileges. 1
• A ready-made back end. Authentication, file storage and real-time messaging come ready-made beside the database. 3
• Easy to move. Its cloud offering is compatible with its self-hosted product, and it uses standards such as pg_dump and CSV files to avoid lock-in. 1

What it is

Behind every app's screens sits a back end: the part that stores the data, checks who's signing in, keeps files and applies the rules. Building all of that from scratch takes time. Supabase gives developers a ready-made back end built around a PostgreSQL database, and it's open source. 2 It chooses open source tools that are scalable and makes them approachable. 1

The database is the core: "Postgres is the core of Supabase". 1 Around it sit the other pieces most apps need.

Auth handles sign-ups and logins, including sign-in with providers such as Apple, GitHub and Slack. 3 Storage keeps and serves files. 3 Realtime sends messages between connected users through WebSockets. 3 Edge Functions run custom business logic in TypeScript, on servers distributed around the world. 3 A REST API, the standard way for an app to ask a server for data, is generated automatically from the database. 3 And Row Level Security lets you write the rules about who can see which record as Postgres policies, so the protection sits next to the data and not only in the app. 3

It's built to be a quick start that can grow. Its tagline is "Build in a weekend. Scale to millions.", and it reports 16+ global regions, 40+ preinstalled Postgres extensions and SOC 2 Type 2 compliance. 2 Supabase is a young company: Y Combinator, the start-up accelerator, lists it as founded in 2020 by Paul Copplestone and Ant Wilson, in its Summer 2020 batch. 5 Its code is published under the Apache 2.0 licence, 4 and 6% of developers surveyed in 2025 said they use it. 6

We value it for one reason above the rest: it's standard PostgreSQL underneath. If a project outgrows the platform, the database moves with it, and your data doesn't need rebuilding. 1

How we use it

We've used Supabase, and because it's standard PostgreSQL underneath, our PostgreSQL skills carry straight over. The place we expect to meet it most is the prototype. Many ideas now start as a quick working prototype, perhaps put together with AI coding tools, with Supabase handling sign-in and the database. That's a sensible way to test an idea fast. When you bring that prototype to us to build properly, we'd look at two paths, and the choice depends on how hands-on you want to be with the database underneath.

• Keep Supabase and build it out. We'd set up and size your Supabase project for real use, tidy up the data and the access rules, and build the rest of the software around it. This suits you if you're comfortable keeping a managed platform at the centre of your product.
• Move to a PostgreSQL instance. Because Supabase is standard PostgreSQL, your data can move to a properly provisioned PostgreSQL database set up as part of your build. This suits you if you want full control, or want the database off your plate entirely. 1 We've helped with PostgreSQL migrations before, and who runs the new database depends on what you need and how your IT or data team is set up.

Either way, you keep what the prototype proved and get software that's ready for real customers.

In Software Development, that's where a prototype becomes tailored, scalable software, and it supports the faster time to value our agile approach aims for. In Solution Architecture, choosing between the two paths is a design decision, so the technology lines up with what you need and how much of it you want to look after. For the database itself, see our article on PostgreSQL.

References

1. Supabase, "Architecture", Supabase Docs. https://supabase.com/docs/guides/getting-started/architecture (accessed 28 October 2026)
2. Supabase, "Supabase | The Postgres Development Platform", supabase.com. https://supabase.com (accessed 28 October 2026)
3. Supabase, "Features", Supabase Docs. https://supabase.com/docs/guides/getting-started/features (accessed 28 October 2026)
4. Supabase, "supabase/supabase", GitHub. https://github.com/supabase/supabase (accessed 28 October 2026)
5. Y Combinator, "Supabase", ycombinator.com/companies. https://www.ycombinator.com/companies/supabase (accessed 28 October 2026)
6. Stack Overflow, "2025 Developer Survey: Technology", survey.stackoverflow.co, 2025. https://survey.stackoverflow.co/2025/technology (accessed 28 October 2026)