Whats new in EventCatalog - September 2025
Welcome to EventCatalog’s monthly update! 🎉
September was a big month — we launched EventCatalog Studio, introduced a new GraphQL Plugin, added Data Stores as a new resource type, and shipped a range of smaller improvements.
In this post, we’ll take a look at what’s new, what’s coming next, and how you can get started.
EventCatalog Studio​
We’re excited to announce the launch of EventCatalog Studio — our new visual design tool for distributed systems.
Many developers already love the EventCatalog visualizer, which gives you a static view of your architecture. With EventCatalog Studio, you can take that experience further: design diagrams interactively, collaborate with your team, and save drafts locally — all using architecture primitives.
Our goal is to make designing and collaborating on event-driven architectures easier than ever. With EventCatalog Studio you can:
- Import your existing EventCatalog diagrams.
- Add documentation to your designs
- Explore and sketch out new ideas.
- Save designs locally for offline work.
- Re-import designs back into EventCatalog when ready.
- Embed diagrams directly into your documentation.
You can jump straight in today. Try EventCatalog Studio or experiment in our playground.
EventCatalog Data Stores​
You can now document your data stores in EventCatalog — whether they’re databases, caches, object stores, search indexes, or anything else — and define which services read from or write to them.
This new feature gives your teams a clearer picture of how data flows across your architecture: who owns the data, and which services depend on it.
We’ve also updated the visualizer to include two new perspectives:
- Service view → see which data stores a service uses (see demo)
- Data store view → see which services depend on a specific data store (see demo)
Data stores take inspiration from the C4 model (containers), giving you a more complete way to document and explore your systems.
You can start adding Data Stores today — check out the documentation to get going.
The new GraphQL Plugin​
GraphQL has become a go-to for many teams building distributed systems. With our new GraphQL Plugin, you can now turn your GraphQL schemas directly into EventCatalog documentation.
The plugin automatically maps your GraphQL operations into EventCatalog concepts:
- Queries → Queries
- Mutations → Commands
- Subscriptions → Events
You can also assign your GraphQL schemas to specific services and domains in your architecture, making it easier to see how everything connects.
This unlocks powerful automation — your catalogs can now be generated directly from your GraphQL schemas. And when combined with our OpenAPI and AsyncAPI plugins, you have a strong foundation for documenting a wide range of services and technologies.
Get started by checking out the GraphQL Plugin docs or watch the demo video.
Introducing Attachments to all Resources​
We added the ability to add attachments to any resource type in EventCatalog. A new feature that allows you to link external resources, diagrams, and documentation directly to your domains, services, events, commands, queries, and channels.
Many teams and organizations have information scattered across different tools and platforms. This makes it difficult to find the information you need when you need it.
With Attachments, you can now link to external resources, diagrams, and documentation directly to your EventCatalog resources.
To learn more and get started you can read our blog post on attachments.
Other improvements​
As usual we have updated our dependencies in the project and we have also added support for Structurizr.
If you have any issues or want to join our community of over 1200 people exploring EventCatalog and event-driven architecture feel free to join us!