Traffic Splitting

Canary Deployments.
Without the Risk.

Route a percentage of traffic to different upstream targets for canary releases, blue-green deployments, and A/B testing — with sticky sessions and consistent hashing. No infrastructure changes required.

90/10 Canary Split

Incoming Requests

90%

stable → api.example.com/v1

10%

canary → api.example.com/v2

Consistent hashing — same user always hits the same variant

Four Ways to Use It

Canary Deployment

Send 5% of traffic to a new version. Monitor error rates and latency. Gradually increase to 100% when confident.

  • 5% canary → 95% stable
  • Auto-rollback on error spike
  • Zero downtime deployment
Blue-Green Release

Instantly switch 100% of traffic between two environments. Instant rollback by flipping the split back.

  • Instant traffic switch
  • Zero-downtime cutover
  • Instant rollback in seconds
A/B Testing

Split traffic 50/50 between two API variants. Compare response times, error rates, and business metrics.

  • 50/50 or any split
  • Sticky sessions for consistency
  • Measure impact per variant
Gradual Rollout

Start at 1%, increase to 10%, 50%, 100% over days. Each stage is a config change — no redeployment.

  • Incremental traffic shift
  • Per-route configuration
  • No infrastructure changes

How It Works

Consistent Hashing

Variant assignment is instant and deterministic — every user always lands on the same variant, consistently and predictably.

Sticky Sessions

Each user sees the same experience for 24 hours — across every node in your infrastructure, without exception.

Up to 10 Variants

Configure up to 10 variants per route. Weights are integers that must sum to 100.

Per-Variant Headers

Inject custom headers per variant (e.g. X-Canary: true) to identify traffic in your backend logs.

Ship Faster. Break Less.

Traffic Splitting is available on paid plans. Configure per-route in your dashboard — no infrastructure changes required.