Turn your architecture into a story
your teams and AI tools can understand
Stop wrestling with outdated docs and missing schemas. EventCatalog turns your architecture into a living system that actually helps your team ship faster.
End the schema scavenger hunt
Stop digging through Slack threads and stale wikis. Find or ask about any event, service, or domain in seconds — with full context and ownership.
Documentation that stays current
Auto-generate from AsyncAPI and OpenAPI specs, schema registries and more. No more outdated documentation.

Scale without documentation debt
Markdown + MDX + Git = documentation that scales with your team. Enriched documentation powered by markdown.
Empower collaboration across teams
Self-service discovery for everyone—from architects, developers to product managers. Visual diagrams that actually make sense.
Helps engineers find what they need in minutes, not days
Your documentation is scattered, out of date, or missing entirely. Your team spends hours asking questions, re-learning the system, and fixing avoidable bugs. EventCatalog fixes that.
Update docs like you update code
Write and maintain documentation in Markdown or MDX—keeping it current as your architecture evolves.
See what changed
Track changes to events, schemas, and services over time, just like your code.
AI Integrations
Bring your own models to EventCatalog itself. Connect your architecture documentation to your AI tools.
Works with your stack — Kafka, SNS, EventBridge, whatever
No rip-and-replace. Connects to what you already use.
Grows with you — 10 services or 1000
Grow documentation across teams, projects, and services without losing clarity.
See your entire system at a glance
See the full picture: services, events, and ownership in one connected map.
Your specs change. Your docs update automatically.
Architecture diagrams. Versioned. Discoverable.
Bring your existing architecture diagrams into EventCatalog — and treat them as first-class architectural artifacts.
Import or link diagrams from Mermaid, Miro, IcePanel, C4 models, draw.io, SVG, and more. We don’t replace your tools — we connect them.
Version your diagrams alongside your docs
Track changes to your architecture diagrams over time. See how your system evolved from v1.0 to today.
Stored in Git. You own everything.
Your diagrams live in your repository. No vendor lock-in, no external dependencies. Perfect for regulated industries.

Searchable and discoverable
Your diagrams become part of your searchable catalog. Find the right diagram when you need it, not buried in a wiki.
AI-ready architecture diagrams
Connect your diagrams to AI tools. Let your models understand your architecture visually and contextually.
How teams go from chaos to clarity
Architecture shouldn’t end with documentation. With EventCatalog, every decision, diagram, and change fuels a continuous cycle of clarity, design, and evolution.
Document
Create an authoritative source of truth your teams can trust. Capture domains, services, and events once — so knowledge isn’t lost in slides, confluence pages, or tribal memory.
Visualize
Give every team a shared understanding of how the system really works. Turn your architecture into a searchable, explorable map every team can understand.
Design
Design using real architecture - not blank canvases. Reuse your existing architecture to plan changes, discover impact, and evolve safely with EventCatalog Studio.
Loved by architects and engineers
Why teams choose EventCatalog
Trusted by engineers and architects building complex systems.
EventCatalog has been a game-changer for how we think about and communicate our architecture. Within days of adopting it, our entire system became something anyone on the team could actually understand and reason about. It's the rare tool that's a joy to use.

As a team working with DDD and Event-Driven Architecture, keeping everyone aligned on domains, services and message contracts is a real challenge. EventCatalog tackles this head-on. We use it both as a company-wide architectural overview and as living documentation generated directly from our code. It is one of those rare tools that genuinely fits how we think about software.

At my current project we have a large event-driven architecture setup with more than 100 events across different domains owned by multiple teams. With EventCatalog we now have a clear view of all events and schemas — and more importantly, we know who to reach out to when we want to consume data.

EventCatalog, together with AsyncAPI and other specs, makes sure your architecture stays controlled, preventing it from spiraling into chaos.

Creating easy to maintain and easy to consume API and event documentation that is always up to date has been one of the most consistent challenges of my career. EventCatalog has become the keystone tool to finally make it possible.

EventCatalog is my go to solution when I introduce event-driven architecture to an audience.

EventCatalog helps to bridge the gap between a PO's business view and an Engineer's technical view.

Join our community
Connect with developers, share ideas, and contribute to the future of event-driven architecture
Join our Discord
Ask questions, get help, and share your ideas with the community. Connect with other developers building event-driven systems.
Open Source
EventCatalog is open source. Explore our codebase, weigh in on RFCs, and contribute on GitHub.
Ready to get started? Try EventCatalog today
Get Started Now




