What is KurrentDB used for?

KurrentDB, formerly EventStoreDB, is an event-native database for event sourcing and event-driven systems, with an integrated streaming engine. It is a good fit for event-sourced application back ends, audit-friendly data histories and event-driven messaging between services.

Is KurrentDB open source?

Yes. KurrentDB is open source under a custom licence. Its source code is on GitHub at kurrent-io/KurrentDB and is written mainly in C#.

Yes. KurrentDB is open source, so the software itself is free to use under the terms of its own licence. A managed cloud version is also available.

Can I self-host KurrentDB?

Yes. KurrentDB can be self-hosted on your own server or infrastructure.

What are some alternatives to KurrentDB?

Similar open-source tools in the Databases category include Materialize, Litestream and Redis. SaaS products in the same category include KX kdb+, Aerospike and Amazon MemoryDB.

Is KurrentDB actively maintained?

Yes. The most recent commit to KurrentDB was on 2 October 2026, and the latest release is v26.2.0, published on 30 September 2026. The project has 5.9k stars on GitHub.

KurrentDB: open-source databases

About KurrentDB

KurrentDB is a database designed for event-driven applications. Formerly known as EventStoreDB, it stores data as streams of immutable events, which suits event sourcing and CQRS designs where the history of changes matters as much as the current state. Its event-native model is meant to simplify data modeling and keep data integrity intact.

An integrated streaming engine handles distributed messaging and aims to keep data consistent across consumers. The company behind it rebranded from Event Store to Kurrent, with the flagship product called the Kurrent platform and the hosted service named Kurrent Cloud. The README points to client libraries, deployment guides and community channels. The server is built on .NET.

The repository lists its license as 'Other', and the README includes a licensing section, so review those terms before commercial use. You can run KurrentDB on your own infrastructure or use the vendor's managed cloud. It suits teams building event-sourced systems, audit-heavy applications and streaming back ends.

Key features

Event-native database with immutable streams
Support for event sourcing and CQRS
Integrated streaming engine
Client libraries for several languages
Self-managed or Kurrent Cloud deployment
Rebranded successor to EventStoreDB

Good fit for

→Event-sourced application back ends
→Audit-friendly data histories
→Event-driven messaging between services

Built with: C#
Tags: event-sourcing; event-store; cqrs; database; streaming; eventstoredb; event-driven

KurrentDB: questions and answers

What is KurrentDB used for?: KurrentDB, formerly EventStoreDB, is an event-native database for event sourcing and event-driven systems, with an integrated streaming engine. It is a good fit for event-sourced application back ends, audit-friendly data histories and event-driven messaging between services.
Is KurrentDB open source?: Yes. KurrentDB is open source under a custom licence. Its source code is on GitHub at kurrent-io/KurrentDB and is written mainly in C#.
Is KurrentDB free?: Yes. KurrentDB is open source, so the software itself is free to use under the terms of its own licence. A managed cloud version is also available.
Can I self-host KurrentDB?: Yes. KurrentDB can be self-hosted on your own server or infrastructure.
What are some alternatives to KurrentDB?: Similar open-source tools in the Databases category include Materialize, Litestream and Redis. SaaS products in the same category include KX kdb+, Aerospike and Amazon MemoryDB.
Is KurrentDB actively maintained?: Yes. The most recent commit to KurrentDB was on 2 October 2026, and the latest release is v26.2.0, published on 30 September 2026. The project has 5.9k stars on GitHub.