Editorial illustration for CedarDB Unifies Transactions and Analytics as AI Agents Raise Database Stakes
CedarDB Merges Transactions and Analytics
CedarDB, a database engine out of Munich, is betting that companies no longer want to run two separate systems, one for storing transactions and another for crunching analytics on them. Cofounder and CEO Moritz Sichert told TechCrunch that this split, standard in database architecture for decades, is becoming a liability now that AI agents need to query business data in natural language and get answers fast. CedarDB traces its roots to Umbra, a research project at the Technical University of Munich built to outperform legacy database engines by squeezing more out of modern hardware rather than throwing additional compute at the problem.
Five Umbra researchers went on to found CedarDB, carrying that engineering philosophy into a product aimed at enterprise customers whose current setups handle years of transaction history well but struggle to answer analytical questions on the fly. The company has spent roughly a decade in development, and Sichert says one decision in particular, building CedarDB to work with PostgreSQL, has shaped how it fits into both existing enterprise stacks and the way large language models are trained to interact with databases.
Analytical databases help businesses spot trends and answer questions, while operational databases store the day-to-day records of transactions, like orders and payments. But the Munich-based database engine CedarDB supports both, and its approach has gained relevance with the rise of agentic AI, its cofounder and CEO Moritz Sichert told TechCrunch.
Why this matters
AI agents don't query databases the way humans do. They fire off rapid, unpredictable sequences of reads and writes, often blending lookups with aggregation in ways that don't respect the old analytical-versus-operational split. That's the gap CedarDB is betting on, and Sichert's pitch to TechCrunch lands at a moment when agentic workloads are forcing infrastructure teams to rethink assumptions baked into databases for decades. For developers building agent pipelines, a single engine that handles transactions and analytics without bolting together Postgres and a warehouse is a real operational simplification, fewer moving parts, fewer sync jobs, less latency between "the agent asked" and "the system answered."
We're less interested in the Technical University of Munich pedigree than in whether CedarDB's hardware-level speed claims hold up under actual agent traffic rather than benchmark conditions. Umbra was a research project; shipping it as production infrastructure for unpredictable AI workloads is a different test. Worth watching whether CedarDB can land customers running real agentic systems, not just teams drawn to the architecture on paper.
Related Reading
Business & Startups Nordic pilot adds Gemini for Education, NotebookLM to boost AI literacy
Business & Startups Kling launches Video O1, all-in-one model with MVL bridge using transformer
Business & Startups DeepSeek Seeks More Capital Weeks After USD 7B Funding Round
From Archives Meta Muse Wonder vs Claude: Rival Runs Best-Effort, Not Common Harness
From Archives Square's New Kiosk Uses Conversational AI to Help Customers Place Orders
Common Questions Answered
Why does CedarDB combine transactions and analytics instead of using separate database systems?
CedarDB unifies both functions because AI agents query business data differently than humans, firing off rapid and unpredictable sequences of reads and writes that blend lookups with aggregation in ways that don't respect the traditional analytical-versus-operational split. This unified approach eliminates the need for companies to maintain two separate systems, which has become a liability in the age of agentic AI that requires fast natural language query responses.
What is the difference between analytical databases and operational databases that CedarDB addresses?
Analytical databases help businesses spot trends and answer questions through data analysis, while operational databases store day-to-day transaction records like orders and payments. CedarDB's innovation is supporting both functions in a single database engine, addressing the gap created by AI agents that require seamless access to both real-time transactional data and analytical capabilities.
How do AI agents' database query patterns differ from traditional human queries?
AI agents fire off rapid, unpredictable sequences of reads and writes that often blend lookups with aggregation in ways that don't respect the old analytical-versus-operational database split. This fundamentally different querying behavior is forcing infrastructure teams to rethink decades-old database architecture assumptions that were designed for more predictable human usage patterns.
What are the origins of CedarDB's technology?
CedarDB traces its roots to Umbra, a research project at the Technical University of Munich, which provides the foundation for its unified database approach. The company was founded by Moritz Sichert and other researchers who recognized the need for a new database architecture that could handle both transactional and analytical workloads simultaneously.
Further Reading
- CedarDB wants one database to handle both transactions and analytics, as AI agents raise the stakes - TechCrunch
- CedarDB secures €5.3 million - Munich Startup
- CedarDB: Revolution for the database world - Munich Startup
