Pricing
Start free. Scale when performance testing becomes a habit.
Every number below comes from the shared billing catalog. The console remains the source of truth for checkout,
account-specific usage, promotions, and invoices.
Usage model
Plans include virtual user-hours for load generation and product caps for monitoring, service virtualization,
retention, and collaboration features.
Plan
Free
Default self-serve tier for new accounts — limited concurrency and retention.
$0 / month
5,000 VU-hours included. Overage: $0.20 / 1k VU-hours.
- Up to 1 concurrent runs
- 7 days result retention
- Engines: taurus, jmeter, k6
- SSO not included
- 5,000 VU-hours included monthly
- $0.20 / 1k VU-hours after included usage
- 5 active synthetic monitors
Start free Plan
Starter
Small teams getting started with cloud load tests.
$29 / month
100,000 VU-hours included. Overage: $0.12 / 1k VU-hours.
- Up to 2 concurrent runs
- 14 days result retention
- Engines: taurus, jmeter, k6
- SSO not included
- 100,000 VU-hours included monthly
- $0.12 / 1k VU-hours after included usage
- 50 active synthetic monitors
Choose plan Popular growth path
Growth
Higher concurrency and longer retention.
$99 / month
500,000 VU-hours included. Overage: $0.10 / 1k VU-hours.
- Up to 10 concurrent runs
- 90 days result retention
- Engines: taurus, jmeter, k6
- SSO not included
- 500,000 VU-hours included monthly
- $0.10 / 1k VU-hours after included usage
- 500 active synthetic monitors
Choose plan Plan
Enterprise
Scale, SSO, and priority support.
Custom pricing
5,000,000 VU-hours included. Overage: Contracted usage pricing.
- Up to 50 concurrent runs
- 365 days result retention
- Engines: taurus, jmeter, k6
- SSO included
- 5,000,000 VU-hours included monthly
- Contracted usage pricing after included usage
- 5,000 active synthetic monitors
Contact sales Metering
Simple enough for self-serve, explicit enough for enterprise
Usage-based load testing can get confusing fast. Maxoperf keeps plan caps and metered usage visible in the billing and run workflows instead of hiding them in cloud bills.
Included usage first
Start with monthly included virtual user-hours before overage estimates apply.
Product caps are visible
Concurrent runs, retention, monitoring, and virtualization caps are driven by the shared catalog.
Enterprise stays flexible
High-scale or compliance-heavy teams can work through sales for custom usage and support terms.
FAQ
Pricing questions
Where do the plan limits come from?
This page reads the shared billing catalog used by the product, so plan names, included usage, retention, engines, and caps do not drift from the application.
Does the free plan launch real load anonymously?
No. Free accounts still authenticate in the console, attach scenarios, choose capacity, and confirm settings before any traffic is generated.
How should we estimate usage?
Plans include virtual user-hours for load tests plus product-specific monitoring and virtualization caps. The console remains the source of truth for checkout and account-specific usage.