Metering, entitlements & edge SDK
Every customer gets what they paid for. Even offline.
Count what customers use, check it against their plan in one place, and warn them before they hit the wall. On edge devices a signed entitlement keeps the rules working when the network does not.
Why it matters
Limits that hold, even with no network
How it works
A device, from first boot to a plan it enforces
- 1AdminIssue a bootstrap tokenSingle use, hashed, valid 24 hours by default.
- 2DeviceRegisterIt waits as pending approval.
- 3AdminApproveThe device gets an RSA-2048 certificate (365 days) and its first entitlement.
- 4DeviceCheck limits offlinemay_add answers ok, at limit, over a soft limit or restricted.
- 5DeviceBuffer and flush usageRecorded locally with an idempotency key; sent in order, 100 at a time.
- 6Identity StudioSync and rotateA new entitlement when the plan changes or fewer than 7 days remain.
Capabilities
What the entitlement carries
| Capability | Details | Status |
|---|---|---|
| Signed entitlement | RS256 from a per-application authority. Plan, dimensions (limit, used, reset, enforce), features, permissions and a signed grace period. | Live |
| States | Active, then grace, then restricted, decided on the device. | Live |
| Refusal reasons | Malformed, forged, wrong application, not yet valid, expired, stale, revoked. | Live |
| Idempotent usage | Stored on the device in SQLite first; the server dedupes on the idempotency key. | Live |
| Hard and soft limits | Each limit blocks (402) or warns. | Live |
| Alerts | Stages at 80, 90 and 100 percent of a limit. | Live |
| Overage policy per limit | Allow, notify, block, charge or meter. | Early access |
| Customer dashboards | Usage, allocations and the edge fleet in each customer's console. | Live |
| Generic for any edge app | Nothing names a dimension or unit; a census test fails on a hard-coded key; a conformance kit checks your integration. | Live |
Configuration
Settings
| Option | Values | Default |
|---|---|---|
| Bootstrap tokens | count 1 to 20 · expiry 1 to 720 hours | 1 · 24 h |
| Limit per dimension | A number, or -1 for unlimited | per plan |
| hard_block | Block at the limit, or warn | block |
| grace_period_days | Signed into the entitlement | from the plan |
| rotate_before_days | When the device asks for a new certificate | 30 |
| edge_devices | Switch edge devices on for an app | off |
Under the hood
What protects it
From the code
Security notes
- Offline verification accepts RS256 only.
- The device pins the authority certificate it receives at sync.
- Device-requested certificate rotations are audited, and fail if the audit row cannot be written.
- Usage the server refused is kept as refused and never resent.
Works with
Part of one platform
Billing & plans The plan sets the limits.SDKs The edge package.Roles & permissions Device roles become permissions.
Which plans include it, and the limits that apply, are on the plans page.See plans →
Explore the platform
One platform, every piece of sign-in and access
Stop hard-coding limits
Move your first limit into Identity Studio and enrol a device.