Supabase just raised $30M, bringing our total funding to $36M. How will we spend this? Read on to find out.
We're growing fast
From the outside, you can see that we're growing fast. To solidify some of the numbers with internal metrics:
As of September, we've launched over 50,000 databases. This is only on our hosted platform - it doesn't include our open source offering, because we don't add telemetry. Active databases are growing 35% per month.
As of September, over 40,000 developers have signed up to Supabase from some of the world's leading companies. Because of the versatility of Postgres, they're building everything from counter-fraud systems for Fintech to digital platforms powering 200,000 users.
Supabase has been in GitHub's top-15 fastest growing open source startups for five consecutive quarters, and our Discord has grown to nearly 4000 members since launching just 3 months ago. Our growth is all organic.
About the round
Supabase is an ambitious project. Firebase, to their credit, is a very well-developed platform which offers a lot of functionality. Building an alternative is a bit like launching five different startups at once.
That said, our approach has been clear from the start: we don't want to re-invent the wheel. We want to leverage existing open source products wherever we can, improving them by up-streaming changes and employing maintainers (PostgREST, PostgreSQL). This model is the real promise of open source, and we've been lucky to have investors who have backed our approach since the start - Y Combinator, Mozilla, and our lead investor, Coatue.
Because of their conviction in Supabase, Coatue doubled down on their Seed investment to lead our Series A. We're extremely excited to welcome Caryn Marooney to our Board.
Joining the round
We've had a number of new investors join the round, this time a lot of operators and partners:
- Elad Gill
- Tom Preston-Werner (GitHub cofounder)
- Solomon Hykes (Docker cofounder)
- Alex Solomon (PagerDuty cofounder)
- Guillermo Rauch (Vercel founder)
- Kurt Mackey (Fly cofounder)
- Chris Nguyen (LogDNA cofounder)
- Tod Sacerdoti (Pipedream Founder)
- Alana Anderson (Base Case Capital)
- Astasia Myers (Quiet Capital)
- (and more)
Our early positioning is an "open source Firebase alternative" but you might be surprised to learn that this is a small part of the Supabase vision.
Firebase is arguably one of the best tools in the world for building new products, but it has a flaw: scalability.
Phase 1: Start with scalability
The term "open source Firebase alternative" is becoming popular now, and we are often asked: how are we different?
Simple. Supabase has smuggled scalability into the product, perhaps without you noticing. Every Supabase project is a full Postgres database. It's not "Postgres compatible", it's not "built on top of", and we don't abstract it. If we did, your applications would face the same scalability issues as Firebase.
Supabase simply makes Postgres easy to use - hopefully easier than any other database platform you've ever used.
We plan to make Postgres the default database for every developer in the world. How do we do that? By making Postgres both easy (Phase 2: tooling) and scalable (Phase 3: Cloud-Native Postgres).
Phase 2: Postgres Tooling
User-facing applications usually require tools beyond just a database and frontend framework:
- APIs: to provide access to your database from untrusted systems.
- Authentication: for users sign ups.
- File Storage: for large images and media.
Supabase makes all of this easy. Beyond the database we offer Auth, RESTful and Realtime APIs, a Storage system for large files, and a bunch of other tools - all wrapped up into a simple-to-use Dashboard.
And this is where Supabase really differentiates itself: by doing less. All of these features build on top of PostgreSQL's existing functionality.
- Row Level Security: restrict user access to data and files using Postgres Policies.
- Realtime data streams: subscribe to database changes using the logical replication stream.
- Function Hooks: trigger external systems using Postgres triggers and our async request extension.
- RESTful APIs: query your database tables and functions over HTTP, using PostgREST.
Phase 3: Cloud-native PostgreSQL
PostgreSQL was created over 30 years ago, and it's one of the safest and most reliable databases in the world.
But modern developers are becoming accustomed to cloud-native services with several characteristics:
- Automatic scaling.
- Low latency anywhere in the world.
- Billing based on usage.
PostgreSQL is still catching up to the modern cloud environment in some areas. What does a Cloud-native PostgreSQL look like?
- Branching: developers should be able to "fork" a database at any point. This is particularly important for Jamstack developers who run deployments for every Git branch.
- Scalable storage: storage should grow and shrink without the user needing to provision more space themselves.
- Distributed: An entire fleet of databases, distributed around the world, should feel like a single database (and even better if all nodes can accept read/write workloads).
- Ephemeral compute: developers don't want to be charged for a database which isn't doing anything. Likewise - if they are running huge computation then the database should scale up seamlessly, and scale down to zero when it's unused.
- Snapshots and time-travel: developers should be able to roll back to any point in time, or take a copy of their database with just a click of a button.
This is the future of Supabase - a platform to power your transactional workloads: no matter how big or small; no matter the use-case. We're building a cloud-native Postgres platform.
We have a track record of hiring open source maintainers, PostgREST is maintained by a Supabase developer, one of our first hires over a year ago. We've recently added another developer with the explicit goal of working within the PostgreSQL community.
If you want to help us build the future of cloud-native Postgres, join us: https://about.supabase.com/careers/postgres-experts