Context-aware rules
Match principal attributes, environment, region, capability, and request metadata.
Runtime plane
Route deterministically, then fail explicitly.
Preserve explicit upstream selection and bounded failure behavior today; health, geography, residency, cost, and failover routing are planned.
Product boundary
The gateway currently dispatches to an explicit eligible member and avoids replay after an ambiguous side effect. A full route evaluator is not yet implemented.
- Available now
- Behavior backed by the current local vertical slice and automated tests.
- Preview
- Useful implementation exists, but the complete operating journey is not proven.
- Planned
- Part of the open MCP-native roadmap, not current product behavior.
- Deployment
- Managed cloud and self-hosted targets share portable packages; live parity remains an acceptance test.
Capabilities
What routing controls
Status labels distinguish tested behavior from useful previews and the open roadmap.
Health-aware selection
Exclude unhealthy deployments using current schema probes and health samples.
Failure isolation
Bound requests, responses, redirects, cancellation, and timeouts; circuit breakers and concurrency bulkheads remain planned.
Safe retries
Do not replay an ambiguous post-dispatch side effect; a complete idempotency and failover ledger remains planned.
Operating flow
The target journey, with current maturity called out above.
Qualify
Filter upstreams by policy, identity, capability, environment, and health.
Select
Evaluate ordered deterministic rules against the remaining candidates.
Execute
Propagate cancellation and correlation while enforcing runtime limits.
Target control surface
Designed for platform and security teams.
These controls define the intended product boundary; the capability labels above are the current implementation record.
- Ordered routing rules
- Circuit breakers
- Concurrency bulkheads
- Cancellation propagation
- Retry classification
- Explicit unavailable errors
Evaluate locally or inspect either deployment target.
The managed cloud and Kubernetes paths are previews of one open codebase, with no intended capability gate or mandatory call-home path.