Your allowance, the meter, and your spend cap

Your plan includes an allowance. Most accounts never see a meter. If yours does, this is how it works.

The allowance

Sized so that ordinary use of your plan stays inside it. It is not a trap set just below normal usage, and if your ordinary month is regularly over it, tell us, because that means the allowance is wrong for your plan rather than that you are using the product incorrectly.

Past the allowance

Metered, at rates published on the pricing page. Nothing is metered at a rate you have to ask for.

The cap

You set a spend cap. When a request would take you past it, the request is refused before it happens.

That word "before" is the whole feature. A cap that reports a breach afterwards is a report. You can only be protected from an unexpected bill by something that declines to create it, which is occasionally inconvenient and is the only version of this that is worth having.

What proves it worked

Two checks.

During the month, look at the usage view. At the end of the month, look at the invoice line. Same number. They are computed from one account rather than calculated twice, so they cannot drift apart.

Set your cap low for a moment and attempt something that would exceed it. It is refused, and the message names the cap. Then set it back.

Seeing it before you are billed for it

The usage view is live during the month, not a statement produced at the end. If the only way to discover an overage were the invoice, the meter would be a surprise rather than a control, and that is exactly the incumbent behaviour this pricing is built against.

Raising the cap

You raise it. It is your cap, it is in the tenant admin, and it takes effect immediately. Nobody has to approve it and there is no conversation attached to it.