Source time Edition date
ToolsLatent Space
Why Agents Love Supabase
为何智能体喜爱 Supabase
Paul Copplestone and Ant Wilson make the case for Supabase, but teams must weigh how much backend control they hand to a hosted platform.
Judgment
Engineering leads choosing a backend for agent-generated apps should treat Supabase's Git-tracked declarative schema and Docker-free local runtime as the default only if they accept hosted-platform lock-in; the cost is ceding operational control to a vendor now launching about five million databases a month.
Basis
Paul Copplestone and Ant Wilson make the case through three practical reductions in agent friction: a local Supabase runtime without Docker, a desired database schema kept in Git so an agent can inspect and edit state directly, and compute running beside the database. Latent Space frames the declarative schema as a Terraform moment for the database and says the founders report Supabase launching about five million databases a month, with existing customers growing into larger workloads. The mechanism is that an agent no longer has to reconstruct migration history or coordinate as many separate services; it can read desired state and operate closer to the data. But that same design deepens dependence on Supabase's hosted platform and its private-alpha compute.
Unclear The source does not quantify the migration cost or exit risk if a team later moves off Supabase's hosted platform.
Next Check whether the Docker-free local runtime and Git-tracked declarative schema are generally available and documented for CI use, rather than alpha-only.