ABOUT OCTORYN

A shared model layer for the Octopus family.

Octoryn Router is an Octopus Core platform capability built for Octopus customers and the Octoryn product family. It gives applications one governed way to reach changing model supply without importing product code into the router.

011 APIshared application contract

02Policybefore provider dispatch

03Sydneyindependent production stack

04Octopuscustomers and product family

Why the router exists

AI applications need models to change faster than product integrations should. Octoryn separates the stable interface used by products from provider selection, availability and operational policy.

Keep a familiar OpenAI-compatible API surfaceExpand details
This is part of Why the router exists. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Move provider choice behind reviewed routing policyExpand details
This is part of Why the router exists. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Avoid reverse imports from the router into product applicationsExpand details
This is part of Why the router exists. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Give family products a consistent operational boundaryExpand details
This is part of Why the router exists. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Built by Octopus Core

Octoryn Router belongs to the Octopus Core platform context. Its first responsibility is dependable model access for Octopus customers and the Octoryn family—not a consumer marketplace or a bundle of unrelated application features.

Designed around managed customer environmentsExpand details
This is part of Built by Octopus Core. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Independent production deployment and release lifecycleExpand details
This is part of Built by Octopus Core. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Shared standards across the Octoryn familyExpand details
This is part of Built by Octopus Core. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Clear boundary between infrastructure and product codeExpand details
This is part of Built by Octopus Core. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Different by design

Octoryn adopts useful conventions from model routers while prioritising the needs of the Octopus environment: policy aliases, regional control, customer-owned provider access and an auditable path from product to provider.

Capability-led routing instead of provider lock-inExpand details
This is part of Different by design. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Governed aliases that products can depend onExpand details
This is part of Different by design. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Regional and provider eligibility controlsExpand details
This is part of Different by design. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Operational evidence for managed deploymentsExpand details
This is part of Different by design. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

A focused platform surface

The router remains intentionally separate from billing products, marketplaces, content studios, agent memory and product databases. Those capabilities may consume the API; they do not become part of its runtime.

A narrower security and deployment boundaryExpand details
This is part of A focused platform surface. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
No product-side database ownershipExpand details
This is part of A focused platform surface. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
No coupling to one Octoryn applicationExpand details
This is part of A focused platform surface. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
A reusable API for customers and family productsExpand details
This is part of A focused platform surface. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

OCTORYN ROUTER

See the platform from the application side.

Explore the interface, routing concepts and integration patterns used across the Octoryn family.

Open developer docs