Documentation your team will actually trust.
Document your domains, services, events, and schemas in Markdown — with automated updates from your specs where it makes sense.
Open source. Self-hosted. Built for distributed systems.

In distributed systems, documentation is architecture.
When services, events, and schemas are modeled explicitly — with ownership and relationships intact — teams can reason about change before it happens.
Make architectural knowledge easy to find
No more searching across repos to understand the system
Document your domains, services and messages.
Reduce the time it takes to find the information you need.
Search or query your architecture
Use search or ask architectural questions across your catalog — via UI, APIs, or AI tools.

Reduce manual documentation drift
Use your OpenAPI, AsyncAPI or Brokers to automatically generate documentation for your domains, services and messages.
Devs find what they need. Architects see the big picture. PMs finally understand the system
Provide everyone with a unified view of your architecture and business. Document your domains, services, messages and business processes.
Documentation that writes itself — so yours is never out of date
Any specification, any broker, any schema
Import any specification, broker or schema
Add OpenAPI, AsyncAPI, GraphQL, Avro, Protobuf, JSONSchema to your documentation. Help your teams get the information they need.
Know who owns what
Assign your specifications to domains and services. Assign ownership and context of your business and organization. Combine technical details with business context.

Stop writing docs manually
Use your OpenAPI, AsyncAPI or Brokers to automatically generate documentation for your domains, services and messages.
One catalog, every audience
Provide everyone with a unified view of your architecture and business. Document your domains, services, messages and business processes.
Ask your architecture anything
✓ Found OrderCreated event
The following services consume this event:
Updates stock levels when orders are created
Sends confirmation emails to customers
Tracks order metrics and trends
→ View full documentation at /docs/events/OrderCreated
All your documentation in one place
ADR-003: Event-Driven Architecture
ActiveDecision to adopt event-driven patterns for order processing
Payment Service Deployment
RunbookStep-by-step guide for deploying payment service updates
RFC-012: API Versioning Strategy
DraftProposal for standardizing API versioning across services
Start for free
Join the teams behind 28,000+ catalogs
Self hosting documentation and governance for your organization.

