CedarDB wants one database to handle both transactions and analytics, as AI agents raise the stakes
- ID
- 35564
- Status
- summarized
- Published
- 15 Oct 2026, 6:00 AM
- Fetched
- 15 Oct 2026, 6:31 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/10/14/cedardb-wants-one-database-to-handle-both-transactions-and-analytics-as-ai-agents-raise-the-stakes/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 5.5
- Created
- 15 Oct 2026, 6:31 AM
- Tags
- Audience
- developersdatabase_learnersai_ml_learnersai_agent_userssaas_founders
What happened
CedarDB, a Munich-based database engine spun out of the Technical University of Munich and built on the Umbra research project, is pitching a single engine that handles both transactional (OLTP) and analytical (OLAP) workloads. Five Umbra researchers are cofounders, and cofounder/CEO Moritz Sichert says the team deliberately made CedarDB PostgreSQL-compatible so customers don't have to rebuild their apps, and because Postgres is the database logic LLMs are most familiar with from training. The excerpt gives no funding amount, pricing, benchmark numbers, or customer names — it's a startup profile, not a measured comparison.
Why it matters
If you're building AI agents that generate SQL against a Postgres store, the pitch here is that you keep your existing schema, drivers, and agent prompts while the engine also answers analytical queries — no separate OLTP-plus-warehouse split to maintain. The decision to make now is narrow: watch or trial it only if your agent workload is hitting the wall of copying Postgres data into a warehouse, and benchmark it yourself, because this piece contains zero performance numbers and no Malaysia-specific detail (no local pricing, cloud region, or regional availability).
Discussion angle
Is PostgreSQL compatibility actually the deciding factor for agent-written SQL, or does the agent era push teams toward a single HTAP engine regardless of what the LLM was trained on? Ask the room which of them has split Postgres from their analytics store and what that cost them.