Skip to main content
⭐️ If you love EventCatalog, give it a star on GitHub. Thanks!

Introducing EventCatalog v2

· 3 min read
David Boyne
Founder of EventCatalog

Event-driven architectures share a common challenge: their complexity can quickly escalate as more domains, services, and messages are added.

As business requirements evolve and teams adapt, governing and understanding this distributed architecture becomes increasingly difficult. What begins as a straightforward system often transforms into a complex structure with minimal documentation and discoverability, leaving most people struggling to comprehend it (I share my thoughts on EDA complexity in this GOTO EDA Day 2024 keynote).

In January 2022 EventCatalog v1 was launched to help bring discoverability and documentation to event-driven architectures. Since its inception, EventCatalog has seen over 13,000 catalogs created, attracted 45 contributors, grown a community of more than 600 members on Discord and was added to Thoughtworks Technology Radar.

The growing popularity of EventCatalog in recent years highlights the challenges of complexity in building event-driven architectures. It also highlights the importance of discoverability and documentation. That's why I'm excited to announce the release of EventCatalog v2.

EventCatalog V2

Example of EventCatalog v2

EventCatalog (v2) has been completely rewritten from the ground up, incorporating lessons from EventCatalog v1 and introducing a host of new features on a fresh foundation. These enhancements include:

  • A refreshed UI and improved developer experience (demo)
  • Documentation for new resources: domains, services, and messages (commands, events, and soon, queries)
  • Visualizer support for all resources within EventCatalog
  • A new discoverability feature that enables quick filtering and searching for resources in a tabular format (demo)
  • Versioning capabilities for domains, services, and messages
  • New landing pages for users and teams (demo)
  • Rewritten using Astro for faster build times and reduce complexity
  • Hot-reload support for catalog changes
  • New components for your catalogs (read more)
  • Ability to search your catalog (demo)
  • Enterprise support
  • And much more...

This new foundation enables faster development and future feature support, including schema registry, API support, broker integrations (plugins), and more.

If you already have a previous version of EventCatalog you can read the migration guide.

Getting started

You can use the EventCatalog CLI tool you can create an EventCatalog in seconds.

# Install your new catalog
npx @eventcatalog/create-eventcatalog@latest [name]

# Example
npx @eventcatalog/create-eventcatalog@latest my-catalog

Read the installation guide for more information.

Already have an EventCatalog? Read the migration guide.

Introducing enterprise support

EventCatalog now offers enterprise support, this support includes priority support, private support channels, custom integrations, priority feature development and more.

If you are using EventCatalog and would like to work together you can contact us on or read more details on the enterprise support page.

What’s next?

EventCatalog v2 is just the start, next on the roadmap (July 2024) is plugin support and plugin documentation. EventCatalog's vision is to integrate with any broker in the world, which will be powered by custom plugins.

Integrations into EventCatalog

Other features include EventCatalog as a schema registry, API support, single sign on support, hosting options and much more.

If you have an idea for a feature or any questions feel free to raise an issue or join us on Discord.


Complexity in event-driven architectures is inevitable, but we believe it can be managed through effective governance and documentation.

EventCatalog was initially created to assist teams in documenting their event-driven architectures and has proven valuable to hundreds of companies worldwide.

The new version of EventCatalog builds on this vision and mission, offering enhanced tools for managing the complexity of event-driven architectures through improved documentation and discoverability.

We are excited to see the possibilities and path that lie ahead.