Feature Flags

The Problem

Feature flags should be simple: is this feature on or off for this user? But in practice, the answer depends on billing tiers, tenant configuration, rollout percentages, and more. Traditional flag tools don’t know about any of that — so you write glue code.

How Flux Handles It

Flux feature flags are entitlement-aware by default:

• Boolean, multivariate, and percentage rollouts
• Tenant-scoped overrides: Enable features per organization
• Entitlement-aware: Flags automatically respect billing tier limits
• Zero-latency evaluation: Flags are evaluated at the edge, not via API call
• Audit trail: Every flag change is logged with who, when, and why

What Makes It Different

// Flag evaluation in Flux includes billing context automatically
let user = flux.auth().verify_session(&token)?;

// This checks: is the flag enabled? Is the user's plan allowed?
// Is there a tenant override? All in one call.
if flux.flags().is_enabled("advanced-analytics", &user) {
    // User's plan includes this feature AND it's rolled out to them
}

No glue code. No “check the flag, then check the plan, then check the tenant override.” One call, complete context.