Metered usage
Metered licensing uses usage signals and caps (soft or hard) instead of — or in addition to — pure seat/feature grants. Caps and meter codes are technical identifiers on Policy / License Plan / license entitlements; Runtime and Management enforce them according to shipped product modules.
What this page covers
| Topic | Guidance |
|---|---|
| Intent | Pay-for-usage or soft/hard usage caps alongside other modes |
| Where rules live | Management packaging (Entitlements FeatureLimits / meter codes) |
| Where enforcement runs | Runtime validate paths and Management reconciliation — not invented client-side counters as source of truth |
| Air-gapped | Usage / receipt export packages may reconcile offline sites (Air-gapped) |
Clients must not treat local tallies as authoritative without a signed or Management-confirmed snapshot.
What this page does not invent
Exact meter event schemas, ingest routes, and billing-settlement APIs are defined in OpenAPI / product specs as modules ship. Use API Reference for current contracts. Do not assume a meter code equals a custom data slot — custom data is a fixed vendor field set (ADR-0026), not a usage counter.
Related modes
Metered often combines with node-locked, floating, or offline leases (Licensing Models). Policy clamps still apply.
Related
Next steps
- Getting Started
- Packaging overview: Entitlements · Licensing Models