Updated May 14, 2026
Billing and usage overview
Understand how Maxoperf connects plans, usage, and metered performance testing activity without hiding cost in ad hoc cloud bills.
Before you start
- An account with billing access for plan review.
Why billing belongs near the workflow
Performance tests consume capacity. When teams build ad hoc runner fleets, cost often appears later as a cloud bill that is hard to map back to a test.
Maxoperf keeps plan and usage concepts close to the account and run workflow so owners can reason about capacity before increasing test cadence.
What affects usage
The important variables are run duration, runner count, location plan, run frequency, and which product capabilities are active. Review these before turning a release-candidate test into a frequent scheduled check.
FAQ
Why is usage easier to manage in a platform?
Plans and usage are attached to test activity, so teams do not have to reverse-engineer cost from unrelated cloud infrastructure bills.