Loading video...
Video Failed to Load
Supabase has become one of the default backends for the AI coding era. The open source Postgres platform now has 13 million users, spins up more than a million databases every week, and roughly 70% of its new activity is coming from agents. As coding shifts from developers writing... show more
45,244 views • 8 days ago •via X (Twitter)
29 Comments
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod same here, i plugged supabase into my agents a while ago and fixed a ton of slow queries on feednest that way
Tune in:
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod does the agent ever complain about the schema it gets handed or is that still our job
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod line is nearly vertical for the npm package wow
70% da atividade vindo de agente é ótimo pro Supabase e um alerta pra todo o resto. Agente sobe banco em segundos e ninguém confere permissão de tabela nem desliga o que sobrou. Em 20 anos de TI pública vi esse filme com servidor esquecido ligado. Quem audita o banco que o agente criou e abandonou?
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod agents never read a landing page
The tooling is already there: apply_migration writes a tracked migration, and branches replay list_migrations. The leak is execute_sql. Whatever an agent "just fixes" that way never becomes a migration, so the next branch quietly doesn't have it. Same trap as JPA ddl-auto=update: a schema that works isn't a schema you can replay.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% of new activity from agents is the stat. Agents are picking the defaults devs used to argue about.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod supabase's ease-of-use for people getting started with DBs using ai is honestly amazing
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% of new activity from agents is the wild number here. agents pick defaults, so whatever the agent reaches for first wins the next decade
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% agents. The other 30% is me asking an agent why the migration failed
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% of new activity coming from agents is the number that jumps out at me. When I build with AI now, I almost never pick the database myself. The agent just reaches for whatever it knows.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod Agents choosing the backend is a real shift. When most new databases are spun up by agents, defaults and docs become the product. Curious how Supabase thinks about guardrails when an agent, not a developer, is making the choices.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod Automatic pausing of idle projects matters a lot at a million new databases a week, because nobody is around to clean up the unused ones.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% of new activity coming from agents is wild. Curious how many of those agent-built databases shipped without RLS 👀
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod supabase is goated bro
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod An agent's raw `CREATE TABLE` needs `ENABLE ROW LEVEL SECURITY` after it: per Supabase's docs, an exposed table that's missing RLS is open to any granted role.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod A million databases a week. Eventually one of these apps will get a second user.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% of the new activity isn't people. the builders started building builders, and the databases noticed first. somewhere a developer just met his biggest customer. it never sleeps and never says thanks.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod If 70% is agents, who's the real customer now: the dev or the agent?
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod check your idle projects, agents rarely drop a database after the task.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% of new Supabase activity coming from agents is wild. Once agents are the main users, does the dashboard still matter, or is the whole product just the API and docs?
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod Supabase is the obvious default now. The user base growing with the AI coding era makes sense. But if agents create 70% of new databases, the hard part moves to what happens after. Who reviews the row level security an agent wrote at 2am?
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% of new activity coming from agents means the real customer is now the model's default suggestion. Whoever the agent picks first wins distribution without a single ad.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% of new activity from agents is the real headline. Your next 10M users don't read docs, they read error messages. DX for agents is the new onboarding.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% agent activity makes retained apps a more useful growth signal than databases created.
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod love supabase
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod 70% of new activity coming from agents means Supabase's busiest users never sleep, never take coffee breaks, and still forget to add an index 😄🐘
@kiwicopple @garrytan @harjtaggar @snowmaker @supabase @LightconePod agents picking defaults forces supabase to bake security and migrations into the core. that'll shape every personal app
