Can One Database Handle Daily Business and AI Helpers at Once?

CedarDB, a Munich-based database company, wants one PostgreSQL-compatible engine to handle both everyday transactions and data analysis, with AI agents as the defining use case. TechCrunch
The pitch is consolidation without pipelines, or one system instead of several. Cofounder and CEO Moritz Sichert said the combined approach has gained relevance with the rise of agentic AI. CedarDB is a Technical University of Munich spinout based on the Umbra research project. It was listed as a TechCrunch Disrupt 2026 Startup Battlefield company.
At the storage and execution layer, CedarDB states it runs transactions and analytics on the same data. CedarDB Like keeping daily sales and monthly accounts in the same notebook, new writes are immediately available to dashboards and reports, removing the extract, transform and load step between operational tables and analytic queries. The company states it runs analytical queries alongside transactions using parallel execution while preserving ACID guarantees, the basic rules that keep data safe and correct. Compatibility is PostgreSQL, which for practitioners means existing drivers, tooling and SQL dialects carry over.
The agent layer sits on top of that engine. CedarDB offers what it calls an Agent-Native Database that lets users create, control and monitor AI agents working directly on live data. CedarDB The company states users decide what agents can touch while the agents handle the rest. In practice, AI agents can write and run SQL, and database roles and row-level policies, limits on what each agent can see or change, constrain what each agent can read or change. The company states the system scales from small writes to handling billions of rows.
On performance and cost, all figures to date are vendor claims. CedarDB claims to be 200% faster than leading analytical databases and 18x faster than Postgres on mixed workloads. It also claims 61% lower LLM-SQL pipeline cost, and describes itself in company materials as the world's fastest database.
The broader context here is why agents change the tradeoff. Traditional separation kept OLTP systems, the systems built for fast daily updates, fast for writes and shipped data elsewhere for analysis. That works when analysis tolerates delay. Agents that query, reason and then write back do not tolerate it well. They need fresh reads and safe writes in the same transaction boundary, with permission enforcement that survives generated SQL.
In my view, the interesting claim is not raw speed. It is permissioned, live SQL execution at scale. Vendor benchmarks rarely survive contact with production schemas, skewed data and concurrent load. Throughput numbers without query mix, hardware, isolation level and dataset size tell an operator little. What matters is steady speed when busy, correct results when many things happen at once, and whether row-level policies hold when the client is non-deterministic.
Looking at what this means for teams, the operational question is simpler. If one engine can absorb dashboards and agent traffic without replica lag, delays between copies, or dual-system governance, managing two systems, it reduces surface area. Fewer copies, one access model, one audit path. The risk moves elsewhere, to big slow queries slowing down small fast ones, and to agent behavior itself. Guardrails help, but giving an agent only the access it needs and watching what it actually touches in production will decide whether the model is workable.
Looking longer term, that is a useful direction even if consolidation is incomplete. Databases that assume machine-generated query volume look different from those built only for human-written SQL. CedarDB is betting that difference starts with unifying the data, then controlling the agent.


