DevOps / SRE / Platform · 04.08.2026, 15:48 UTC
AI agents can create database sprawl issues. YugabyteDB’s solution is more agents!
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 04.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
The next database scaling problem may not be how big a database gets, but how many databases an enterprise suddenly has to run.
That’s the inspiration behind YugabyteDB AMP, or Agentic Multitenant Postgres, a new serverless PostgreSQL tier designed for a world in which companies could be running hundreds or thousands of AI agents, each generating its own data layer demands. For Yugabyte, that means rethinking what scale looks like.
Karthik Ranganathan, co-founder and co-CEO of Yugabyte, tells The New Stack, “The dimension of scale is shifting. It’s not just large databases; it’s also a proliferation of databases.”
“The dimension of scale is shifting. It’s not just large databases; it’s also a proliferation of databases.”
YugabyteDB AMP extends Yugabyte’s reach to the smaller end of that spectrum, while maintaining the distributed architecture the company has traditionally built for large, mission-critical workloads. It uses serverless multitenancy and what Yugabyte calls Enhanced Colocation to pack hundreds of workloads onto shared infrastructure, while giving each agent an isolated PostgreSQL database.
The economics make sense for fleets of databases, including those that underpin AI agents. An experimental agent might hammer its database for a few minutes, and then the database might sit untouched for days or even be destroyed after the task was completed. YugabyteDB AMP scales to zero when that workload is idle and charges by CPU minute when it is running.
Yugabyte is also seeing another problem will appear alongside all those databases: the need for someone (or …