Federated catalog
Teams own their catalogs.
They federate into a central catalog for organization-wide visibility.
A federated catalog gives every team their own EventCatalog—their domains, their services, their schemas—then merges them into a single, central catalog that the whole organization can browse.
Each team keeps full control of their slice. They version it in their own repo, ship it on their own cadence, and document their architecture the way that fits their domain.
The central catalog stitches every team-owned catalog together so anyone in the company can navigate the whole architecture from one place—without forcing every team to work in lockstep.
Built for autonomous teams
Federation lets each team move independently while still contributing to a shared, organization-wide picture. No single team owns the whole catalog—everyone owns their part of it.
How it works
Teams own their catalog
Each team runs their own EventCatalog in their own repository, with their own review process.
Federate into central
Team catalogs are pulled into a central catalog automatically—no manual copying, no drift.
One organizational view
The central catalog stitches every team's contribution into one navigable architecture.
Scale without bottlenecks
New teams plug in their own catalog without waiting on a central platform team to onboard them.
Benefits
Teams own their documentation
Engineers document the systems they actually build. No central team writes about code they don't own.
Scale through team-aligned patterns
Documentation grows with your org. Each team scales independently using the same patterns and standards.
Independent release cadence
Each team ships catalog changes on their own schedule, without coordinating a central release.
Clear ownership boundaries
Every domain, service, and event has an obvious owner. No ambiguity about who maintains what.
Cross-team discovery
One central place to discover events, services, and APIs across every team—without jumping between tools.
Lower platform overhead
The platform team curates standards, not content. Teams contribute documentation directly.
Use it for
Common scenarios where federation is a better fit than a single, monolithic catalog.
Large engineering orgs
Hundreds of services across dozens of teams—where one central catalog would become a bottleneck.
Domain-driven teams
Teams aligned to bounded contexts that already own their roadmap, repos, and on-call.
Mergers and acquisitions
Bring acquired teams onto the same map without forcing them to migrate their tooling first.
Ready to federate your architecture?
Let every team own their catalog while still giving the whole organization one place to discover, navigate, and govern your architecture.