Supabase Dot Com

Summary

Supabase announced a migration of its primary website from supabase.io to supabase.com over the upcoming week. User API endpoints will remain unchanged on supabase.co, requiring no configuration adjustments for active applications. The company originally selected supabase.io as a meme-inspired placeholder after releasing a Postgres Realtime engine on GitHub in 2019 and failing to find an available dot com name. Following advice from Y Combinator to secure a dot com address, the founders bypassed domain brokers charging percentage fees and negotiated directly with the domain owner, whose business address was located one hundred meters from the founder's home. The migration updates public website destinations while preserving existing developer infrastructure unaffected.

Context

Supabase initially adopted the domain supabase.io as a placeholder while building an open source company around Postgres, but Y Combinator advised that startups should secure the dot com version of their name.

Approach / What changed

Instead of hiring a percentage-fee domain specialist, Supabase investigated the owner listed on the supabase.com website, discovered the company address was located 100 meters from the founder's home, and directly negotiated a purchase.

Takeaways

• Supabase migrated its primary website from supabase.io to supabase.com while maintaining API endpoints on supabase.co to prevent breaking changes for existing users.
• The company originated after releasing a Postgres Realtime engine on GitHub at the end of 2019 following a migration from Firebase to Postgres.
• Rather than hiring domain specialists who charge a percentage of the purchase price, Supabase negotiated directly with the owner after discovering their office was 100 meters away.

Related reading

• Supabase · Apr 2, 2021

  PgBouncer is now available in Supabase

  Serverless JavaScript frameworks and developer tools frequently establish separate database connections during bursty traffic, rapidly exhausting PostgreSQL connection limits in the absence of traditional middleware. To resolve connection surges, Supabase integrated the open-source connection pooler PgBouncer directly onto the PostgreSQL server across all newly created projects. Rather than increasing the total number of connections PostgreSQL can open, PgBouncer recycles open connections and queues excess requests until active connections become available. Developers can manage pooling through the dashboard across Session, Transaction, and Statement modes, with Transaction mode recommended for serverless functions despite disabling session features like prepared statements. The default pool size is initially configured to 15 connections.

  Angelico de los Reyes

• Supabase · Sep 3, 2020

  Supabase Alpha August 2020