Whats new in EventCatalog - August 2025
Welcome to EventCatalog's monthly update!
August brought a welcome change of pace as many in our community took well-deserved summer breaks. While things were quieter overall, we stayed focused on two key areas: advancing EventCatalog Studio and strengthening the core platform through stability improvements and bug fixes.
In this update, we'll dive into:
- The exciting progress on EventCatalog Studio and what's on the horizon
- Recent fixes and improvements to the platform
- A preview of what's coming next
Let's explore what we've been building while you've been recharging!
EventCatalog Studio
During August we have been busy, working on our new open source project called EventCatalog Studio. This is a visual editor that allows you to design, gather feedback, collaborate with your teams, define schemas and much more.
Before we get into the details, it’s important to understand why we are focusing in this area.
Life-cycle of event-driven architecture
Over the past 3 years we have learnt from the community and users of EventCatalog that the life-cycle of defining messages, schemas, ideas, collaboration with teams, documentation and governance is a mess.
EventCatalog was born from a personal problem. That discoverability with event—driven architecture is hard. So we built an open source project to help folks discover what events they have, assign them to services and domains, and provide their teams with a platform where they can get a better understanding of what is going on in their architecture. The project has grown far beyond the initial release and is now being used by companies around the world, helping them document and govern their architectures, and continues to be adopted.
Whilst this solves documentation and governance, I feel we still have a gap in the life-cycle.
I feel we have gaps in the ability to capture ideas, drafts, schema designs, get feedback from teams, capture breaking changes, notifying teams of changes, understand how events are used in their architecture, and the list goes on…. As I dive deeper into this topic, I've started to learn from community members and teams using EventCatalog that the life-cycle for event-driven architecture is broken.
What if we could make this easier? What if we had tools that let us explore new drafts, ideas, plan work, get feedback, design diagrams that can be exported into artifacts that we can actually use in our code, our documentation and specifications?
Could we close the gap between ideas, design, implementation and documentation?
I think it’s possible, and that’s why we have been exploring EventCatalog Studio.
What is EventCatalog Studio?
EventCatalog Studio is a local first open source visual designer, that focuses on architecture primitives (e.g messages, channels, data stores, etc). Your designs are owned by you and can be shared with your teams and committed to source control.
You will be able to run EventCatalog on the cloud or run locally on your machine. Either way your data is owned by you, and nothing is shared, keeping your designs private to your organization.
To start you can create new designs, or use custom templates to start from. You can define workflows, business processes, or architecture patterns. You can start from predefined templates to get started.
In future versions you will be able to define your own templates for your teams to get started. Below is an example of the welcome dashboard you will see. Allowing you to open a design from disk, or create a new one from scratch or from a predefined template.
In EventCatalog Studio you will be able to create designs, simply dragging your primitives onto the canvas (e.g Service, Events, Command, Query, Domain etc). This will let you create design concepts for your teams, simulate messages on the design, define schemas and much more.
Then you will be able to export this design into EventCatalog (or any other tool), and use your designs as a living reference.
Using the documentation editor you can reference any node in your canvas. This lets you document your design and link to resources in your designs to guide your end users through the flow of your design. Helping them understand your architecture, choices, and changes.
Similar to Figma, you will be able to leave comments on your designs, join the conversation and get feedback. Everything in your design is version controlled.
You will be able to import all resources from your EventCatalog documentation into your canvas. This will allow you to create new drafts, designs and ideas using your architecture patterns and components you already have. Giving you a foundation to start for new ideas, get feedback on schema design and much more….
Getting access to EventCatalog Studio
We are aiming to get EventCatalog Studio released very soon. If you would like to try it out you can sign up to our beta here https://studio.eventcatalog.dev/
EventCatalog documentation is helping teams govern and discover their architecture. EventCatalog Studio can help teams design, gather feedback and explore ideas. We want to make governing event-driven architecture easier, and we are super excited to see what you all think to EventCatalog Studio.
Recent fixes and improvements to EventCatalog
New EventCatalog SDK Version
We have released a new version of the EventCatalog SDK. This new feature let’s you programmatically create entities in EventCatalog. This means you can create entity maps in EventCatalog from any source you have.
To get started, you can read the EventCatalog SDK documentation.
Other improvements to EventCatalog
- EventCatalog visualizer is now ready to import designs from EventCatalog Studio.
- Architecture pages for messages, services, and domains are now single column.
- Added support for avsc files in changelog diffs.
- SchemaViewer now supports array rooted schemas.
- Reduced pagesize of EventCatalog.
What’s coming in September?
In September, we are focused on releasing EventCatalog Studio. We are also focusing on implementing offline license checks (for those that want to use EventCatalog in regulated environments) and exploring support for Azure messaging services, Azure Schema Registry, and Apicurio Schema Registry.
We are also exploring and working on notifications. These will be webhook notifications you can setup and listen to when things in your catalog change. Examples of these are schema changes, breaks, new versions, etc. Use cases include:
- Teams getting notified when a new version of a schema is published.
- Trigger contract tests or infrastructure when schemas change.
- Provision new infrastructure when a new version of a service is published.
- Trigger a build when a new version of a service is published.
If you have any questions or want to join our community of over 1200 people exploring EventCatalog and event-driven architecture feel free to join us.