Our take
Activeregular commits and releases- Activity
- 70
- Community
- 93
- Issues
- 47
- Pull requests
- 57
+8 stars in the last 16 days
- Merges more pull requests than 81% of the projects we track
- Releases more often than 78% of the projects we track
- More contributors than 77% of the projects we track
KurrentDB is an actively maintained, purpose-built option for event-driven systems, with frequent releases and a broad contributor base, though its repository does not provide an asserted license value.
Good fit if
- Your application is built around event sourcing, CQRS, or event streams.
- You want storage and event streaming integrated, with gRPC clients across several languages.
- You can build and run a .NET-based service, or prefer the managed Kurrent Cloud offering.
Look elsewhere if
- Your project needs a clearly established license before adoption, since the supplied repository metadata says NOASSERTION and the README points to a separate licensing page.
- You need a general-purpose database rather than an event-native platform.
- Your team cannot accommodate the .NET SDK 10.0 build prerequisite for building from source.
All health signals
| Last commit | 2026-10-09 (3 days ago) |
|---|---|
| Commits, last 90 days | 52 |
| Releases, last 12 months | 25 (latest v26.2.2, 2026-10-07) |
| Contributors | 100+ (top contributor: 15% of commits) |
| Issues closed, last 90 days | 1+ |
| Pull requests merged, last 90 days | 67 (typically merged in 1 day) |
| Project age | 14 years |
Checked on 2026-10-13 with the GitHub API.
Overview
KurrentDB stores application data as events and includes a streaming engine for distributing them. This approach suits systems that need an ordered record of changes and consistent event delivery, rather than treating the database and messaging layer as separate concerns.
It is aimed at teams building event-driven software, including systems using event sourcing or CQRS. You can run it yourself or use Kurrent Cloud, the company’s managed offering.
Key Features
- Event-native data storage for event-driven applications.
- Integrated streaming engine for distributing events.
- Designed to support data integrity and consistency across storage and messaging.
- gRPC protocol with supported clients for Python, JavaScript/TypeScript, Java, .NET, Go, and Rust.
- Self-managed deployment, with Windows, Linux, and macOS development supported through Docker.
- Kurrent Cloud offers managed clusters on AWS, Azure, and GCP.
Use Cases
- Event-sourced applications that need to keep a durable record of state changes.
- CQRS systems where teams want an event store and streaming engine in one platform.
- Distributed applications that need to publish and consume events consistently.
- Teams that want to evaluate an event-driven database locally before deciding between self-managed deployment and Kurrent Cloud.
What you need
Detected in the repository
- C# (main language on GitHub)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
- Automated checks on GitHub Actions
Getting Started
Install the .NET SDK 10.0, then build from the repository root:
dotnet build -c Release
See the README and user documentation for running a node, deployment, and client setup.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Considerations
The repository is active, with recent commits and regular releases. Its contributor base is broad, and the measured activity does not indicate dependence on a single contributor. The health data reports limited issue closures in the measured period, so it does not establish how quickly issues are typically resolved.
Building from source requires .NET SDK 10.0. Docker is supported for building and running the service, but the provided repository data does not list a Helm requirement or confirm a test setup. The API-reported license is NOASSERTION; review the licensing information and confirm that its terms fit your intended use before adopting it.
Found this useful?
Share it with someone who would like KurrentDB.