Instant Revocation

A credential is only as safe as how fast you can turn it off. When access lives inside every server, killing it means finding and redeploying all of them — and hoping you didn’t miss one.

Revoke once, everywhere

Any disable, rotate, or revoke atomically bumps a global epoch counter. Servers poll the epoch with lightweight ETag-cached checks and flush their caches the moment it changes, so a revocation propagates across the whole fleet in roughly 30 seconds.

Short-lived by default

Because servers only ever hold short-lived access tokens — never long-lived refresh tokens or API keys — the blast radius of a leak is small to begin with. Revocation closes the window; short lifetimes keep it narrow.

What you get

• One-click disable, rotate, regenerate, or force-reissue from the dashboard
• Propagation to every entitled server without touching a deployment
• The next call from a revoked token gets a clean 401 — no lingering access