Trait-Based Feature Flags
EdgeAssign evaluates eligibility rules and rollouts in one call, using trait-based feature flags.
Gate features by plan tier, role, or cohort while keeping sensitive data out of your request payloads.
Use SafeTraits to keep raw PII out of requests while EdgeAssign handles deterministic evaluation.
Unified guide: SafeTraits boundary + cookbook recipes.
What trait-based flags solve
- Eligibility gates based on attributes instead of endpoints.
- Consistent rule evaluation across services.
- Rules plus percentage rollouts in one flow.
How EdgeAssign handles eligibility
- Send a subject plus a traits object.
- Rules are evaluated before rollout percent.
- Return a deterministic decision you can cache.
Concrete example
# PowerShell (safe JSON)
$body = @'
{"subject":"alice","traits":{"plan":"pro","beta":true}}
'@
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"
{
"eligible": true,
"enabled": true,
"bucket": 8,
"rollout_percent": 25
}Rules decide eligibility first, then rollout percent is applied to the stable bucket.
Why this is different from typical platforms
- Rules and rollout in one evaluation call.
- Deterministic results without assignment storage.
- SafeTraits guidance keeps raw PII out of payloads.
For the vendor comparison, see EdgeAssign vs. the usual options.
Who it is for
- Teams that want feature gates tied to plan tiers.
- Apps that combine eligibility rules and rollouts.
- Developers who need consistent trait evaluation.
FAQ
What rules are supported?
Rules support common ops like eq, in, and exists.
Should I send raw PII as traits?
No. Map sensitive values to SafeTraits (booleans or coarse labels) before sending.
Can I mix traits and percentage rollout?
Yes. Traits determine eligibility, then rollout percent is applied to the stable bucket.