Event sourcing in Python — coming soon

A Python client for Chronicle — the open-source (MIT) event-sourcing database and processing runtime — is in development. It will join the existing .NET, TypeScript, Kotlin/Java, and Elixir clients, all of which speak the same language-agnostic gRPC/protobuf contract against the same event store.

Pre-release

The Python client is pre-alpha. APIs will change, no package has been published to PyPI, and no commitment is implied. There is nothing to install yet — follow the repository for progress, or ask in the community if it matters to your project.

In the meantime, Chronicle’s gRPC boundary means any language with a gRPC implementation can talk to it — see Building a client — and the Chronicle MCP server connects AI agents to a running Chronicle regardless of client language.

Where to go next

Chronicle.Python on GitHub Follow the Python client's development.

Chronicle in your language The clients that ship today: .NET, TypeScript, Kotlin/Java, and Elixir.

Get started with Chronicle Run Chronicle locally and build your first event-sourced feature.

Building a client Implement the Chronicle gRPC contracts for a new language or runtime.