No database on the hot path
Every flag lives in an in-memory, (project, environment)-partitioned index. Eval is a hash and a table lookup, no round-trip, ever.
Wagle is a multi-project, multi-environment feature-flag system where every flag lives in memory and evaluates locally, with no database on the hot path, built for very-high-traffic apps.
xxhash64 · bucket % 10000 · in-memoryWhy & how it works, including where it's less strong →Every flag lives in an in-memory, (project, environment)-partitioned index. Eval is a hash and a table lookup, no round-trip, ever.
Flags are keyed by (project, environment) day one. Same flag set across dev, staging, prod, with a different rollout in each, promoted explicitly.
xxHash64 over {project}:{env}:{flag}:{entity}, mod 10000. The same entity always lands in the same bucket, so a 5% rollout is a stable 5%.
Compose rules over segments and attributes with an ordered fall-through to a default variation. Typed values, not just booleans.
Every write bumps a per-project version and appends to history, attributed to an actor. Read a whole version torn-free, never a mixed snapshot.
SDKs pull one initial snapshot and evaluate locally. Server-only flags stay server-side. Built for very-high-traffic apps.
Untouched screenshots of the console working a real project: one bool flag, one string flag with a rolling split, one JSON config with a rule and a rollout, and the history those edits leave behind.
Evaluations run locally and are always free: the only call that reaches wagle is an SDK sync (the config pull). So the bill scales with one number: how many times your SDKs sync.
price ∝ syncs · evals free5k syncs included, then pay as you grow.
More volume, cheaper overage.
For high-traffic apps metering millions of syncs.