Introducing EventCatalog Studio (v2): design what comes next, together
EventCatalog is good at telling you how your architecture works today. Your teams document their domains, services and messages, and everyone can find out what talks to what.
But the conversations that matter most are often about tomorrow. "How would we add buy now, pay later?" "What happens if we split the Order Service?" "Who needs to know if we retire this API?"
Those conversations usually happen somewhere else: a whiteboard, a slide, a diagram tool that knows nothing about your architecture. Someone redraws the services by hand, gets a few of them wrong, and the result ends up in a folder nobody opens again.
We kept hearing the same thing from customers: we document the present in EventCatalog, but we plan the future somewhere else.
Today we're excited to introduce EventCatalog Studio (v2): live, collaborative canvases inside your catalog, for designing what comes next with your team and your AI agents.
The first version of EventCatalog Studio was a separate tool for drawing designs with architecture primitives. Studio v2 lives inside EventCatalog itself, so your designs start from the architecture you already document, and your team and your agents can work on them together.
