2 Sources
[1]
Event-series database keeps agent history | VentureBeat
For a data engineer building retrieval or analytics pipelines for agents, the practical question is where event history lives. Traditional databases flatten events into rows and precomputed aggregates, discarding the sequence and context an AI agent needs to reason about why something happened --
[2]
Startup Keewano launches agent-focused database and pulls in $12M in funding
Startup Keewano launches agent-focused database and pulls in $12M in funding Database startup Keewano today launched KeewanoDB, an event-oriented database designed to give artificial intelligence agents real-time context for analytics and decision-making. The startup also announced $12 million in
Share
Copy Link
Keewano unveiled KeewanoDB, an event-series database built specifically for AI agents, alongside $12 million in seed funding led by Hetz Ventures and Andreessen Horowitz's a16z Speedrun. Unlike traditional databases that flatten events into rows, KeewanoDB stores complete event sequences by entity, enabling agents to understand why outcomes occurred without reconstructing history at query time.

Keewano made KeewanoDB generally available on Tuesday, introducing what the Tel Aviv-based startup calls an event-series database designed specifically for AI agents. The company, formally known as Sandstorm Ltd., announced the launch alongside $12 million in seed funding led by Hetz Ventures, with participation from Andreessen Horowitz's a16z Speedrun and other investors.
1
2
The agent-focused database addresses a fundamental problem: traditional databases flatten events into rows and precomputed aggregates, discarding the sequence and context AI agents need to reason about why something happened. This forces agents to reconstruct history from a warehouse or search index at query time, creating bottlenecks in agentic analytics workflows.
1
Co-founder and CEO Mark Kardashov pushes back on categorizing KeewanoDB as a graph database, document database, or straightforward time series system. Instead, he describes it as an event-series database that treats each entity—a user, device, or agent—as a primary key, with every event attaching to it in sequence.
1
The architecture creates one large table per entity rather than requiring joins across many tables. Events are stored as four-byte units on disk, sequenced by entity rather than split across relational tables. This approach lets agents inspect an entity's complete history without flattening information into tables or waiting for extract, transform and load pipelines.
1
2
KeewanoDB runs as a fully managed service on Google Cloud, with other clouds and self-managed deployment planned for early 2027. An agent connects directly to KeewanoDB and reads sequences where they already sit, wired through an SDK and the Model Context Protocol (MCP).
1
The system includes a semantic layer built during ingestion using large language models that attaches additional context to each event as it lands. If a user transitions from active to inactive to flagged for fraud, all three labels persist in sequence—agents see current status without losing earlier context. An acceleration engine enables in-database agent queries by executing Lua scripting directly through MCP, eliminating the need to move data to external processes.
1
2
Related Stories
Keewano claims the distributed, multi-sharded design running in Docker containers orchestrated by Kubernetes can query approximately 250 million events in less than half a second using vectorized instructions on standard CPUs instead of GPUs. Customers ingesting data from Snowflake or Google's BigQuery have reported token savings of approximately 84% compared with querying existing systems directly.
2
The database supports Apache Kafka for event stream ingestion and works with Parquet and Apache Iceberg formats. Keewano charges based on the number of active entities rather than individual events, positioning the system to run alongside existing databases like Snowflake for conventional business intelligence while handling agent workloads separately.
2
Co-founder and CTO Pavel Bibergal previously ran data infrastructure for cross-platform gaming vendor Plarium, where his team started building with agents and large language models roughly two years ago. Despite a large budget and full analyst team, they could not get simple questions answered in real time about why outcomes occurred at sustainable costs. That gap led Bibergal to build KeewanoDB's first prototype independently before forming Keewano.
1
A separate analytics layer includes an agent called Signal that runs anomaly detection and causal inference approximately once an hour, applying machine learning and statistical methods to test hypotheses and present supporting event sequences as evidence. The company is launching two products: the general-purpose KeewanoDB for agentic analytics and reasoning, and an analytics layer for product analytics and real-time operational decisions.
1
2
Summarized by
Navi
[1]
17 Feb 2026•Technology

30 Jun 2026•Technology

22 Apr 2026•Technology

1
Technology

2
Science and Research

3
Technology
