Today we're excited to announce the release of the official Elixir Client SDK for EventSourcingDB, version 1.0. If you're building event-sourced systems on the BEAM, you now have first-class support for writing, reading, and observing events from your Elixir applications.
Elixir has earned its place as one of the most compelling platforms for building fault-tolerant, distributed systems. With this SDK, we're bringing EventSourcingDB into that world, and we've made sure it feels like Elixir from the ground up.
Over the past few months, we have received more feedback than ever before. Hundreds of conversations with developers, architects, and CTOs have painted a remarkably consistent picture. The message was clear, and we owe it to you to be honest about what we heard: Event Sourcing is too complex. Not in theory. In theory, everyone loves it. But in practice, teams struggle. They struggle with modeling, with naming, with the sheer cognitive overhead of thinking in events rather than rows.
AI-powered agents are no longer a future promise. They are here, embedded in development workflows, automating decisions, analyzing data, and helping teams move faster. Tools like Claude, ChatGPT, and Gemini have become part of the daily toolkit for developers and architects alike. But until now, these agents had no way to talk to your event store. They could reason about code, summarize documents, and generate queries, but they could not read your events, explore your subjects, or run an EventQL query against live data. The most valuable data source in an event-sourced system was invisible to AI.
Today, we are changing that. We are releasing the MCP Server 1.0 for EventSourcingDB, an extension that connects large language models directly to a running EventSourcingDB instance. It implements the Model Context Protocol, an open standard that defines how AI models discover and invoke external tools. With this release, your AI agents can read events, write events, browse subjects, inspect event types, register schemas, and run EventQL queries, all through natural language.
Data analysis is more important than ever. Data science and AI have become essential tools for many companies. The tools keep getting better: more powerful models, faster computers, smarter algorithms.
But here's the problem: the underlying data is often garbage. And as always: garbage in, garbage out. The best models, the fastest computers, the smartest algorithms – none of it matters if your data doesn't tell the real story.
EventSourcingDB 1.2.0 is available for download. Since we shipped 1.1.0, we've spent a lot of time listening – at conferences like KanDDDinsky, in customer calls, through GitHub issues, and in direct conversations with teams running EventSourcingDB in production. This release is our response to what you told us you needed most.
Today we're thrilled to celebrate an important milestone for the Event Sourcing community: the release of OpenCQRS 1.0. Built by our friends at Digital Frontiers, OpenCQRS brings first-class support for CQRS and Event Sourcing to the JVM world, with native integration for EventSourcingDB. This release matters deeply to us, not just because it adds another powerful tool to the ecosystem, but because it represents collaboration, shared vision, and the steady growth of something we have believed in for more than a decade.
Today we're pleased to announce the release of the official .NET Client SDK for EventSourcingDB, version 1.0. With this release, .NET developers gain first-class support for building event-sourced applications with EventSourcingDB – bringing the same level of quality and ergonomics we've already delivered for Go, JavaScript/TypeScript, PHP, Python, and Rust.