Data & API catalog

Living documentation from your existing schemas

Turn the schemas you already publish into searchable documentation, relationships and architecture views.

As your systems change, the catalog changes with them.

Living documentation

Orbital turns the schemas you already publish into a searchable catalog of your APIs, data and relationships.

See where a data concept appears, which services use it, and how everything connects.

Pull schemas from Git, or publish them directly from your services.

Orbital indexes them automatically, so the catalog changes when your schemas do.

Generate interactive diagrams from the services and schemas in Orbital.

Follow the relationships between APIs, databases and the data they expose.

See every change to your APIs and schemas, and when it happened.

Track what changed and which connected services are affected.

Put interactive schema diagrams and runnable queries inside your documentation.

Link directly into the catalog, so the docs stay tied to the systems they describe.

Got another gnarly question? We’d love to hear it. Come and chat on Slack.

: Orbital supports OpenAPI, Protobuf, Avro, SOAP, JSON Schema, database schemas, Taxi and more.
The catalog brings them together into a single view, regardless of how each service describes its data.
: Schemas can be read from Git or published directly by your services as part of deployment.
The same schemas are used by Orbital at runtime, so documentation and integration are driven from the same source.
: Orbital understands the meaning of types and fields, not just their names.
That means you can find a concept across different systems, see where it is produced and consumed, and follow the relationships between APIs and data sources.
: Yes. You can start with Orbital as a catalog and semantic layer, then introduce querying, integration and other capabilities when they become useful.

Point Orbital at a Git repository or push from a service, and the catalog builds itself.