kurrent-io/KurrentDB

KurrentDB is a database that's engineered for modern software applications and event-driven architectures. Its event-native design simplifies data modeling...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 11th, 2026
Created on September 17th, 2012
Open Issues & Pull Requests: 150 (+0)
GitHub issues: Enabled
Number of forks: 679
Total Stargazers: 5,850 (+0)
Total Subscribers: 200 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.4 days
Mean response time: 46.6 days
90th percentile: 103.6 days
Tracked items: 103

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 21% of issues opened in the past year have been closed. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 35
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 704 days
Stale 30+ days: 35
Stale 90+ days: 34

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (26)
  • enhancement (18)
  • subsystem/projections (6)
  • documentation (4)
  • kubernetes (3)
  • Projections (2)
  • customer initiated (2)
  • good first issue (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

KurrentDB is a database engineered for event-driven architectures and modern applications that implements event sourcing and CQRS patterns.

The tool addresses the complexity of building event-driven systems by providing an event-native database design that simplifies data modeling while maintaining data integrity. Rather than treating events as secondary concerns, KurrentDB makes them a first-class citizen in the data model. It includes an integrated streaming engine that handles distributed messaging and ensures consistency across systems, eliminating the need to bolt on separate message brokers or event streaming platforms for applications built around event sourcing.

Teams building event-sourced applications, systems requiring audit trails, or architectures centered on CQRS patterns should consider KurrentDB. It suits projects where preserving the complete history of state changes is essential and where event-driven communication between services is a core architectural principle. The tool provides gRPC-based client libraries for integration and supports deployment across multiple cloud providers through its managed Kurrent Cloud offering, which removes infrastructure management overhead.

The project receives most of its issue reports from outside users rather than the core team, indicating a substantial base of adopters using it in production. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker centers on bugs, enhancements, and documentation, reflecting a focus on stability and usability.