AI agents change the database business model. For years, SaaS apps were built around “one app, one database”. But agents are different. The emerging pattern is: one agent, one database. Why? Because each agent needs its own durable memory, context, tools, permissions, audit trail, and billing boundary. A shared database sounds cheaper at first, until you hit the real problems: - compliance gets messy - tenant isolation becomes fragile - per-agent billing is hard - debugging is painful - noisy neighbors appear everywhere - deleting one agent’s data cleanly is harder than it should be The clean abstraction is simple: Give every agent its own database. The hard part is cost. Can you imagine buying 1 million databases from Supabase, Aurora, or hosting 1 million MySQL/Postgres instances yourself? That model breaks immediately. This is where TiDB Cloud proves something important: “one agent, one database” is not just an architecture pattern. It is a new database business. With TiDB Cloud, we can make a database cheap enough to be provisioned per agent — around $2 or even cheaper per database per year. That changes the unit economics. Agents won’t share one giant memory forever. They will each get their own database. And the winning database platform will be the one that makes millions of tiny, isolated, compliant, billable databases feel boringly easy.