Policy routing

Route every request with intent.

Octoryn gives Octopus customers and family products one stable model interface, then applies the routing rules that matter to each workload.

01PolicyChoose by workload intent

02HealthKeep fallback paths explicit

03RegionRespect deployment boundaries

Stable aliases, changeable supply

Applications call a durable policy alias instead of coupling product code to a specific model endpoint. Routing policy can evolve while the application contract stays familiar.

OpenAI-compatible request surfaceExpand details
This is part of Stable aliases, changeable supply. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Workload-specific policy aliasesExpand details
This is part of Stable aliases, changeable supply. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Provider-independent application codeExpand details
This is part of Stable aliases, changeable supply. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Fallback is part of the policy

Define an ordered route and its permitted alternatives before an incident. Octoryn can use health signals to keep decisions inside the boundaries your team has approved.

Explicit primary and fallback orderExpand details
This is part of Fallback is part of the policy. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Health-aware routing decisionsExpand details
This is part of Fallback is part of the policy. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Controlled failure behaviourExpand details
This is part of Fallback is part of the policy. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Balance quality, cost and latency

Different requests deserve different optimisation targets. Route interactive work for responsiveness, complex work for quality, or constrain a workload to an agreed budget posture.

Latency-oriented routesExpand details
This is part of Balance quality, cost and latency. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Quality-oriented routesExpand details
This is part of Balance quality, cost and latency. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Cost-aware policy constraintsExpand details
This is part of Balance quality, cost and latency. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

Keep data boundaries visible

Residency and private-routing requirements belong in the routing layer, not scattered through every product. Octopus teams can establish regional or private paths for the workloads that require them.

Regional routing boundariesExpand details
This is part of Keep data boundaries visible. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
Private and BYOK path supportExpand details
This is part of Keep data boundaries visible. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls
One governed policy surfaceExpand details
This is part of Keep data boundaries visible. Octoryn keeps its configuration, outcome and routing context together so teams can validate and review the capability independently.
Explore related controls

OCTORYN ROUTER

Design a route for your workload.

Start with a stable alias, define its optimisation target and fallback boundary, then connect it through the API your application already understands.

Read the routing guide