Skip to main content

Whats new in EventCatalog - May 2025

· 8 min read
David Boyne
Founder of EventCatalog

Welcome to the monthly update for EventCatalog, here you can find what’s next, how to get started, and what’s coming next.

Subdomain support to EventCatalog

Many users of EventCatalog come from a Domain-Driven Design (DDD) background and rely on domains to organize their resources. To better support this approach, we’re excited to introduce subdomains.

Subdomains provide an additional layer of flexibility, allowing you to group resources within domains. When you create a subdomain in EventCatalog, it will be displayed as part of the parent domain, enabling a clearer structure and easier navigation between domains and their subdomains.

If you’re following Domain-Driven Design (DDD) practices, subdomains can help you better organize your resources. You can find more details on how to get started in our documentation.

Introducing EventCatalog Reports

We believe that establishing strong governance foundations is essential when building an event-driven architecture. This includes setting clear naming conventions, defining schema versioning strategies, establishing ownership, documenting producer/consumer relationships, and much more.

Unfortunately, many teams skip over governance early on—only to face the consequences later. Without governance, architectures often suffer from poor discoverability, a lack of shared understanding, and missed opportunities for delivering value.

EventCatalog already helps teams achieve better discoverability through documentation, schemas, visualization, and ownership. With the introduction of EventCatalog Reports, you can now track and monitor governance across your organization, ensuring your event-driven architecture stays healthy and aligned.

EventCatalog Reports generates a PDF that highlights areas where your governance practices could be improved across your documentation and architecture (see demo). These insights include:

  • Schema completeness across your services and messages
  • Identification of parts of your architecture that lack clear ownership
  • Detection of services using outdated versions or deprecated messages
  • And much more.

Learn more about EventCatalog Reports in our announcement blog post here.

Need help with your governance?

Many companies ignore governance until it's too late. We can work with you to get your governance in place with custom workshops and support. If you are interested to explore more, feel free to get in touch at hello@eventcatalog.dev

New GitHub Plugin for EventCatalog

Many teams use GitHub as their schema registry, and now EventCatalog makes it easy to integrate with your GitHub repositories. Our new plugin allows you to pull and sync schemas directly from GitHub into EventCatalog, ensuring your documentation stays up to date with your source of truth.

Watch the video to see it in action, or read the documentation to get started.

New Confluent Schema Registry

We’re excited to announce that you can now pull and sync schemas from Confluent Schema Registry directly into EventCatalog.

This integration allows you to keep your documentation and architecture in sync with your source of truth. With support for custom filters, you can easily select which schemas to pull—giving you full control over which messages get updated and how they are assigned within EventCatalog.

Watch the video above for a quick demo, or read the documentation to get started.

Bring your own models to EventCatalog Chat

EventCatalog Chat now supports OpenAI, Gemini, and Anthropic models.

This integration allows you to connect your own AI models with EventCatalog and gain insights into your architecture through natural language—helping you ask questions, understand relationships, and explore your event-driven system more intuitively.

EventCatalog Growth

With EventCatalog, you can ask questions, define custom prompts, and much more—giving you a powerful way to explore and interact with your event-driven architecture.

To get started you can read the documentation.

Entities are now supported in EventCatalog

In Domain-Driven Design (DDD), entities are the core building blocks of a domain. They represent key concepts or objects—like Order, Customer, or Invoice—that have a unique identity and persist over time. Each entity lives within a bounded context, ensuring it adheres to the specific business rules and logic of that part of the system.

With this release, EventCatalog introduces Entities as a new resource type. You can assign entities to domains and services, helping your teams better understand the concepts they work with. This makes it easier to build a shared understanding of your architecture and the real-world ideas it models.

If you want to get started with entities you can read the documentation.

Add multiple specifications to your services

EventCatalog now supports adding multiple specifications to a single service. This is especially useful for teams managing services that expose several interfaces—such as APIs, events, and schemas—under the same service.

By assigning multiple specifications to a service, EventCatalog will display them for your users in a clear and organized way—helping your team better understand the capabilities and responsibilities of each service.

If you want to get started with multiple specifications you can read the documentation.

EventCatalog Visualizer updates

Swap between multiple versions in Visualizer

We’ve added the ability to switch between different versions of your architecture directly in the EventCatalog Visualizer. Using a simple dropdown, you can navigate across as many versions as you need—making it easy to compare changes, track evolution, and spot differences over time.

Embed multiple Visualizers into your documentation

You can now embed multiple Visualizers within your documentation. This allows you to embed any domain, service, or message—giving your team rich, visual context directly alongside your written documentation.

This feature is perfect for helping teams explore and understand your architecture more easily, all within the same place.

You can see an example of the customised homepage for EventCatalog.

Copy markdown from any page in EventCatalog for your LLMs

A new pattern emerging in documentation is the ability to copy a page’s markdown for use in LLMs. We’ve made this easy in EventCatalog by adding a dropdown on every page—letting you quickly copy markdown to your clipboard for use in AI models or other tools.

In addition, you can view any page as markdown and copy schemas to your clipboard just as easily.

Other project improvements

What’s coming in June?

In June, we’re releasing more integrations for EventCatalog, including support for Azure messaging services, Azure Schema Registry, and Apicurio Schema Registry. These integrations will allow you to add semantic meaning to your schemas and keep them in sync with your documentation—making it easier for teams to find the information they need and maintain a shared understanding of your architecture.

We’re also exploring improvements to the EventCatalog MCP server and working to bring EventCatalog closer to the tools your teams already use, like Slack and Azure Chat.

We are exploring CI/CD GitHub actions to help find governance problems before they reach your environments.

Many teams use EventCatalog as a design > implement > document workflow. We’re exploring ways to make drafting messages, services, and resources directly in EventCatalog easier—and we expect to release the first version of this feature in June.

Lastly, we know many of you are eagerly waiting for EventCatalog Studio. We’re still hard at work on it and aim to release an initial version soon. Stay tuned!

If you have any questions or want to join our community of over 1150 people exploring EventCatalog and event-driven architecture feel free to join us!