The dimensions
Standing dimensions bill for what exists, such as a seat or an application, at a monthly rate. Counted dimensions bill for what happened, meaning events ingested. Guardrail dimensions are metered but carry generous included volumes; they exist to keep pathological automation visible, not to price ordinary use.
Alfiz is never in your request path
Everycan() runs in-process against your own database. Alfiz Cloud is not a dependency of your application: it cannot add latency to a check, cannot throttle one, and cannot fail in a way that stops one. That holds in every topology, including full federation, because the relay carries administrative traffic only, and the audit stream is opt-in and never sits between a request and its answer.
Pricing follows from it. Alfiz Cloud bills for the work it performs, being the dimensions above, and check volume is not a billing dimension and will not become one.
Permission metrics are a different feature with a confusingly similar name. Metering counts work Alfiz Cloud performed; metrics count checks your application performed. Metrics are stored by the application that produced them, in its own database. The hosted dashboard can read them for your own administrators, the same relayed read as every other admin surface, but Alfiz Cloud stores no copy and never bills on them.
Reading your meters
Every meter is readable over the API, exactly as the Dashboard renders it, with the same numbers and the same server function:Hard caps
Every dimension carries a hard cap, settable per dimension:Prices
The numbers live with the tiers they belong to:Linked pricing
Admin seats and opt-in audit retention. The linked application itself is free.
Federation pricing
The federation base, member applications, provisioned connectors, and carried-over seats.