Fits existing tools
No parallel authoring surface. The source of truth stays where teams already work.
Source-connected OpenAPI publishing
Point Manja at your spec.
Manja tracks the source, understands revisions, renders the OpenAPI reference, and keeps the public version stable. Say where the spec lives; the rest should fall into place without asking developers to change their workflow.
- Publication source
- last known good
- Repository
- github.com/acme/platform-api
- Spec path
- docs/openapi.yaml
- Revision
- refs/tags/v2026.06
- Public docs
- api.acme.test/docs
Connect source
Use the repo, ref, credentials, and spec path developers already maintain.
Discover versions
Branches, tags, commits, and singleton file sources become selectable revisions.
Index OpenAPI
Operations, schemas, routes, snippets, and examples are derived from the spec.
Publish deliberately
Public readers see the chosen version, even if a later sync or parse fails.
Versions stay close to source
Branches, tags, commits, and singleton spec files become publication candidates without moving ownership out of source control.