Platform

Feature Flags

Boolean, percentage, or attribute-targeted toggles. Runtime-switchable.

▸ How it works

Flags live in `feature_flags` with a kind (`boolean`, `percentage`, `targeting`), value, per-environment overrides, and audit log. Resolved values are held in an in-memory ETS cache invalidated on update, so the dashboard reflects flips in <5 ms. Targeting rules match against arbitrary user attributes — `userId`, `plan`, `country`, anything.

▸ What this lets you do

✓ Ship dark launches, gradual rollouts, kill switches
✓ Flag changes apply in <5 ms across the cluster
✓ Per-environment overrides for safe staging→prod testing
✓ Every flip is audited (who, when, before/after)

▸ Get it running

1 Open `Flags` → `+ New flag`
2 Pick a kind: `boolean`, `percentage`, `targeting`
3 Flip values from the dashboard — changes propagate via PubSub

▸ Code examples

Open `Flags` → click `+ New flag`, then fill the form:

  Key           checkout-v2
  Kind          Percentage
  Value         25            # rollout %
  Environment   prod

Save — the flag is live immediately. Per-environment
overrides (`staging`, `prod`) are added from the same
drawer; every flip is recorded in the audit log with
who / when / before-after.

Where to find it

/app/p/:org/:project/flags

Open in app →