Gradual rollouts

Ship to 5%.
Promote when it's healthy.
Roll back when it's not.

Define the steps and the guardrails once. AyBee advances the rollout on a schedule, watches your metrics at each stage, and reverses course automatically the moment something breaches its limit.

Get early access See traffic routing →

The rollout, step by step

A policy, not a pager rotation.

1
Start at the initial percentage
Open the feature to a small, deterministic slice — 5% by default. Bucketing is stable, so those users stay in until you promote.
2
Advance on a schedule
Walk the defined steps — 10 → 25 → 50 → 100 — one step per interval. No one has to remember to bump the number.
3
Check guardrails at every stage
Error rate vs control, p99 latency, and custom metric rules are evaluated before each promotion — within a cooldown window so noise doesn't trip it.
4
React automatically
On a breach, the policy rolls back, pauses, or reduces — your choice. Every transition is written to an append-only audit trail.

Guardrails

Promotion is earned.

A rollout only advances if the new variant stays inside the limits you set. Miss one and the policy's on-unhealthy action fires — rollback, pause, or reduce.

# rollout policy
initial_pct: 5
steps: [10, 25, 50, 100]
step_interval: 1 hour

error_rate_limit: 0.05 # 5% max vs control
latency_p99_limit:250 # ms
on_unhealthy: rollback
cooldown: 10 minutes

Why deterministic matters

Users don't flip
between variants.

0
network calls in the hot path
1
variant per visitor, stable
100%
of transitions audited

Automate the boring, risky part.

AyBee is in development. Get early access and we'll reach out personally.

Get early access