Billing, seats and usage
Documentation
Two pages that are often assumed to be one. Billing is about what you pay. Usage is about what you have used, and only one of them is hosted-only.
Billing
Applies to: Hosted only
A self-hosted deployment has no billing page at all — the tile is not shown, because there is no platform behind your deployment to invoice you. Your costs are your own infrastructure's.
The page shows your current plan, how many seats are in use against your limit, and what the seat charges come to.
Changes go through the payment provider's own portal, not through this page. That is deliberate: card details, tax identifiers and invoices belong where they are already handled properly, and there is exactly one link out to it. Your billing history lives there too.
Seats are counted from your team page. Inviting someone is what consumes a seat — see Adding team members and setting permissions. At your limit an invite is stopped with a route to raising it, rather than failing in a way that looks like a bug.
Usage
The usage page exists in both modes, which is worth stating because it looks like a hosted-only page and is not.
| Metric | Hosted | Self-hosted |
|---|---|---|
| Inspections | Counted, and capped on a metered plan | Not shown — nothing is metering you |
| Text messages | Counted; capped on a metered plan | Counted |
| Counted; capped on a metered plan | Counted |
Messages sent through your own provider credentials are counted separately from ones sent on platform infrastructure. That distinction is the point: what you send on your own account is your bill with that provider, not a number anyone here should be capping.
On a metered plan, a metric approaching its cap raises a banner on the pages where the work happens rather than waiting for you to visit this one. What happens when a cap is actually reached is in Creating an inspection.
Usage without caps is still useful: it is the cheapest way to see that a month's text volume tripled.
← Connected apps · Next: Security