Automated catalog
Pull from schema registries, OpenAPI, AsyncAPI, and custom tooling.
Generate documentation with AI. Keep everything in sync, automatically.
The artifacts that describe your architecture already exist—OpenAPI files in your repos, AsyncAPI definitions next to your services, schemas in your registry, ownership in your IDP. An automated catalog plugs into all of them and turns them into living documentation.
When a schema changes, the catalog updates. When a new service is registered, it shows up. No one has to remember to update the docs—because the docs are generated.
And where automated metadata isn't enough, AI and humans can fill in the gaps—drafting summaries, business context, and ubiquitous language straight from your specs and code.
Always in sync
Wire it up once and the catalog stays current. Build it on demand, on a schedule, or as part of CI—whatever fits your existing pipelines. See integrations for everything we plug into.
Where teams get the most value
Automation + manual context, better together
Machines are great at keeping the mechanical bits in sync. Humans are great at the context that gives those bits meaning. Catalogs that combine both are the ones teams actually use.
Keep mechanical metadata in sync
Anything that already exists somewhere else should never be hand-typed into your docs. Wire it up once and let the catalog mirror reality.
- Schemas from registries (Confluent, Apicurio, AWS Glue, your own).
- API specs from OpenAPI and AsyncAPI files in your repos.
- Topics, subjects, and consumers straight from your brokers.
- Service and ownership data from your IDP, Git repos, and internal tools.
Layer in the context machines can't infer
A schema tells you the shape of a payload. It doesn't tell you why it exists, who relies on it, or how it fits into the business. That's where humans come in.
- Domain information—bounded contexts, sub-domains, and how teams map to them.
- Ubiquitous language—glossaries that align engineers, product, and business stakeholders.
- Business workflows—the end-to-end flows that explain how events tie into customer journeys.
- Decisions and rationale—architectural decisions, deprecations, and tradeoffs that shape your system.
The result: a catalog that's always accurate and always meaningful. Automation removes the toil; manual context makes the docs worth reading.
How it works
Connect your sources
Point EventCatalog at your schema registries, OpenAPI/AsyncAPI specs, Git repos, and brokers.
Sync automatically
The catalog rebuilds on demand, on a schedule, or in CI—so docs always match what's running.
Enrich with AI
Use AI to draft summaries, business context, and ubiquitous language straight from your specs and code.
Customize and extend
Build your own integrations with the SDK to pull from internal tools and bespoke registries.
Use it for
Common scenarios where teams reach for an automated catalog instead of hand-curated docs.
Schema-driven docs
Generate event, message, and API documentation directly from JSON Schema, Avro, Protobuf, OpenAPI, and AsyncAPI.
Live broker visibility
Pull topics, subjects, and consumers from Kafka, Confluent, AWS, and other brokers to keep producers and consumers in sync.
AI-assisted onboarding
Bootstrap documentation for legacy systems by letting AI generate summaries and context from existing specs.
Ready to automate your catalog?
Connect your schema registries, specs, and tools—and let your architecture documentation update itself.