Know what exists.
Know who owns it.
Know how it connects.
EventCatalog is the architecture catalog for distributed systems, making your domains, services, events, and schemas discoverable by your team and your AI tools.
Trusted by engineering teams at
Your architecture grows. Discoverability doesn't.
These problems get worse with every new service, every new team, every new schema.
You don't know how your architecture connects.
Nobody knows where to look, or what reflects reality.
Schema sprawl makes discoverability impossible.
No one knows where the schemas are, or what they look like.
Duplication of effort across the organization.
Teams build the same integration because nobody knew it already existed.
A schema changes without warning.
You find out in production.
Knowledge lives in docs, Slack, and people's heads.
New engineers spend weeks piecing it together.
Documentation tools aren't designed for architecture primitives.
Off-the-shelf docs treat your architecture like any other page. Events, services, domains, and schemas deserve more.
Your architecture needs a catalog, not another wiki.
Document. Visualize. Query.
One place for your domains, services, events, and schemas. So your team can find what exists, who owns it, and how it connects.
Powered by markdown
Store documentation in your Git repository. Version controlled and developer-friendly.
Natural language questions
Ask about your architecture in plain English. Get accurate answers instantly.
Powered by markdown
Store documentation in your Git repository. Version controlled and developer-friendly.
Your architecture visualized
EventCatalog will visualize your domains, services and messages.
Natural language questions
Ask about your architecture in plain English. Get accurate answers instantly.
Document your entire architecture
EventCatalog is purpose-built for architecture, not implementation details. Document and discover your system without coupling to any specific codebase or tooling.
Your schemas change.
Your docs update automatically.
Pull from OpenAPI, AsyncAPI, and schema registries to keep generated docs in sync. Diagrams, context, and language stay human-owned.
Generate from your specs
Use OpenAPI, AsyncAPI, and schema registries as inputs to generate and update services, events, and schemas without duplicating work.
Stay in sync
When schemas change, generated content updates automatically. Your diagrams, descriptions, and relationships stay exactly as you wrote them.
One command
Run npm run generate locally or in CI/CD. One command refreshes everything.
SDK & API support
Extend EventCatalog to integrate with any system in your stack. If you can extract architectural data, you can model it.
Architectural context stays intentional.
Connect to your stack
Docs always in sync
Add to CI/CD and automate your documentation so you never have to think about it again.
Context matters. For your team and your AI.
Help engineers find answers faster, and give AI tools the structured context they need to understand your architecture.
Your team asks in Slack. Your AI asks via MCP.
Both get answers from the same source of truth.
Your data never leaves
Self-hosted and secure by default. Your architecture, your queries, your AI context all stay on your infrastructure.
Built-in MCP Server
Ask Cursor “what services consume OrderCreated?” and get a real answer. Works with Claude, VS Code, Windsurf, or any MCP-compatible tool.
Bring Your Own Models
You own your models and your data. Connect OpenAI, Anthropic, or any LLM. Your architecture context stays private.
llms.txt, generated for you
Every build produces an llms.txt file so any AI agent can discover your architecture without custom integrations.
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.
Make your architecture discoverable.
Docs-as-code for architecture. No lock-in.
npx @eventcatalog/create-eventcatalog@latest my-catalog