Supabase Series B

Summary

Supabase announced an $80 million Series B in May, bringing total funding to $116 million, and reported growth to more than 150,000 hosted PostgreSQL databases and 110,000 developers. Community metrics also increased, with Discord membership rising from 4,000 to 8,000, Twitter followers from 18,000 to 37,000, and GitHub stars from 19,000 to 36,000. The round is led by Felicis, with Coatue, Lightspeed, and Square Peg Capital joining, while Supabase describes its open-source support through contributor payments, maintainer hiring, sponsorship, and community collaboration. The company is moving into its third phase, focused on cloud-native PostgreSQL capabilities including branching, scalable storage, distribution, ephemeral compute, snapshots, and time travel. It invested $500,000 in OrioleDB and hired a developer to work on it, while stating that OrioleDB is not currently used on the Supabase platform and that the company will not run a PostgreSQL fork.

Context

Supabase is revisiting the plans outlined in its Series A post to hold itself accountable for earlier promises. It is moving into Phase 3, focused on cloud-native PostgreSQL, with goals including branching, scalable storage, distributed databases, ephemeral compute, and snapshots and time travel.

Approach / What changed

Supabase raised a Series B led by Felicis and is supporting the open-source ecosystem through contributor payments, maintainer hiring, sponsorship, and community collaboration. It invested $500,000 in OrioleDB and hired a developer to work on it, while keeping OrioleDB off the Supabase platform and avoiding a PostgreSQL fork.

Takeaways

• Supabase reported more than 150,000 hosted PostgreSQL databases and 110,000 developers, up from over 50,000 databases and 40,000 developers at Series A.
• Supabase has paid more than $80,000 to contributors and maintainers through its Open Collective, covering activities such as library maintenance and Discord moderation.
• OrioleDB currently requires about 1,000 lines of PostgreSQL core modifications; its goal is to upstream those changes so developers can build storage extensions with lower-level access to PostgreSQL storage capabilities.

Related reading