Your architecture is a system.
Stop documenting it like pages.
Wikis and diagrams flatten your architecture into disconnected documents. EventCatalog models it as it really is: domains, systems, services, APIs and events, connected, versioned, and explorable by every team.
npx @eventcatalog/create-eventcatalog@latest my-catalog
Motorway
AWS
Nike
GOV.UK
Flipdish
Eurostar
EverQuote
PayPoint
PayFit
Worldpay
Airtime
Booksy
NHS
Costco
Deel
American Logistics
Prisma
MazdaThe knowledge exists. It’s just scattered.Ownership lives in a spreadsheet. Diagrams in Miro. Schemas in a registry. Context in someone’s head, answered one Slack thread at a time. Nobody can see the whole system.
Give everyone a shared understanding of your architecture. Every service gets a real home. Owners, messages, schemas, dependencies, and decisions live on one page that is part of the model, not a wiki island.
Give systems, domains, services, events, and flows first-class structure.
Attach systems, owners, decisions, and guidance directly to the architecture they describe.
+2Start in markdown. Automate when you're ready. Your catalog lives in git beside your code. Generate it from OpenAPI, AsyncAPI, and schema registries, or build your own workflow with SDKs, on your infrastructure.
OpenAPIAPI specifications
AsyncAPIEvent specifications
ConfluentSchema Registry
AWS GlueSchema Registry
AzureSchema Registry
GitLabMarkdown and CI
Apache KafkaTopics and schemasCart API
The public-facing API for shopping carts. Handles commands to add and remove items and publishes an event when a cart is checked out.
Overview
The Cart API is the front door to the Cart System. It persists cart contents to the Cart Database, asks the Promotion System to calculate discounts, and publishes Cart Checked Out.
Responsibilities
- Validate incoming cart commands
- Persist cart contents and checkout state
- Publish checkout events to consumers
Connected architecture
Use integrations, generators, and SDKs to build your catalog around the tools your teams already use.
Use integrations, generators, and SDKs to update your catalog whenever specifications, schemas, or repositories change.
See your architecture as a connected model. Save your team hours of manual discovery by making every service, event, API, data store, and relationship immediately visible.
Runs the checkout saga
Create a new order
Cancel an existing order
Fetch a single order
The system of record for orders
PostgreSQL order data
A new order was created
An order was fulfilled
An order was cancelled
Coordinates fulfilment
Start with the domain view, then zoom into systems, services, and the messages they exchange.
Review pull requests against your architecture documentation to catch breaking changes and affected consumers before merge.
Stop searching. Ask your architecture. Get grounded answers about ownership, dependencies, schemas, and change impact in natural language—without digging through pages or interrupting another team.
Orders Service
Service that handles orders
Overview
The Orders Service manages customer orders, status tracking, and interactions with Inventory Service, Payment Service, and Notifications.
This service is part of the Orders domain and works with the Order entity.
Search the model in the browser or bring its context into your IDE through MCP.
Scope MCP servers to a domain or system so teams and AI tools get focused, trusted architecture information exactly when they need it.
Govern the model as your architecture evolves. Make ownership, dependencies, standards, and the impact of every change explicit.
Document ADRs, assign them to resources and teams, and see where each decision applies across your architecture.
EventCatalog Agents review schema changes against your architecture, flag breaking changes, and identify affected consumers before merge.
Start with one team. Skip the Confluence sprawl. Scale when you’re ready.
Create your first catalogOpen source. Used by teams around the world.Self-host EventCatalog and keep full ownership of your architecture documentation and data.
Trusted by teams building complex systems.What architects and engineers say about EventCatalog.
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 BaertenFreelance Lead Engineer at NikeNikeYour architecture is a system. Document it like one.
Rolling out across many teams? Talk to us about Enterprise or see pricing.