Domains
Services
Messages
Schemas
Software primitives
Model architecture as architecture
Treat domains, services, messages, schemas, teams, and flows as first-class resources instead of burying them inside pages, diagrams, and scattered markdown.
NewEventCatalog Editor is now in beta
The open-source catalog for distributed systems
Document, govern, and discover your services, domains, APIs, and events in one place.
EventCatalog helps you document your architecture for engineers and AI
Trusted by engineering teams at
Auth Service
Microservice
Order Service
Microservice
Payments
Domain
Document. Visualize. Query.
One place for your domains, services, messages, and schemas. So your team and AI agents 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.
1 / 4
Your architecture visualized
EventCatalog will visualize your domains, services and messages.
1 / 2
Natural language questions
Ask about your architecture in plain English. Get accurate answers instantly.
1 / 3
“With EventCatalog we now have a clear view of all events and schemas, and we know who to reach out to when we want to consume data.”
Dennis Baerten/Freelance Lead Engineer, Nike
Documentation designed for
software architecture
EventCatalog is not a general documentation tool. It is built around software primitives, domain-driven design practices, and technology-agnostic models for any architecture.
DDD
APIs
Brokers
Teams
DDD and technology agnostic
One catalog for any architecture
Capture bounded contexts, ubiquitous language, ownership, and relationships across whatever stack your organization uses today or adopts next.
Architecture context for AI
Context matters. For your team and your AI agents.
Give engineers and AI agents the same structured architecture context: domains, services, events, schemas, owners, and flows.
EventCatalog MCP
$
Your system has 4 domains:
1.Orders handles order lifecycle
2.Payments processes transactions
3.Inventory manages stock levels
4.Notifications sends alerts and emails
$
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.
Connected automation
In sync with your specifications and schemas
Use OpenAPI, AsyncAPI, and schema registries to generate catalog resources automatically. Teams keep the context, ownership, and language that automation cannot.
Generate from specs
OpenAPI, AsyncAPI, registries.
Stay in sync
Schemas change, docs update.
One command
Run locally or in CI/CD.
SDK & API support
Connect internal systems.
Connect to your stack
terminal
$npm run generate
Fetching OpenAPI specs...
Syncing AsyncAPI definitions...
Pulling schemas from registry...
Done in 2.3s. 47 resources updated.
sequenceDiagram
Mermaid
Canvas
Miro
Whiteboard
c4 Diagrams
Architecture
IcePanel
diagram.svg
Any Tool
Architecture diagrams. Versioned. Discoverable.
Bring your existing architecture diagrams into EventCatalog and treat them as first-class architectural knowledge.
MermaidPlantUMLArchimateMiroIce Panelc4 DiagramsDraw.ioSVG / PNG
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.
team-orders
feat: add OrderCreated event schema
team-payments
docs: update PaymentService API
team-inventory
fix: correct StockUpdated schema
main
Merge: Build unified catalog
Deploy successful
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.
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.
Dustin Cole
Datawake (datawake.io)
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.
Bart Kardol
Essent
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.
Dennis Baerten
Freelance Lead Engineer at Nike
EventCatalog, together with AsyncAPI and other specs, makes sure your architecture stays controlled, preventing it from spiraling into chaos.
Fran Mendez
Creator of AsyncAPI
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.
Adam Fanello
Strategic Cloud Software Architect, Rackspace Technology
EventCatalog is my go to solution when I introduce event-driven architecture to an audience.
Ruben Fonseca
Senior Solutions Architect, AWS
EventCatalog helps to bridge the gap between a PO's business view and an Engineer's technical view.
Jan Wagebach
PRISMA, CTO
33,000+
Catalogs created
2,700+
GitHub stars
1,200+
Community members
40+
Contributors
0+
Catalogs created
0+
GitHub stars
0+
Community members
0+
Contributors
Start building
Make your architecture discoverable.
Docs-as-code for architecture. Open source, self-hosted, and no lock-in.
$
npx @eventcatalog/create-eventcatalog@latest my-catalogOpen source
Your data, yours
Deploy anywhere