MODEL DIRECTORY

Choose capabilities. Route by policy.

Octoryn gives every workload a stable alias, then applies your quality, latency, residency and cost rules behind it. Applications stay portable while model supply can evolve.

011 APIOpenAI-compatible interface

02Stablepolicy aliases for applications

03AUregional routing controls

04BYOKcustomer-owned provider access

A directory of capabilities, not logos

Start with the job your application needs done. Octoryn organises routing around durable capability categories instead of coupling product code to a provider or a short-lived model name.

Reasoning and general-purpose workloadsExpand details
This is part of A directory of capabilities, not logos. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Tool use and structured outputsExpand details
This is part of A directory of capabilities, not logos. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Vision and multimodal inputsExpand details
This is part of A directory of capabilities, not logos. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Low-latency and interactive pathsExpand details
This is part of A directory of capabilities, not logos. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Stable aliases are the application contract

Aliases such as policy/frontier, policy/fast and policy/residency describe operational intent. Their backing supply can be evaluated and changed without requiring a release across every Octopus product.

Version routing policy independently from application codeExpand details
This is part of Stable aliases are the application contract. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Move supply without changing SDK integrationsExpand details
This is part of Stable aliases are the application contract. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Use controlled fallbacks when eligible routes are unavailableExpand details
This is part of Stable aliases are the application contract. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Review policy changes before production rolloutExpand details
This is part of Stable aliases are the application contract. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Region and data policy travel with the request

Routing decisions can account for where inference is processed, which providers are eligible and how data may be handled. Governance is part of route selection rather than an application-side convention.

Regional and residency constraintsExpand details
This is part of Region and data policy travel with the request. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Provider allowlists and deny rulesExpand details
This is part of Region and data policy travel with the request. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Retention and data-handling requirementsExpand details
This is part of Region and data policy travel with the request. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Auditable policy decisions for managed environmentsExpand details
This is part of Region and data policy travel with the request. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Bring keys without giving up control

BYOK routes let customers use authorised provider accounts while Octoryn remains the governed access layer. Credentials stay separated from product code, and usage follows the same policy and audit path.

Customer-owned provider credentialsExpand details
This is part of Bring keys without giving up control. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Workload and environment separationExpand details
This is part of Bring keys without giving up control. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Budgets, quotas and access controlsExpand details
This is part of Bring keys without giving up control. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Consistent observability across eligible routesExpand details
This is part of Bring keys without giving up control. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

OCTORYN ROUTER

Define the route your products can depend on.

Start with a capability and operating policy. Octoryn turns it into a stable application contract.

Open developer docs