Skip to content

FAQ

Short answers to the most common questions. If yours is not here, check the rest of the docs or contact us through the Support page.

Any HTTP-based system you are authorized to load: web apps, public APIs, internal services, GraphQL endpoints, and most workflows you can express in Taurus, JMeter, or k6.

Taurus, JMeter, and k6. The engine is inferred from the file you mark as the entrypoint. See Test engines.

Yes. Install the MaxoPerf agent inside your network and pick that location when you create a test. See Connect a private datacenter.

Can I run multiple tests at the same time?

Section titled “Can I run multiple tests at the same time?”

Yes, subject to your plan’s concurrent-run limit. See Billing and plans.

Files live with the test, in the project that owns it. Upload them once and re-use them across runs. See Upload test files.

How do I keep credentials out of my test files?

Section titled “How do I keep credentials out of my test files?”

Use project secrets. They are encrypted, scoped to one project, and injected as environment variables at run time. See Manage test secrets.

Yes. Each test has a Schedules tab where you can define cron expressions and timezones. See Schedule recurring tests.

Yes. Use the Platform API from any CI system. See Run tests from CI.

Why is the average latency green but the p95 red?

Section titled “Why is the average latency green but the p95 red?”

Averages hide tail latency. Always read p95 and p99 per request label instead of whole-run averages. See Read run results and logs.

Can I save a dashboard that I can re-use across runs?

Section titled “Can I save a dashboard that I can re-use across runs?”

Yes. Dashboards live at the workspace level and can be pinned as the default view for a test. See Build reporting dashboards.

Where can I see the actual error response bodies?

Section titled “Where can I see the actual error response bodies?”

Open the Errors tab on the run page, select an error and open its First, Last or Recent sample. See Inspect error response bodies.

The Pricing page lists the current tiers. The account Billing screen shows your active plan. See Billing and plans.

From the account Billing screen, click Change plan. See Upgrade or cancel your plan.

You get a banner and an email. You have a grace period to update payment before the plan downgrades to the free tier. See Billing payment issues.

Do you store the request bodies of my test traffic?

Section titled “Do you store the request bodies of my test traffic?”

MaxoPerf keeps redacted samples of failing requests for diagnosis: the first, the last, and up to 5 of the most recent, for each combination of runner, scenario, label, and error, up to 64 KiB per body. It does not keep a body for every request, only for failures, and only for engines that expose bodies (JMeter, k6, Gatling, Locust, Apiritif, Playwright, and Selenium on Chrome). Turn capture off per test if you don’t want it. See Inspect error response bodies.

Project secrets are encrypted at rest. MaxoPerf decrypts them only when a run starts and injects them into the runner. They never appear in result pages or logs. See Manage test secrets.

status.maxoperf.com. It is always reachable, and you don’t need an account. See Status page.

Use the search box at the top of these docs, browse the Glossary, or contact us through the Support page.