
Octri is a platform for teams that publish an API. It takes an OpenAPI specification and produces four things from it: a documentation site, client SD
Polished docs and production-ready SDKs in 10 languages from your OpenAPI spec, with error reporting your SDK users can switch on.
No. Plans are not per-product, so you can leave one switched off and turn it on months later without redoing anything you have already set up.
Your users install a client with an error reporter that ships switched off. Once the developer using it enables reporting, an error in production reaches you tagged with the SDK version, the language and the method that failed. Ingress is metered, so a very chatty SDK counts against your plan’s monthly allowance.
Yes, and regeneration works around your edits. Docs changes are stored per page, so a new spec revision only disturbs the endpoints that actually changed. Custom SDK code is available on Growth and above.
GitHub sync defaults to a draft with a diff for you to review. When you publish a release, SDKs publish to linked registries after the build finishes if registry auto-publish is on. You can turn that switch off and publish packages manually.
No.
Octri is hosted today. Self-hosted generation and docs rendering are not available yet.
Most of a day for a normal docs site. The importer rebuilds your structure from the config you already have. What takes real work is anything hand-built on top of it, like custom components or bespoke pages.