Alpha Launch Postmortem

Summary

An unexpected viral submission on Hacker News prompted sudden alpha traffic for Supabase, attracting 30,000 visitors and over 1,400 signups in one week. The surge strained initial infrastructure, which initially relied on a single server running Docker Compose for middleware and Digital Ocean for customer databases. System bottlenecks emerged rapidly, including hit limits on Digital Ocean droplet counts, frequent physical server faults, and a three-hour provisioning outage when Cloudflare reached its 1,000-subdomain limit. In response, the team migrated middleware to multiple globally load-balanced ECS clusters via AWS Global Accelerator. Supabase also transitioned 1,800 servers from Digital Ocean to AWS t3a instances, nearly halving database startup times from 90 seconds to 50 seconds.

Takeaways

1. 1

   Hitting Cloudflare's 1,000-subdomain limit caused a three-hour outage because account upgrade permissions were restricted solely to the account owner, preventing available team members from resolving it immediately.

2. 2

   Running middleware via Docker Compose on a single 4-CPU, 8GB RAM Ubuntu server unexpectedly handled the initial viral traffic before being transitioned to multiple ECS clusters using AWS Global Accelerator.

3. 3

   Migrating 1,800 database servers from Digital Ocean to AWS t3a instances reduced Postgres database startup times from approximately 90 seconds to 50 seconds.