The private beta of GenesisDB Syncra, a new member of the GenesisDB product family, has been open for a few days now. Syncra aggregates multiple event sourcing database instances into a single, deterministic, unified stream. It is built for event-driven architectures that have outgrown a single event store and now span services, teams, and regions.
If GenesisDB is the engine that captures every state change as an immutable event, Syncra is the layer that turns those scattered signals into one coherent flow.
Event sourcing works beautifully inside a single bounded context. Every change is an event, every event is the truth, and replay is just a matter of reading the log. But real systems rarely stay inside one bounded context for long.
As event-driven systems grow, they naturally split into multiple bounded contexts, each backed by its own event sourcing database. Orders live in one store, users in another, billing in a third. Each service owns its events, but downstream consumers - dashboards, projections, reporting tools, business flows - often need a combined view across all of them.
The usual answer is custom integration code: one consumer per event store, glued together with bespoke ordering logic and a lot of hope. Syncra replaces that pile of glue with a single, well-defined component.
One connection instead of many.
One deterministic stream instead of scattered sources. One API for all your event sourcing data. Your existing GenesisDB clients keep working - just point them at Syncra.
Whether you run a handful of services or a large-scale event sourcing platform, Syncra fits into your architecture without changing how your services work. A few scenarios where it shines:
Syncra is intentionally narrow in scope and engineered for speed and predictability:
instance field identifying which event store produced it. Filter, route, or display by source.GenesisDB Syncra is closed source and ships as part of the GenesisDB product family - free forever. No license fees, no per-event pricing, no surprise tiers down the road. We want Syncra to be a natural extension of every GenesisDB deployment, not a paywalled add-on. During the private beta we are working closely with participating teams to shape Syncra around the architectures that actually exist in production.
If you are running multiple GenesisDB instances - or you are about to - and you have ever wished for a single deterministic stream out of the box, this beta is for you. We are onboarding a small group of teams first, gathering feedback, and iterating quickly.