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.
Self-hosted · Open source · Your data stays yours
npx @eventcatalog/create-eventcatalog@latest my-catalogTrusted by teams at Nike, AWS, GOV.UK, and more. 31,000+ catalogs created
Your architecture grows. Discoverability doesn't.
These problems get worse with every new service, every new team, every new schema.
You need to understand how services connect.
Nobody knows where to look, or which view reflects reality.
You need to find the owner of a service.
It takes longer than fixing the bug.
Three teams build the same integration.
Nobody knew it already existed.
A schema changes without warning.
You find out in production.
Data changes upstream without anyone noticing.
Dashboards break. Models drift. Trust disappears.
Knowledge lives across Confluence, Notion, Slack, and people's heads.
New engineers spend weeks piecing together what should be obvious.
Eventually, teams stop trusting documentation at all.
When that happens, every change feels risky. Even small ones.
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.
Generated content stays in sync with your systems.
Architectural context stays intentional.
Connect to your stack
Docs always in sync
Add to CI/CD. Never 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.
Architecture diagrams. Versioned. Discoverable.
Bring your existing architecture diagrams into EventCatalog and treat them as first-class architectural knowledge.
We don't replace your tools. We connect them.
Version your diagrams alongside your docs
See how diagrams looked last quarter, last year, or before the migration. Every version is preserved alongside the docs that explain them.
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
Diagrams are indexed alongside your architecture. Find flows, dependencies, and system views when you need them, not buried in a wiki or slide deck.
Diagrams your AI tools can understand
Because diagrams are linked to real architectural resources, AI tools can explain flows, dependencies, and responsibilities, not just render images.
Fits your workflow. Updates on every push.
Trigger catalog builds from any CI/CD pipeline: GitHub Actions, GitLab CI, Jenkins, or anything else. Teams update schemas in their own repos, and the catalog rebuilds automatically.
feat: add OrderCreated event schema
docs: update PaymentService API
fix: correct StockUpdated schema
Merge: Build unified catalog
catalog.yourcompany.com updated
3 services, 12 events, 4 schemas
Works with any CI/CD
GitHub, GitLab, Jenkins, and more
Each team owns their docs
Teams update specs and schemas in their own repos. The catalog picks up changes on the next build. No central bottleneck.
Fits your pipeline
GitHub Actions, GitLab CI, Jenkins, or any CI/CD tool. EventCatalog integrates without dictating how you deploy.
Trigger on change
Rebuild documentation on schema changes, merges, releases, or on demand. You control when and how architectural changes become visible.
EventCatalog doesn't impose a workflow. It reflects the ones you already have.
Why architects choose EventCatalog
Trusted by engineers and architects building complex systems
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."
"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."
Make your architecture discoverable today.
Install in under 5 minutes. No credit card. No vendor lock-in. Your data stays in your Git repo.
npx @eventcatalog/create-eventcatalog@latest my-catalogFree forever for open source. Deploy on your own infrastructure.