Supabase raised $80M in May, bringing our total funding to $116M. This comes one year after our Series A, and so we're revisiting the plans we outlined in our Series A blog post tk hold ourselves accountable for the promises we made.
Where we've been
We shared a few metrics in our Series A post. Since then we've grown a lot.
At Series A we'd launched over 50,000 PostgreSQL databases (on our hosted platform).
As of today, we've launched over 150,000 PostgreSQL databases.
At Series A we had 40,000 developers.
Today we have more than 110,000 developers.
We've seen a lot of growth in our community:
- Discord: 4000 → 8000
- Twitter: 18,000 → 37,000
- GitHub Stars: 19,000 → 36,000
Supabase vs React (GitHub stars)
It's early days but we're doing well for a database company.
About the round
Our Series B is led by Felicis, an amazing team of people who support the long-term approach we're taking to build an open source business.
Supabase is a collaborative company. We aim to support existing open source tools before developing anything ourselves. When we do develop ourselves, we try to include our community as maintainers in a variety of ways. We've been experimenting with several models to support the open source ecosystem.
To date, we've paid over $80,000 to contributors and maintainers through our open collective. This is for everything from maintaining our libraries to moderating our Discord.
We've had some amazing open source stories like Isaiah, a 15-year old who started contributing after his school day. Or Olyno, who created a Supabase Discord on their own initiative and is now an official moderator. Or Zernonia, who created madewithsupabase.com which is now central to every Supabase Hackathon.
PostgREST is a automatically generate RESTful APIs from your Postgres schema, and it's one of the core pieces of the Supabase stack. As well as being a gold sponsor, Supabase hired Steve, the maintainer of PostgREST in 2020 to work primarily on PostgREST. This model has been surprisingly successful and we hope that more companies will consider this approach for supporting open source projects.
Elixir Type support
Elixir is a functional programming language that enables huge horizontal scalability. We use it at Supabase for our Realtime engine and our logging infrastructure. Recently announced by José at ElixirConf EU, the Elixir team is investigating a type system. Supabase is sponsoring this research and development.
Functions was one of the most demanded features of Supabase, and we explored a huge number of options before settling on Deno. Deno checked all the boxes - most important for us was their approach to open source. Both Supabase and Netlify now support Deno Edge Functions, and we hope that our backing will help convince others to adopt the Deno runtime too.
A teaser for next week's Launch Week - a few months ago we hired Michel, the maintainer of pgsodium, to re-think what a modern database encryption system and database secrets management would look like. Since then he has released two major versions of pgsodium: 2.0 and 3.0 to support Transparent Column Encryption.
Founder Chat: Paul Copplestone and Ant Wilson discuss the several ways we give back to the community, and what Open Source means for Supabase.
Where we're going
In our Series A post, we outlined our plans for Supabase in three phases:
We're now moving into Phase 3, with the same goals that we outlined in 2021:
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.
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.
We have a lot of work ahead of us, but we're excited to announce one of the ways that we're supporting the community is through our investment into OrioleDB.
While it currently requires some modifications to the Postgres core (about 1000 lines), the goal is to upstream those changes so that anyone can build a Storage extension like OrioleDB. Giving developers low-level access to the underlying storage capabilities of Postgres will unlock a slew of new capabilities in Postgres. You can read more about OrioleDB's plans for Snapshots and Branching in their wiki.
Supabase has invested $500K into OrioleDB to support their efforts, and we've hired a developer at Supabase to work full-time on OrioleDB, with more to come. Apply here if you're interested in working on Postgres full time.
Note: we are not running OrioleDB on the Supabase platform. Our promise to you is “no vendor-lockin”, and therefore we will never run a fork of Postgres. In the future, if all of the OrioleDB core changes are up-streamed, then we might offer it on the platform.
If you want to try out OrioleDB today, you can switch the Postgres docker image to OrioleDB in the self-hosted setup.
Achieving the goals we've outlined above will be a long journey requiring collaboration from many companies besides Supabase.
If you want to help build the future of cloud-native Postgres, join us at Supabase. If you're already working towards the same goals, reach out and let's do it together.
By the way
Launch Week 5 is starting Monday 15th August, we will launch one new feature every day for a week. If you want to follow along check out supabase.com/launch-week.