Make your software architecture discoverable.
EventCatalog is documentation for software architecture — designed to make domains, services, events, and schemas discoverable by humans and machines across distributed systems.
Self-hosted · Open source · Your data stays yours
Trusted by engineering teams worldwide — 28,000+ catalogs created
Why architecture becomes hard to discover.
Your architecture grows. Discoverability doesn’t.
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.
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.
Making architecture discoverable requires a different approach.
Making architecture discoverable in practice
EventCatalog helps teams model architectural knowledge in one place — making ownership, relationships, and key primitives discoverable as systems evolve.
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 models architectural primitives — not implementation details — so teams can document and discover their architecture without coupling to code or tooling.
Reduce drift between your architecture and your schemas
Pull schemas from OpenAPI, AsyncAPI, and schema registries — while keeping architectural context, diagrams, and language intentional and 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, EventCatalog can refresh the generated parts of your catalog — while preserving manually curated diagrams, language, and relationships.
One command
Run npm run generate locally or in CI/CD to refresh generated content from your connected systems.
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.
Empower engineers to find answers faster — and give AI models the context they need to understand your distributed system.
Ask structured questions about domains, services, events, schemas, and dependencies — using the same architectural model.
Privacy First
Self-hosted and secure by default — your architectural data never leaves your infrastructure.
MCP Server Integration
Expose your architectural model via MCP — enabling tools like Claude, Cursor, and VS Code to query your system structure.
Bring Your Own Models
You own your models and your data. Connect any LLM and bring your own tools to extend capabilities.
llms.txt Auto-Generation
Automatically generate llms.txt files so AI agents can discover and understand your architecture when needed.
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
Track how your architecture diagrams evolve over time — alongside services, schemas, and events.
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.
Machine-readable architecture diagrams
Because diagrams are linked to real architectural primitives, AI tools can explain flows, dependencies, and responsibilities — not just render images.
EventCatalog adapts to how your teams work
Trigger catalog builds from anywhere. EventCatalog integrates into any Git-based workflow — across teams, repos, and pipelines — and can be rebuilt as often as your architecture changes.
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
Distributed teams
When teams update their specifications or schemas in their own repositories, the catalog updates as part of their existing workflow.
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.
Ready to get started?
Get started in minutes. Self-hosted, open source, and your data stays yours.
No credit card required. Deploy on your own infrastructure.