Pricing

Start with a test. 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.

Start a test Contact sales

Usage model

Plans include virtual user-hours for load generation and product caps for concurrent runs, retention, and collaboration features.

$0 / month

100 VU-hours included. No overage — hard usage cap.

Up to 1 concurrent runs
Up to 1 concurrent runners
7 days result retention
Tests up to 20 minutes
100 VU-hours/month (×12 for annual, granted up front)

Aggregation latency: < 10s
Executors: All 21 Taurus executors (JMeter, k6, Locust, Gatling, Selenium, …)
Regions: AWS, GCP + Azure regions
Browsers: Chrome and Firefox

Start a test

$29 / month

$290 / yr billed annually

1,000 VU-hours included. No overage — hard usage cap.

Up to 2 concurrent runs
Up to 10 concurrent runners
30 days result retention
Tests up to 6 hours
Scheduled runs
1,000 VU-hours/month (×12 for annual, granted up front)

Aggregation latency: < 10s
Executors: All 21 Taurus executors (JMeter, k6, Locust, Gatling, Selenium, …)
Regions: AWS, GCP + Azure regions
Browsers: Chrome and Firefox

Choose plan

$199 / month

$1,990 / yr billed annually

10,000 VU-hours included. No overage — hard usage cap.

Up to 10 concurrent runs
Up to 50 concurrent runners
90 days result retention
Tests up to 1 day
BYOC private datacenters
Scheduled runs
10,000 VU-hours/month (×12 for annual, granted up front)

Aggregation latency: < 10s
Executors: All 21 Taurus executors (JMeter, k6, Locust, Gatling, Selenium, …)
Regions: AWS, GCP + Azure regions
Browsers: Chrome and Firefox

Choose plan

Custom pricing

Included usage only — no overage

Unlimited concurrent runs
Unlimited concurrent runners
365 days result retention
Tests up to 7 days
BYOC private datacenters
SSO included
Static IPs

Aggregation latency: < 10s
Executors: All 21 Taurus executors (JMeter, k6, Locust, Gatling, Selenium, …)
Regions: AWS, GCP + Azure regions
Browsers: Chrome and Firefox

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

Monthly plans start with the period's included VU-hours allowance. Annual plans receive the full year (12× the monthly allowance) up front as a single pool — it is not reset monthly.

Aggregation latency: < 10s

Product caps are visible

Concurrent runs, retention, and engine allowances are driven by the shared catalog.

All 21 Taurus executors (JMeter, k6, Locust, Gatling, Selenium, …) · AWS, GCP + Azure regions

Enterprise stays flexible

High-scale or compliance-heavy teams can work through sales for custom usage and support terms.

Browsers: Chrome and Firefox

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 caps such as concurrent runs and retention. The console remains the source of truth for checkout and account-specific usage.

How does the annual plan quota work?

When you subscribe to an annual plan, the full year's VU-hour allowance (12× the monthly figure) is granted immediately as a single pool for the entire 365-day term. There is no monthly reset — you can use the quota at whatever pace suits your testing schedule. If you downgrade before the year is up, any refund is prorated against the original annual plan price, capped at the unused portion of the term.