Artillery 2.xEU only

Load testing for engineering teams

Loaderao runs your Artillery scenarios on a managed fleet in the EU. Go from 100 to 100,000 virtual users, find the breaking point, and shut it down after.

A managed fleet for every run

Pick a plan or pay per VU-hour. The fleet is the same.

Runs the load in three regions

One scenario runs across isolated generators in three EU regions, up to 100,000 virtual users.

Live percentiles and errors

Throughput, p95, p99 and errors update while the run is live, not after it.

Requests per secondThis run
184.2kPeakat 50,000 users

Threshold gates in CI

A pull request fails when p95 or the error rate crosses the thresholds in your YAML.

shop/checkout-flow #482 10m 06s Passed
Ramp 4,000 to 50,000 users run_482
  1. Fetch scenariogit fetch --depth 11s
  2. Validateartillery validate2s
  3. Generators12 × eu-north-18s
  4. Run50,000 users · 10m9m 54s
  5. Thresholdsp95 < 400 ms1s

EU data residency

Generators and results stay in EU regions. A data processing agreement is available.

From YAML to verdict in three steps

01

Your Artillery scenario

Use your existing Artillery YAML, plugins and custom JS.

checkout.ymlYAML
config:
  target: "https://staging.shop.ee"
  phases:
    - duration: 600
      arrivalRate: 200
      rampTo: 5000
scenarios:
  - flow:
      - get: "/cart"
02

Your load profile

Choose users, duration and ramp. The fleet is provisioned for you.

loaderao/run artillery checkout.yml
~/shop$artillery run checkout.yml
3 of 3 phases
warm-up2,000 VUs1m 00s
ramp50,000 VUs4m 00s
steady50,000 VUs5m 00s
Requests6.2M(10m)
Errors0.02%(1.2k)
Passedin 10m 06s
~/shop$
03

The run report

Percentiles, errors and pass or fail against your thresholds.

Run thresholds
4 of 4
  • p95 under 400 ms
  • 5xx under 0.1%
  • Requests above 6M
  • Run longer than 10 min

Artillery is the engine. Loaderao is the fleet.

Artillery is the open source load testing toolkit for Node.js. Loaderao runs it at a scale one laptop cannot reach, with the generators, telemetry and cleanup handled.

Read the Artillery docs
  • Your YAML unchanged: phases, flows and plugins.
  • Plugins and custom JavaScript supported.
  • MIT licensed, with no proprietary DSL.
checkout.yml Artillery 2.x
config:
  target: "https://staging.shop.ee"
  phases:
    - duration: 120
      arrivalRate: 50
    - duration: 600
      arrivalRate: 200
      rampTo: 5000
  plugins:
    expect:
      thresholds:
        - http.response_time.p95: 400
        - http.codes.5xx: 0
scenarios:
  - name: "Checkout flow"
    flow:
      - get: "/cart"
Runs locally and on Loaderao without changes.
  • GitHub Actions
  • GitLab CI
  • Docker
  • Kubernetes
  • Node.js
  • Grafana
  • Datadog
  • Webhooks

Plans and pay as you go

Every plan runs withGitHubGitLabDockerKubernetes

Starter

For a team validating a release.

€49/month

Billed monthly

Choose Starter
  • 10,000 VU-hours a month
  • 5,000 concurrent users
  • 3 team seats
  • 7-day result retention
  • Community support

Scale

For platform teams with heavy runs.

€699/month

Billed monthly

Choose Scale
  • 250,000 VU-hours a month
  • 100,000 concurrent users
  • Unlimited seats
  • SSO and audit log
  • 90-day result retention

Pay-as-you-go pricing

No monthly fee. €0.005 per VU-hour, with volume steps at 100,000 and 500,000 hours.

A VU-hour is one virtual user under load for one hour. Ramp phases count as actual load.

Request access
  • Same EU fleet as the plans
  • 7-day result retention
  • Spend cap on every run
  1. 01Pick the load
  2. 02Run the test
  3. 03Pay for the VU-hours

Every run gets isolated generators.

Above 10,000 concurrent users, use the Scale plan.

Estimated monthly

€50

10,000 VU-hours

Effective rate
€0.0050
Per run
€5.00
Max users
10,000
Results kept
7 days
Start with PAYG
First 100,000 VU-hours
€0.005
Next 400,000
€0.004
Above 500,000
€0.003

Questions before the first run

Works withGitHubGitLab

Request access

Do I need to rewrite my tests?

No. Loaderao runs your Artillery YAML, plugins and custom JavaScript unchanged.

Where is the load generated?

From isolated generators in EU regions. Traffic and results stay in the EU.

How is a VU-hour counted?

One virtual user held under load for one hour. A run with 1,000 users for 12 minutes uses about 200 VU-hours.

Can I run it from CI?

Yes. Trigger runs from GitHub Actions, GitLab CI or any runner with the API.

What am I allowed to test?

Only systems you own or have written permission to test. We verify ownership for public targets.

Request access

Tell us the target and the load. We set up the first run and reply by email.

Only systems you own or have written permission to test.

  • EU generator fleet
  • Artillery YAML and plugins
  • Plans or pay as you go

Authorised targets and EU data residency.

We reply by email. Nothing is sent to a third party.