User Bucketing API
EdgeAssign is a user bucketing API for stable assignment and consistent cohorts.
Send a subject ID, and it returns the same bucket every time so treatment groups remain consistent across services and clients.
What stable assignment should guarantee
- Same user ID, same bucket.
- Consistent cohorts across backend, frontend, and edge.
- Predictable treatment groups for experiments or rollouts.
How EdgeAssign keeps cohorts consistent
- Derives the bucket from stable inputs.
- Returns deterministic results you can cache.
- No assignment table to synchronize.
Concrete example
# PowerShell (safe JSON)
$body = @'
{"subject":"alice","traits":{"plan":"pro"}}
'@
curl.exe -X POST -H "X-API-Key: YOUR_API_KEY" -H "Content-Type: application/json" --data-binary $body "https://api.edge-assign.com/v1/eval/prod1/new_checkout"
{
"bucket": 8,
"enabled": true,
"rollout_percent": 25
}The same subject and inputs always produce the same bucket.
Why this is different from typical platforms
- Derived cohorts instead of stored assignment rows.
- Consistent bucketing across services and clients.
- Stable assignment without extra storage work.
For the vendor comparison, see EdgeAssign vs. the usual options.
Who it is for
- Teams who need consistent cohorts across environments.
- Developers rolling out by user ID with predictable assignment.
- Products that value deterministic, cacheable decisions.
FAQ
Does the same user always land in the same bucket?
Yes. EdgeAssign derives the bucket from stable inputs and returns the same result.
What if I change the rollout percent?
The bucket stays stable. Only the threshold changes.
Can I use hashed IDs?
Yes. Deterministic bucketing works on hashed identifiers.