Percentage Rollout API
EdgeAssign is a percentage rollout API built for gradual releases with stable bucket mechanics.
Change 5% to 50% without reassigning users. The bucket stays stable; only the threshold moves.
What gradual rollouts need to get right
- Stable cohorts so users do not bounce between states.
- Consistent behavior across backend, frontend, mobile, and edge.
- Fast adjustments without a rewrite or backfill.
How EdgeAssign handles gradual rollout mechanics
- Derives a stable bucket from subject + flag.
- Applies a percentage threshold to that bucket.
- Returns the same decision for the same inputs.
Concrete example
// Deterministic bucketing
bucket = hash(seed + flag + subject) % 100
enabled = bucket < rollout_percentStable buckets make gradual rollouts predictable.
Why this is different from typical platforms
- Percent changes do not reshuffle buckets.
- Derived decisions keep rollout mechanics simple.
- Predictable outputs reduce QA churn.
For the vendor comparison, see EdgeAssign vs. the usual options.
Who it is for
- Teams rolling out features by percentage safely.
- Services that require consistent behavior across channels.
- Applications that need a low-ops rollout API.
FAQ
Can I move from 5% to 50% without reassigning users?
Yes. Buckets are stable, so only the threshold changes.
What if I cache responses?
Cached responses follow the TTL. Purge cache for urgent rollbacks.
Do you store assignment history?
No. Decisions are derived on demand.