Run Chronicle locally in one container, append your first events from a plain .NET console app, and watch them become read models — every command in this post was executed against the exact versions it names.
Chronicle's kernel sits behind a language-agnostic gRPC/protobuf boundary — 22 canonical .proto contracts that any language can implement. Here's how the contract is layered, how the existing clients are built on it, and what a new client implements.
Most event sourcing comparisons reduce to popularity. We compiled a version-pinned, source-cited comparison of KurrentDB, Marten, and Cratis Chronicle instead — every row reproducible from public documentation, with the same rules applied to our own product. Here's how to use it.
