The Postgres Company That Let AI Write the Signups

In April 2020, a few months after two friends launched a database company, the entire product amounted to eight hosted databases. Not eight thousand. Eight. Supabase was a rounding error with a landing page and a bold claim - that developers deserved an open-source version of Firebase, built on a real relational database. Six years later, roughly 10 million developers build on it, AI coding tools launch most of its new projects, and in June 2026 investors valued the company at $10.5 billion. The graph that made people stare wasn't the valuation. It was the adoption curve underneath it.

The pitch has always been unusually plain. Supabase gives you a dedicated PostgreSQL database for every project, then wraps it with the things you would otherwise have to bolt on yourself: authentication, file storage, realtime subscriptions, serverless edge functions, auto-generated APIs and vector search for AI apps. One project, one login, no servers to patch. The unglamorous promise is that you never have to assemble the plumbing again.

01 / The betWhy "just Postgres" turned out to be the whole strategy

Most backend startups try to invent a cleverer database. Supabase did the opposite. Co-founders Paul Copplestone and Ant Wilson decided the database was already solved - it was PostgreSQL, the 30-year-old open-source workhorse - and the real problem was that using it well took too much glue code. So they built the glue and gave developers plain SQL, row-level security, foreign keys and every Postgres extension, unchanged. If you outgrew the managed service, you could pick up the open-source stack and self-host it. No rewrite, no ransom.

That refusal to reinvent looked conservative in 2020. It reads very differently now. When the AI embedding boom arrived, Supabase had already shipped the pgvector extension by default, which meant developers could store relational data, authenticate users and run vector similarity search in one managed service. The company didn't pivot into AI. Postgres simply happened to be standing where the puck went.

02 / The customersFrom weekend projects to the companies that build tools for a living

The user base runs the full spread. On one end are solo builders spinning up a free-tier database at midnight; on the other are engineering teams at Mozilla, GitHub, 1Password, Figma, Replit and Cursor running production workloads. There is a certain tell in that list: the companies that make developer tools tend to build on Supabase themselves. In 2025 alone, 15.1 million databases were created on the platform.

Then came the twist nobody wrote into the plan. As AI coding tools like Cursor and Replit matured, they needed somewhere to put the apps they generated - a database, auth, storage, all provisioned instantly with a free tier. They reached for Supabase. By 2026 the company reported that more than 60% of new databases were launched by AI tools, and database creation was up 600% year over year. When machines write the code, they also pick the backend, and they kept picking this one.

03 / The problemThe two things every app needs, and nobody wants to build twice

Strip a modern web or mobile app down and you find the same chores every time: a place to store data, a way to sign users in, somewhere to keep their files, and some live updates so two people see the same thing at once. Historically you either wired these together from a dozen services or handed them to a proprietary platform that made leaving expensive. Supabase's answer is to hand you all of it, pre-assembled, on infrastructure you can walk away with.

The convenience has a philosophy attached. Because the whole stack is open source and self-hostable, the switching cost that usually defines this category is inverted - the exit door is always unlocked, which is precisely why people stay.

04 / The rivalFirebase taught the lesson; Supabase collected the tuition

The obvious comparison is Google's Firebase, and Supabase has never run from it - the phrase "open-source Firebase alternative" is practically stitched into the brand. But the differences are real. Firebase is proprietary and built around a NoSQL document store; Supabase is open source and built on relational SQL. Firebase bills per operation - every read, write and delete - which produces the horror story of a viral app and a surprise invoice. Supabase bills on resources consumed, so costs stay closer to predictable.

The other rivals are newer-generation Postgres platforms like Neon and PlanetScale, plus the incumbents' own managed databases. Supabase's counter is scope: not just a database, but the full backend around it, kept open.

05 / The moneySix rounds, $1.2 billion, and a valuation that would not sit still

The funding history reads like a time-lapse. An $80 million Series C in September 2024 valued the company under a billion. A $200 million Series D lifted it to $2 billion. Then, in October 2025, a $100 million Series E co-led by Accel and Peak XV put it at $5 billion - and just eight months later, a $500 million Series F led by Singapore's GIC doubled that to $10.5 billion. Stripe invested again; Salesforce Ventures joined. Total raised now tops $1.2 billion.

A telling detail sits in the fine print: Supabase reserves an allocation in its rounds so community members can co-invest alongside institutional VCs. The people who file the GitHub issues get a chance to hold the stock.

06 / The house styleFully remote, open by default, options you can actually keep

Supabase runs as a fully remote team of around 410 people spread across more than 50 countries, with standardized global compensation so an engineer's pay doesn't hinge on their postcode. The equity terms are unusual on purpose: employees have up to 10 years to exercise their stock options - most startups give 90 days - and can sell up to a quarter of their vested shares in each funding round. For a company built by and for a distributed community, the internal mechanics mirror the external pitch.

07 / The positionWhere a Postgres company sits when the software writes itself

The market Supabase occupies - backend-as-a-service - is old enough to have a reputation for lock-in and surprise bills. What changed is the buyer. It used to be a human developer choosing tools deliberately. Increasingly it's an AI agent scaffolding an app in seconds and needing a backend it can provision without a sales call. Supabase's open, instant, free-to-start, Postgres-native stack turned out to be shaped exactly for that customer, which is a large part of why the valuation moved the way it did.

In 2026 the company also shipped Multigres, an open-source high-availability layer for Postgres, and continued work on connection pooling and reliability - the unglamorous scaling problems that decide whether a viral app survives its own success. None of it strays from the original bet. The company still thinks the database was solved in the 1990s. It just keeps building everything around it, in the open, and letting other people's software do the signing up.