Changelog
EN
Open developer docs

Product changelog

What changed, and why it matters.

A dated record of production capabilities across the Octoryn Router, Console, public platform and developer surface. Shipped means observable in production—not merely present in source.

012026.07.31Shipped

Compliance becomes an execution capability

The Compliance & Trust Engine now evaluates signed identity and environment trust, tenant policy, provider eligibility and sensitive-data signals at the Router boundary.

Release scope
RouterGovernanceLanding

What changed

  • Request-bound Trust Context assertions with replay protection
  • Versioned policy-as-code and explainable decision evidence
  • Reviewed Provider Trust profiles for 11 production integrations
  • Input and output inspection for regulated and secret data classes
  • Content-free tenant posture and route-simulation APIs
  • Sydney multi-AZ shadow rollout with a proven rollback path

SHADOWShadow mode records the decision that enforce mode would make. It does not deny customer traffic.

Verify the releaseExplore Compliance & TrustRead governance documentationCheck live status
022026.07.30Shipped

Service health gets an independent evidence surface

Status is no longer a decorative health badge. Octoryn now publishes component state, retained uptime windows and reviewed incident history from an independent public origin.

Release scope
ReliabilityStatusOperations

What changed

  • Router API, Console, Landing, identity and catalog components
  • Ninety-day daily status history with explicit no-data states
  • Incident lifecycle, timestamps and resolution updates
  • RSS feed for operational changes
  • Separate public status origin and health contract
Verify the releaseOpen service status
032026.07.30-catalogShipped

Catalog separates discovery from approval

Provider discovery inventory and workspace-approved routing inventory are now treated as different governance states instead of one misleading model count.

Release scope
ModelsProvidersConsole

What changed

  • 234 approved routable models across 11 production providers
  • Provider detail pages with approved model inventories
  • Model type, price, manufacturer and provider filtering
  • Search, pagination and provider-to-model navigation
  • Clear distinction between platform-managed credentials and BYOK
  • Official discovery counts do not automatically become production routes
Verify the releaseBrowse modelsReview providers
042026.07.29Shipped

The governed API surface is documented end to end

Developer documentation now covers the compatibility surface and the operational rules needed to use it safely in production.

Release scope
APIDocumentationSDK

What changed

  • OpenAI-compatible chat, responses and embeddings guidance
  • Anthropic-style messages compatibility
  • Tools, structured outputs and streaming lifecycle
  • Rerank and moderation operations
  • Provider preferences, fallback and routing policy
  • Errors, rate limits, workspaces, governance and route simulation
Verify the releaseStart with the docsOpen API reference
052026.07.28Shipped

Octoryn becomes an independent Router

The production boundary was separated from incubator product code so applications consume the Router through APIs without the Router importing product services.

Release scope
ArchitectureSecuritySydney

What changed

  • Independent Router, Console and Landing deployment surfaces
  • No product databases, consumer billing or incubator feature imports
  • OpenAI and OpenRouter-compatible versioned endpoints
  • Tenant, workspace, service-key and audit boundaries
  • Immutable production images and rollback-safe releases
  • Sydney deployment with provider portability
Verify the releaseSee the architectureReview enterprise controls

OCTORYN ROUTER

A release record should be verifiable.

Compliance enforcement remains in shadow mode: decisions and evidence are produced, while customer requests are not blocked.

View production status