event-catalog/eventcatalog
Documentation tool built for software architecture. Document your domains, services, events and schemas — for your teams and your AI agents. observed · 2026-08-28
Health v2 · maintenance only
95/100
- Activity 99
- Release rhythm 87
- Longevity 100
Flags: no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 0.0
- age_days: 1749
- days_rel: 9
- days_push: 9
- n_releases_24m: 727
Adoption not part of the score
2841 stars · 272 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
EventCatalog is an open-source documentation tool purpose-built for software architecture, letting teams document domains, services, events, messages, flows, and schemas as structured, versioned resources stored in Git. It generates a searchable, visualizable architecture catalog with integrations for OpenAPI, AsyncAPI, GraphQL, and schema registries, plus AI-powered discovery via a built-in chat and MCP server.
Use cases
- document event-driven architecture with domains, services, and events
- generate service and event documentation from AsyncAPI or OpenAPI specs
- search and explore schemas like Avro, Protobuf, and JSON Schema across a catalog
- give AI agents and LLMs context about system architecture via MCP
- map producers and consumers of messages across microservices
- track architecture decision records alongside services
- federate documentation from multiple team repositories into one catalog
- detect breaking changes in event schemas before production
When to choose
- you run event-driven or microservice architectures and need a living service/event catalog
- your architecture knowledge is scattered across wikis, spreadsheets, and Slack
- you want docs generated and synced from OpenAPI, AsyncAPI, or schema registries
- you want to expose your architecture to AI agents and developer tools
When to avoid
- you only need generic wiki-style documentation pages
- you need a lightweight API reference tool without architecture modeling
- you require federation, SSO, or advanced automation without a commercial license
Facets
application · maturity active
documentation api-documentation search-engine data-visualization mcp plugin-system developer-tools documentation microservices apis cross-platform self-hosted cli event-driven-architecture asyncapi openapi schema-registry domain-driven-design architecture-catalog service-catalog mcp-server ai-agents visualizer backstage eventcatalog architecture nodejs web-server
9 sources
- readme: https://github.com/event-catalog/eventcatalog · fetched 2026-08-28 · eddd6f8e5e6b
- homepage: https://eventcatalog.dev · fetched 2026-08-29 · 2c0387d48db0
- site_page: https://www.eventcatalog.dev/docs/development/getting-started/installation · fetched 2026-08-29 · 5558515fa4a4
- site_page: https://www.eventcatalog.dev/docs/development/getting-started/introduction · fetched 2026-08-29 · f19ff2a0ba4e
- site_page: https://www.eventcatalog.dev/pricing · fetched 2026-08-29 · f4aaf0649c0e
- site_page: https://www.eventcatalog.dev/federation · fetched 2026-08-29 · 9474631babac
- site_page: https://www.eventcatalog.dev/book-demo · fetched 2026-08-29 · 3362c3a5f01d
- site_page: https://www.eventcatalog.dev/integrations · fetched 2026-08-29 · 64c26da1b247
- site_page: https://www.eventcatalog.dev/changelog · fetched 2026-08-29 · 9ea25a320dc8
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| event-catalog/eventcatalog | main | 95 |
For agents
markdown · JSON · MCP: product_card(name="event-catalog/eventcatalog")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem