Apache Benchmark
Fast single-URL HTTP benchmarking tool
execution:
- executor: ab
concurrency: 50
hold-for: 30s
scenario:
requests:
- url: https://example.com/api Instant lightweight demo
Paste a URL and we will spin up a lightweight live test demo. Your email is all it takes — we create your free account on the spot.
21 test engines
JMeter, k6, Gatling, Locust, Selenium, and 16 more — all running under one managed control plane. No new tooling to learn.
Fast single-URL HTTP benchmarking tool
execution:
- executor: ab
concurrency: 50
hold-for: 30s
scenario:
requests:
- url: https://example.com/api Python HTTP client for API scenario tests
execution:
- executor: apiritif
concurrency: 10
iterations: 100
scenario: api-test
scenarios:
api-test:
requests:
- url: https://example.com/users
method: GET Run any test tool via Taurus subprocess
execution:
- executor: external
command: ./my-tool --duration 60s
env:
TARGET_URL: https://example.com
WORKERS: "8" Developer-first JVM load testing with Scala DSL
execution:
- executor: gatling
concurrency: 100
ramp-up: 30s
hold-for: 2m
scenario: checkout
scenarios:
checkout:
script: simulations/Checkout.scala Distributed Java/Jython load framework
execution:
- executor: grinder
concurrency: 50
iterations: 200
scenario: grinder-test
scenarios:
grinder-test:
script: scripts/test_script.py Industry-standard Java load testing engine
execution:
- executor: jmeter
concurrency: 200
ramp-up: 1m
hold-for: 5m
scenario: checkout-flow
scenarios:
checkout-flow:
requests:
- url: https://example.com/checkout
method: POST Java functional tests executed under load
execution:
- executor: junit
concurrency: 10
iterations: 50
scenario: junit-load
scenarios:
junit-load:
script: target/test-classes/
additional-classpath:
- lib/test-deps.jar Modern developer-first load testing in JavaScript
execution:
- executor: k6
concurrency: 50
hold-for: 2m
scenario: k6-load
scenarios:
k6-load:
script: scripts/load.js Python-based distributed load testing
execution:
- executor: locust
concurrency: 200
ramp-up: 1m
hold-for: 5m
scenario: locust-test
scenarios:
locust-test:
script: locustfile.py Async Python HTTP load framework
execution:
- executor: molotov
concurrency: 50
hold-for: 2m
scenario: molotov-test
scenarios:
molotov-test:
script: loadtest.py Node.js test framework for API load scenarios
execution:
- executor: mocha
concurrency: 5
iterations: 100
scenario: api-test
scenarios:
api-test:
script: test/api.spec.js Ultra-high concurrency HTTP benchmark in C
execution:
- executor: pbench
concurrency: 1000
hold-for: 30s
scenario:
requests:
- url: https://example.com/api
method: GET Keyword-driven test automation at scale
execution:
- executor: robot
concurrency: 5
iterations: 20
scenario: robot-test
scenarios:
robot-test:
script: tests/load_suite.robot Taurus-native parallel test execution
execution:
- executor: scalable
concurrency: 500
steps: 5
hold-for: 5m
scenario: scale-test
scenarios:
scale-test:
requests:
- url: https://example.com/api Browser UI automation under real load
execution:
- executor: selenium
concurrency: 5
hold-for: 10m
scenario: ui-flow
scenarios:
ui-flow:
browser: Chrome
requests:
- url: https://example.com/login HTTP regression and load testing CLI
execution:
- executor: siege
concurrency: 25
hold-for: 1m
scenario:
requests:
- url: https://example.com/
- url: https://example.com/about YAML-only test definition, no extra scripts
execution:
- executor: taurus
concurrency: 100
hold-for: 3m
scenario: yaml-only
scenarios:
yaml-only:
requests:
- url: https://example.com/api
assert:
- contains: '"ok"' Java testing framework with load scenarios
execution:
- executor: testng
concurrency: 10
iterations: 50
scenario: testng-load
scenarios:
testng-load:
script: target/test-classes/
testng-xml: testng.xml Erlang distributed load testing for massive scale
execution:
- executor: tsung
concurrency: 500
hold-for: 10m
scenario: tsung-test
scenarios:
tsung-test:
script: tsung-config.xml Go HTTP load testing with constant attack rates
execution:
- executor: vegeta
rate: 100
hold-for: 60s
scenario:
requests:
- url: https://example.com/api
method: GET Node.js browser automation and load testing
execution:
- executor: wdio
concurrency: 3
iterations: 10
scenario: browser-test
scenarios:
browser-test:
script: wdio.conf.js Global infrastructure
Managed runner capacity across AWS, GCP, and Azure in every major region — so latency numbers reflect real geography, not the closest data center to your CI server.
Use cases
Start with a use case that matches your team's workflow.
API teams
Turn endpoint collections and test engine scripts into repeatable API load tests with explicit capacity, data, and release-gate context.
See examplesWeb teams
Exercise critical web journeys with production-shaped traffic patterns while keeping launch decisions tied to latency, errors, and logs.
See examplesRelease engineering
Make performance checks part of delivery without turning every pipeline into custom infrastructure.
See examplesDebugging
Re-run known scenarios after a production incident and compare the signals that matter: latency, errors, logs, and capacity.
See examplesPrivate environments
Place runners near private systems when targets are not reachable from public cloud locations or require allowlisted egress.
See examplesReliability
Give service teams a shared path for scheduled checks, controlled load, and evidence-rich performance reviews.
See examplesTest data
Generate correlated synthetic test data with the full faker catalog, upload your own CSVs, preview rows live, then split across load generators or replicate to every runner.
Test data
Generate synthetic, correlated test data with the full faker catalog or upload CSVs, preview rows live, then split across load generators or replicate to every runner.
Explore test dataDistribution
Choose how data reaches your load generators at run time. Split gives each runner a disjoint slice. Replicate delivers the full dataset to every runner. The platform handles delivery automatically.
Learn how it worksFAQ
Yes — a short, real lightweight demo from AWS Virginia (~15 requests/second for 3 minutes) against the URL you enter. We create the test for you; you can adjust load and locations within plan limits (duration stays fixed), then click Start, and stop or rerun it as often as you like.
No separate signup step: entering your email creates your free MaxoPerf account straight away and opens the console with the demo test ready. You never choose a password on this page — we email you a link to set one and finish your profile whenever it suits you. The account is a normal free account with no restrictions in the meantime.
Yes. MaxoPerf supports managed cloud locations and private runner locations for teams with network, allowlist, or residency constraints.
Backend, platform, SRE, QA, and release teams that need repeatable performance evidence without owning runner infrastructure.
Loadrigo
MaxoPerf AI assistant
Sharing your email here creates your free MaxoPerf account. By continuing you agree to our Terms of Service and Privacy Notice.