CEDX Entitlements · Platform
Entitlements evaluates 320 flags 104.4 million times a day in the demo estate, and remembers what most flag tools forget: which of the 68 temporary flags became permanent, which overrides never expire, and which flag is 868 days old and still serving traffic.
The retirement queue is the feature: 24 flags score high enough on debt to be candidates, led by one at 94 that has been stuck at 100% with no kill switch and no owner.
Runs on demo data. Northline Platform in the captures is the software's demo workspace, not a customer.
What it is
The Flags table does not stop at on and off: kind, state, environment, exposure, debt, blast and age on every key. Sorting by debt puts a 94-scoring legacy flag at the top — 868 days old, still on in production — which is a retirement decision presented as a row, not a post-mortem.
48 plans with seats, feature counts and attach rate: 1,366 feature slots across plans, 84% of features wired to flags. The MRR column is labelled demo SKUs on the screen itself — $391,320 packaged — so the wiring between a plan and its flags is the thing being shown, not a revenue claim.
96 force-rules, each typed segment, account, user or device, each with an expiry or the word never in red. The reasons are the honest part: month-end freeze, sales demo, contract exception, incident mitigation, QA holdout. Twenty set to never are a review queue, by design.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/entitlements.
01 — Overview
Estate health reads 40% hygiene, and the alerts say why: a temporary dual-write flag never retired at 413 days; a legacy payments flag stuck at 100% with no kill switch; six permanent overrides piled on one partner integration at 703 days old.
02 — Flags
Three hundred twenty keys with kind, state, environment, exposure, debt, blast and age. The temp-permanent card counts 68 flags that were never cleaned up — the failure mode every flag system has, made into a number you can work down.
03 — Plans
Forty-eight plans with code, tier, status, seats, feature count and attach rate per row — the top plan attaches 38 of 42 features to flags. Sunset plans stay visible, because retiring a plan is a lifecycle, not a deletion.
04 — Overrides
Ninety-six overrides where the REASON column does the governance: partner SLA, contract exception, beta cohort. The ones expiring never are red, counted at 20, and one click from a review.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the flag registry: debt and blast on every key, and the retirement queue of 24 that turns spring cleaning into a sorted list.
retire queue · 24Owns the 45 live rollouts and the staged 72 behind them — and the kill switches, because a rollout without one is an alert on this console, not a risk accepted silently.
live rollouts · 45
Owns the overrides: 96 open, 20 that never expire, and the monthly review that asks whether the month-end freeze reason is still true.
never-expire · 20The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
A feature ships behind a flag — one of the 189 active, typed boolean, percentage, multivariate or config, with a kill switch from day one.
Staged rollouts move exposure up — 45 live now — with the gate stable for days before the next stage, as the checkout alert describes.
Plans attach the flag to tiers: 84% of features are wired this way, so a plan change is a flag change, not a deploy.
Debt and age accumulate on the key until the retirement queue says the obvious: 24 flags are past the line, and the queue is the to-do list.
One record
Entitlements is the switchboard between identity and product: the person is known elsewhere, but what their plan turns on is decided here.
Sign-on policy decides who gets in; the plans and flags here decide what they can touch once inside.
CEDX AdminSeat tiers on the Admin console map to plans here — the pack a workspace pays for is the flags it evaluates.
CEDX DeployRollouts with kill switches and staged exposure are the release discipline Deploy runs; the flags are the mechanism.
CEDX AuditFlag flips, override grants and plan changes are admin-class events — exactly what Audit retains.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your flags, your plans
Entitlements with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/entitlements. It runs on demo data, which the page says next to the figures rather than in a footnote.
A score per flag that weighs age, stuck exposure, missing kill switch and ownership. Twenty-four flags score 55 or above and form the retirement queue — the top one has been on at 100% for 868 days with no owner, which is precisely the state debt scoring exists to surface.
Debt asks how overdue a flag is for retirement; blast asks how much it costs if it flips wrongly. Both are columns on the registry — a fraud holdout config scores 72 on debt and 95 on blast, which is a different conversation than a stale experiment.
Every override has a type, a value, an environment, an expiry and a reason on its row. The 20 set to never expire are red and counted, so the exception register is the same table engineers already read.
That is the attach rate's job: 84% of features across the 48 demo plans are wired to flags, so moving a feature between tiers is a plan edit. The remaining 16% is visible as unwired, not assumed away.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then ask how old the oldest temporary flag in your own codebase is.