Usage & billing
Usage & billing in the Workspace area (Admin) — route /workspace/usage-billing.
Usage & billing lives in the Workspace area of the dashboard, under Admin.
At a glance#
| Dashboard route | /workspace/usage-billing |
| Area | Workspace (workspace) |
| Group | Admin |
| Platforms | Available for every app platform. |
What it does#
Usage & billing shows your current plan and status, how much of each metered resource you have used against its limit, and your invoice history with downloadable copies.
The metered resources are sessions, events, replays and team seats. A metric with no limit is unlimited on your plan rather than unmeasured — the two are displayed differently.
When to use it#
Before you change your sampling configuration, and before a launch. Usage is driven by instrumentation decisions made in code: raising a replay sample rate or adding an event to a high-frequency path can multiply consumption without anyone intending it.
Checking here after a configuration change is much cheaper than discovering it at the end of the billing period.
Workflow#
Read consumption as a rate, not a total
Half your session allowance used on day five of the month is not "half used", it is a 300% overrun in progress. Compare against how far through the period you are.
Attribute a spike before changing plan
A jump in events usually traces to one new event on a frequently-executed path. Find it first — the fix is often a one-line change rather than an upgrade.
Check seats against your member list
Seats are consumed by workspace members. Offboarding people you have already stopped working with is the easiest reduction available.
Permissions and prerequisites#
Billing is OWNER-only — ADMIN deliberately does not include it. This page is read-only:
plan changes and payment details are handled outside it.
Limits and edge cases#
Usage figures may lag slightly. They aggregate ingested data, so the very recent tail is not instantaneous. Do not use this page to measure the effect of a change you made five minutes ago.
Replays are metered separately from sessions. A session and its replay are two units of consumption, which is why replay sampling is the most effective lever available.
Invoice amounts are in the currency's minor units internally and formatted for display; if you are reconciling against an export, check which form you have.
Seats count members, not activity. An inactive member still occupies a seat.
Troubleshooting#
Usage far higher than expected. In order of likelihood: replay sampling raised, a new event on a hot path, or a debug build reporting into production. The third is more common than it sounds — check the environment.
A metric shows no limit. Unlimited on your plan. It is still worth watching as a rate.
Where the data comes from#
Served by
Billing
entitlements— internal module, no public endpoints