$1,000 trialSDKsChangelog
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.08.02-design-partnersShipped

Design Partner applications are open

Octoryn is accepting a deliberately small first cohort of companies ready to validate governed routing against a real workload.

Release scope
Early AccessOnboardingCredits

What changed

  • Public bilingual application flow with durable server-side submission storage
  • Up to US$1,000 in non-cash promotional Router credits for each of the first three approved companies
  • Ninety-day credit validity from activation and one award per company
  • Direct technical onboarding for teams able to begin a real workload within 30 days
  • Explicit acceptable-use, eligibility and promotional-credit terms
Verify the releaseApply for early accessReview the Router
022026.08.02-routerShipped

The hardened Router release is serving production traffic

The current production Router now exposes an independently verifiable build identity and carries the completed streaming, failover and provider-qualification hardening release.

Release scope
RouterReliabilityProviders

What changed

  • Typed public status contract with deployed build identity and API contract digest
  • Streaming upstream error bodies are read and classified before provider failover
  • Upstream finish reasons and incomplete terminal states are preserved across streaming responses
  • Fifty retained qualification cases across OpenAI, Anthropic, Gemini and Grok
  • Candidate-bound, freshness-checked shadow evidence and rollback gates
  • Contract-transition and retired-surface guards across the SDK release paths
Verify the releaseVerify production statusRead the API reference
032026.08.02-sdkShipped

SDK v3 and native patch releases are available

Registry versions, public mirrors and release guards now align with the production Router contract across the supported client platform.

Release scope
SDKRegistriesSupply Chain

What changed

  • TypeScript @octoryn/sdk 3.0.0 and Python octoryn-llm 3.0.1
  • .NET 0.1.2, Swift 0.2.1 and React 0.2.1 patch releases
  • PyPI and NuGet trusted publishing with registry-native provenance
  • Live Router contract validation before SDK and mirror publication
  • Relative-route and retired-product guards extended across public language mirrors
  • UI clients retain structured object streams, recovery, custom transports, validation and transforms
Verify the releaseChoose an SDKOpen the Octoryn GitHub organisation
042026.08.01-capacityShipped

Prepaid capacity has a governed lifecycle

Promotional and contract-funded Router capacity can now be allocated and accounted for without reintroducing consumer billing into the Router.

Release scope
CapacityBudgetsAudit

What changed

  • Tenant-scoped capacity allocation, reservation, settlement and expiry
  • Idempotent funding operations and content-free audit evidence
  • Budget enforcement remains ahead of provider access
  • Promotional credits and contract prepayment share one governed capacity authority
  • No cash balance, withdrawal, rebate or consumer-wallet semantics
Verify the releaseReview pricingExplore governance
052026.07.31-sdkShipped

The SDK platform is publicly available

Official language SDKs, UI framework packages and ecosystem adapters now have public, native distribution paths with anonymous installation verification.

Release scope
SDKDeveloper ExperienceRegistries

What changed

  • TypeScript and Python production clients through npm and PyPI
  • Go, .NET, Java, PHP, Ruby, Swift and Kotlin/Android public distribution
  • React, Vue, Svelte, Angular and UI Core framework packages
  • UI SDK 0.2.0 adds streamed structured objects, resume, regenerate/edit, custom transports, schema validation and stream smoothing
  • Vercel AI SDK, LangChain, LlamaIndex, MCP and OpenTelemetry adapters
  • Text, streaming, tool calling and JSON Schema structured outputs
  • Public language mirrors without exposing the private monorepo
Verify the releaseExplore the SDK platformRead the API documentation
062026.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
072026.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
082026.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
092026.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
102026.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