Plans, Usage and Billing
A plan belongs to an organization, not to a site. One allowance covers every site inside it, which is why the usage screen totals them together.
:::note Nothing is charged yet Paid plans are not switched on in this deployment. Every organization is on the Free plan, the checkout button is absent rather than broken, and the API says so explicitly rather than letting a customer discover it at a payment form. The plans below are what the tiers will be. :::
What is counted
Three counters, reset monthly:
- Pageviews — one per page a visitor loads.
- Recordings — one per recorded session, plus the bytes those sessions store.
- Errors — one per occurrence, not per unique fault. An error seen five thousand times is one row in the dashboard and five thousand against the allowance, because it cost that.
Nothing is counted for a request that was not stored. A payload refused for consent, for an opt-out signal or for an excluded URL never reaches a counter — you cannot be billed for data we declined to keep, and a counter that ticked on refusals would make a site look busy for switching privacy protections on.
What happens as you approach a limit
| At | What happens |
|---|---|
| 80% | A notice on the usage screen, and a message to the organization's owners. Nothing changes. |
| 100% | A second notice. Still nothing changes. |
| 120% | Collection is refused for the metered kinds only. |
The gap between 100% and 120% is deliberate: a month that runs 5% over is not a reason to stop collecting somebody's data, and a hard stop the moment a round number is crossed is how a shop loses the week of analytics it was about to look at.
Errors and leads keep flowing past every limit, always. They are the two things that cost money to miss — an error you never saw is a checkout that is broken right now, and a lead you never received is a customer. Analytics and recordings are the ones that stop, because they are the ones you can catch up on.
Reading the usage screen
It shows the current month against the allowance, per counter, for the whole organization. The month is calendar-based and resets at the start of the next one; it is not a rolling window, so a spike does not follow you for thirty days.
Invoices
Every charge produces an invoice row with its amount, currency, status and period, readable from the billing screen and included in your account export. There is no separate archive to request.
Changing or cancelling
A subscription lives in one of four states — trialing, active, past due, cancelled — and a cancellation takes effect at the end of the period you have paid for, not immediately. Data collected during a paid period stays under the retention rules that applied when it was collected.
The provider's own portal handles payment methods and receipts. It is available once there is a customer record to open it against, which means after the first checkout — before that there is nothing to show and the button says so instead of failing.