As event-driven architectures scale, an invisible problem emerges: who is producing what, and who is consuming it? A service starts consuming your OrderPlaced event. No ticket. No Slack message. No email. You find out weeks later when something breaks downstream.
At scale, you need governance over these relationships. You need to know when dependencies change, who is affected, and ideally, before it reaches production.
EventCatalog already gives you auto-generated visualizations: Entity Maps, Interaction Maps, and domain views that update as your catalog changes. These are great for understanding relationships between your resources.
But sometimes you need your own diagrams. Target architecture plans. Event storming results. Sequence flows from Miro. C4 diagrams from IcePanel. The stuff that lives in scattered boards, Confluence pages, or that folder someone created two years ago.
EventCatalog 3.3.0 lets you bring those diagrams to your documentation.
Your custom diagrams are now first-class, versioned resources in your catalog. Bring them in from any tool, version them, link them to your domains and services, and even ask AI about them.