Skip to main content

Stability and Support

This is the first public version of the Orqio Developer Docs. The goal is to give you stable integration boundaries from day one, while keeping the platform flexible enough to evolve quickly.

Stable boundaries you can depend on​

As a general rule, you can safely build against:

  • The API contracts described in the API Reference (OpenAPI)
  • The public docs in this site (guides + reference pages)
  • The public examples in the Examples section
  • Use staging for all validation and experimentation
  • Promote to prod only after successful staging runs
  • Keep credentials/API keys separate per workspace
  • Review the changelog before production releases

How changes are communicated​

User-visible changes are tracked in the Changelog.

If you operate an integration in production, make changelog review part of your release process.

Out of scope for this site​

To keep the public docs focused and safe to depend on, this site intentionally excludes:

  • Internal infrastructure topology
  • Internal deployment procedures
  • Internal-only runbooks and operational playbooks

If you need clarity on a missing integration contract, treat that as a signal that the boundary should be documented—reach out through your Orqio contact/support channel.