Track workspace token usage, daily and monthly allowances, top-up balances, and detailed consumption across features and instances.
What Usage shows
Usage tracks consumption for the active workspace.
The current implementation includes categories such as:
- Instance runtime
- Instance storage
- AI responses
- Site Testing
- Plugin site scans
- Plugin full uploads
- Canary Wizard
Usage balance
The balance area explains how much of the workspace allowance has been consumed and how much remains.
Depending on plan configuration, CanaryWP can track both daily and monthly allowances.
Daily allowance
Daily usage resets on its configured reset schedule.
Use it to understand short-term consumption.
Monthly allowance
Monthly usage represents the broader billing-period allowance.
It resets on its configured monthly schedule.
Top-up balance
Top-ups provide additional allowance beyond the included plan allocation.
The Usage page should clearly show the remaining top-up amount separately from included plan usage.
When included usage runs out
When a daily or monthly allowance is exhausted:
- Available top-up usage may cover eligible actions.
- Otherwise, eligible actions can be blocked until additional usage is available or the allowance resets.
The application should state which condition caused the block.
Usage categories
Instance runtime
Usage associated with running CanaryWP environments.
Long-running instances therefore contribute differently from short-lived environments.
Instance storage
Usage associated with persistent instance storage.
AI responses
Usage generated by supported CanaryWP assistant responses.
Site Testing
Usage generated by CanaryWP testing workflows.
Plugin site scans
Usage generated by supported plugin/source-site scanning workflows.
Plugin full uploads
Usage associated with supported full custom-plugin upload workflows.
Canary Wizard
Usage generated by supported Canary Wizard workflows.
Recent Usage
The usage ledger is the detailed history behind the summary.
A ledger entry can identify information such as:
- Usage type
- Amount
- Date
- Description
- Instance
- Source
- Creator/system source
- Ledger identifier
Positive and negative entries
Consumption reduces the available balance.
Top-ups or qualifying adjustments increase it.
Instance attribution
Where available, usage should identify the instance responsible for the charge.
This is particularly useful when investigating unexpectedly high runtime, storage, or testing use.
Investigating unexpected usage
- Select the relevant date period.
- Review the category breakdown.
- Identify the category with increased consumption.
- Open recent ledger entries.
- Filter or search for the affected instance.
- Review the related activity or workflow.
- Determine whether the usage was expected.
Usage versus Billing
Usage: What CanaryWP resources did we consume?
Billing: What plan, top-ups, credits, and monetary charges apply?