How we launch at Supabase

Summary

Following their participation in YCombinator, Supabase sought a structured method to maintain product momentum and recreate the urgency of an accelerator internally. The team established Launch Week, a quarterly shipping sprint using a fixed-timeline and flexible-scope model where a major feature or announcement releases each day for a week. Each cycle begins with a broad distributed planning session that maps high-level goals and generates ideas, followed by execution and finely scheduled launch days covering coordinated social media, blog posts, and community engagement. Following the launch, team members transition into maintenance mode and downtime to handle support, bug fixes, and open-source contributions. Finally, a structured retrospective evaluates successes, failures, and process relevance before carrying lessons into the next planning meeting.

Context

After graduating from YCombinator, Supabase faced a drop in external pressure and needed an internal framework to sustain rapid product development, user acquisition, and momentum across a distributed team.

Approach / What changed

Supabase implemented Launch Week, setting a quarterly deadline with a fixed timeline and flexible scope to ship one major feature per day for a week. The cycle incorporates cross-functional visual planning, detailed minute-by-minute execution schedules across channels, post-launch downtime for maintenance, and a mandatory retrospective.

Takeaways

• Adopting a fixed-timeline, flexible-scope launch model helped recreate accelerator momentum and supported a 47% month-on-month increase in managed databases over 18 months.
• Planning cycles start with a whole-company whiteboard session across 12 countries to ensure engineers and marketers align on business goals before selecting features.
• Launch weeks are followed by deliberate downtime and maintenance mode to manage support surges, bug fixes, and community pull requests sustainably.

Related reading

• Supabase · Nov 7, 2021

  Supabase Beta October 2021

  Supabase announced its October 2021 beta release, introducing three new authentication providers for Slack, Spotify, and MessageBird phone logins. The platform rolled out database multi-schema support, enabling users to browse different database schemas directly within the Dashboard interface and query them through the PostgREST API after enabling schema access. Documentation and instructional resources were expanded to cover PostgreSQL functions, authentication server-side functions, RedwoodJS quickstarts, self-hosting architectures, and production readiness checklists. In addition to ecosystem releases such as supabase-py v0.0.3, nuxt-supabase v2.2.1, and vue-supabase v2.2.3, the project reached over 21,268 GitHub stars. The team also announced Launch Week III: The Trilogy, set to begin on November 29th on Discord.

  Paul Copplestone

• Supabase · Mar 28, 2022

  Community Day

  Supabase initiated its Launch Week with Community Day, announcing a series of ecosystem updates, security integrations, and open-source contributions. Through a partnership with GitHub, secret scanning now detects exposed Supabase service role API keys and automatically revokes them to prevent unauthorized database access. The pre-release of PostgREST version 10 introduces arrow operator queries for composite types and array elements, structured PostgreSQL-compliant error messages, and automated recovery from Linux EMFILE conditions. Authentication features expanded with four community-contributed OAuth providers, two phone providers, email one-time passwords via verifyOTP, and framework-specific supabase-auth-helpers starting with Next.js and Nuxt. Finally, Supabase launched a partner gallery powered by Postgres Full Text Search alongside educational courses and an upcoming ten-day virtual hackathon.