惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

爱范儿
爱范儿
H
Help Net Security
Jina AI
Jina AI
T
The Blog of Author Tim Ferriss
宝玉的分享
宝玉的分享
博客园 - 叶小钗
Y
Y Combinator Blog
罗磊的独立博客
大猫的无限游戏
大猫的无限游戏
WordPress大学
WordPress大学
C
Check Point Blog
Recent Announcements
Recent Announcements
IT之家
IT之家
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
美团技术团队
云风的 BLOG
云风的 BLOG
雷峰网
雷峰网
H
Hackread – Cybersecurity News, Data Breaches, AI and More
S
SegmentFault 最新的问题
MyScale Blog
MyScale Blog
Apple Machine Learning Research
Apple Machine Learning Research
Microsoft Azure Blog
Microsoft Azure Blog
V
Visual Studio Blog
B
Blog

Supabase Blog

AI Agents Know About Supabase. They Don't Always Use It Right. Custom OIDC Providers for Supabase Auth 100,000 GitHub stars Supabase docs over SSH Navigating Regional Network Blocks Supabase Joins the Stripe Projects Developer Preview Log Drains: Now available on Pro Supabase Storage: major performance, security, and reliability updates Supabase incident on February 12, 2026 Hydra joins Supabase X / Twitter OAuth 2.0 is now available for Supabase Auth BKND joins Supabase Supabase is now an official Claude connector Supabase PrivateLink is now available Introducing: Postgres Best Practices When to use Read Replicas vs. bigger compute Introducing TRAE SOLO integration with Supabase Supabase Security Retro: 2025 Sync Stripe Data to Your Supabase Database in One Click Building ChatGPT Apps with Supabase Edge Functions and mcp-use Own Your Observability: Supabase Metrics API Introducing iceberg-js: A JavaScript Client for Apache Iceberg Introducing Supabase for Platforms Adding Async Streaming to Postgres Foreign Data Wrappers Build "Sign in with Your App" using Supabase Auth Introducing Seven New Email Templates for Supabase Auth The new Supabase power for Kiro Introducing Supabase ETL Introducing Analytics Buckets Introducing Vector Buckets
Supabase Dot Com
Paul Copplestone · 2021-04-02 · via Supabase Blog

Supabase Dot Com

tl;dr During the next week, we'll be migrating from "supabase.io" to "supabase.com".

There are no changes required on your end. Your API URLs will remain on "supabase.co", and only our website URLs will change.

The rest of this post talks a bit about the origin of the name, but there's nothing important to know.

At the end of 2019 we released a Postgres Realtime engine on GitHub. We created this in my previous company after migrating from Firebase to Postgres.

It started gaining traction (if you count "GitHub stars" as traction) and so I tapped my friend, Ant, on the shoulder to see if he wanted to build an open source company with me (he was building another start up at the time).

The company we envisaged had Postgres at the core. We searched for every "dot com" we could think of with "base" in the name - hyperbase, superbase, suprabase, uberbase. It turns out this is what every database start does. We couldn't find any good "dot coms". And so we moved on to "dot io" domains.

Anybody who knows Ant, knows that he loves memes. While we were brainstorming we found that "supabase.io" was available.

To be honest, this name wasn't a strong contender, but it served a very important purpose - it was extremely "meme-able" because it sounds similar to Nikki Minaj's Super Bass.

We chose it as a placeholder and found it was, indeed, very funny to send each other Nikki memes while we brainstormed the business.

Note to anyone starting a business, don't use a placeholder. You'll never change it.

Luckily for us, the name grew on us and now we love it.

When we joined Y Combinator, they gave this advice:

Except in unusual circumstances (like Twitch.tv), if you don't have the .com version of your name, you should probably change it.

We decided to try purchasing supabase.com from the current owner. The YC forums were full of founders recommending a particular Domain Specialist who would help us negotiate and purchase the domain. The only catch - he would take a percentage of the purchase price.

This struck us as odd. The incentives were more aligned to the domain seller than the purchaser.

We're not afraid to roll up our sleeves at Supabase, so we decided we could handle it ourselves.

We were in for a huge surprise. After searching on the (old) supabase.com website, we found a company address. And it was literally 100m from my home.

Of all the places in the world that the domain could be registered, the owner was within yelling-distance. But we didn't yell. We simply asked, and after some negotiation, the owner agreed to sell it.

We were always willing to walk away from the Supabase brand if we needed to, but the price was reasonable for both parties. There really isn't much more to it than that.

Over the next few weeks, we'll update our domain name across most of the sites. If you're using a Supabase database and API, you're on a ".co" domain so your apps won't be affected at all.

You may also find some easter eggs appear ...