# 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 and preserves data integrity while the integrated streaming engine solves distributed messaging challenges and ensures data consistency.

Repository: https://github.com/kurrent-io/KurrentDB
Canonical: https://ross.abutalabs.com/products/kurrentdb
Homepage: https://www.kurrent.io/
Language: C#
License: NOASSERTION
License Family: other
Topics: cqrs, eventsourcing, eventstore, event-sourcing, event-store, database
Last push: 2026-08-26T17:11:52+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 98, longevity 100
- inputs: {"age_days": 5098, "days_push": 7, "days_rel": 14, "gap_med": 16.5, "n_releases_24m": 33}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 5848, forks 679 (observed 2026-08-28T04:09:31.603307+00:00)

## What it is
KurrentDB (formerly EventStoreDB) is an event-native database designed for event-driven architectures, storing data as immutable event streams with an integrated streaming engine for distributed messaging. It is the open-source server component of the Kurrent platform, with a companion managed cloud offering.

## Use cases
- store application data as an event stream
- build event-sourced systems with CQRS
- implement event-driven microservices messaging
- preserve an audit log of every state change
- replace a message broker and database with one event store
- run a highly available event database cluster

## When to choose
- your architecture is built around event sourcing or CQRS
- you need immutable event logs with built-in subscriptions and projections
- you want one system for both persistence and distributed messaging

## When to avoid
- you only need simple relational CRUD with ad-hoc SQL queries
- your team has no experience with event-driven design and needs a general-purpose database
- you need heavy analytical scans over mutable records

## Facets
- artifact type: service
- maturity: active
- function: database, streaming, message-queue, microservices
- domain: databases, microservices, backend
- platform: windows, self-hosted, cloud, dotnet
- tags: event-sourcing, cqrs, event-store, event-driven-architecture, kurrentdb, grpc-clients, messaging, linux, macos, docker

## Member repositories
- kurrent-io/KurrentDB (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:31.603307+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:51:54.406410+00:00, confidence not recorded.
  - readme: https://github.com/kurrent-io/KurrentDB (fetched 2026-08-28T04:09:31.603307+00:00, sha 787ee52c558c)
  - homepage: https://www.kurrent.io/ (fetched 2026-08-29T08:47:18.977317+00:00, sha e4d0bef547ce)
  - site_page: https://www.kurrent.io/docs/capacitor/getting-started/quickstart (fetched 2026-08-29T08:47:18.981714+00:00, sha e627a32de775)
  - site_page: https://www.kurrent.io/pricing (fetched 2026-08-29T08:47:18.979941+00:00, sha 19077985f9f5)
- Data as of 2026-08-30T08:39:29.467469+00:00.