Developer through Enterprise all stay self-hosted.
Pricing
Flat self-hosted pricing for transaction-aware load testing.
Run LoadStrike on your own infrastructure for developer-first transaction load testing across C#, Go, Java, Python, TypeScript, and JavaScript workloads. Start with a 7-day trial, then choose the plan that matches your runtime, transport, and runner-key requirements.
Self-hosted runtime
No cloud usage meter
Runner-key licensing
Predictable monthly cost
Regional currency when available
Developer is the first paid tier for a single engineer validating one real transaction path.
Yearly billing lowers cost without changing the runner-key policy or plan entitlements.
Eligible new accounts can validate the product before choosing a paid plan.
Choose a plan for runner access, supported execution patterns, and integration surface. There is no cloud usage meter.
Your bill follows the selected plan, not the number of requests or correlated transactions you run.
Every paid tier keeps the same scenario, step, tracking, and reporting model while higher tiers expand the available runtime surface.
Start here
7-day Trial
Use the trial to validate one real transaction path before you commit to a broader rollout.
No payment required
7-day Trial
Use LoadStrike for 7 days with the same runtime capabilities as the Developer plan before you buy, for accounts with no prior paid license history.
Trial Free /7 days
- No payment required to start
- Same runtime capabilities as the Developer plan
- One local runner key with one registered device
- No CI/distributed runner support included
- Started directly by the signed-in account holder
- Available only before an account has any paid license history
- Expires automatically after 7 days
Paid plans
Self-hosted pricing
Choose the plan that matches how many people, environments, and extensibility points you need. You are paying for runtime access and plan entitlements, not per-run cloud consumption.
Developer
For individual engineers validating API and stream performance workloads.
Best for: Individual engineers validating one real transaction path.
Monthly $99.00 /month
Yearly $1,069.20 /year
Annual discount: 10.00%
- 1 local runner key with up to 1 registered device.
- Remote runner keys are not included in this plan.
- Scenario, step, and simulation runtime
- HTTP and Kafka endpoint adapters
- Cross-platform tracking selectors (header/json)
- Source-only reporting when destination is omitted
- HTML, CSV, TXT, and Markdown reports
- Local dev cluster (coordinator + in-process agents)
- Grouped correlation summary via GatherByField
- One local runner key with one registered machine
Most popular
Team
For teams running broader protocol mixes and distributed load execution.
Best for: Collaborative teams running broader protocol coverage and distributed execution.
Monthly $199.00 /month
Yearly $2,149.20 /year
Annual discount: 10.00%
- 1 local runner key with up to 2 registered devices.
- 1 remote runner key with up to 1 active device at a time.
- Includes all Developer features
- NATS endpoint adapter
- Redis Streams endpoint adapter
- RabbitMQ endpoint adapter
- Azure Event Hubs endpoint adapter
- Push Diffusion and delegate stream endpoint adapters
- Distributed cluster using NATS
- Redis-backed correlation store
- One local runner key with three registered machines
- CI/distributed runner support with 1 simultaneous session
Business
For high-scale test programs requiring advanced control and integration surfaces.
Best for: Larger self-serve programs that need more control and integration surface.
Monthly $299.00 /month
Yearly $3,229.20 /year
Annual discount: 10.00%
- 1 local runner key with up to 3 registered devices.
- 1 remote runner key with up to 2 active devices at a time.
- Includes all Team features
- Trace-To-Test Autopilot starter generation
- Built-in InfluxDB, TimescaleDB, Grafana Loki, Datadog, Splunk HEC, and OTEL Collector reporting sinks
- Custom reporting sinks
- Custom worker plugins
- Runtime policy controls for agents, scenarios, sinks, plugins, targeting, and timeout ceilings
- Advanced threshold policy controls
- Advanced coordinator/agent targeting and cluster tuning controls
- One local runner key with five registered machines
- CI/distributed runner support with 3 simultaneous sessions
Enterprise
For teams that need enterprise capabilities with tailored runner capacity and commercial terms.
Best for: Quote-led runner capacity, tailored terms, and procurement-heavy rollout.
- Includes all Business features
- Custom reporting sinks
- Custom worker plugins
- Runtime policy controls for agents, scenarios, sinks, plugins, targeting, and timeout ceilings
- Advanced threshold policy controls
- Advanced coordinator/agent targeting and cluster tuning controls
- Local registered machines per runner key: tailored
- Simultaneous CI/distributed runner sessions: tailored
- Private portal checkout for agreed monthly or yearly Enterprise offers
Plan fit
Match the plan to the buyer and rollout shape.
The names are meant to describe who buys the plan, not how the runtime itself works.
Individual engineers validating one real transaction path.
Collaborative teams running broader protocol coverage and distributed execution.
Larger self-serve programs that need more control and integration surface.
Quote-led runner capacity, tailored terms, and procurement-heavy rollout.
Feature comparison
See what changes by tier.
The table keeps the entitlement story consistent across transports, cluster execution, sinks, and extensibility.
| Feature | Developer | Team | Business | Enterprise |
|---|---|---|---|---|
| Scenario runtime, steps, and load simulations | ✓ | ✓ | ✓ | ✓ |
| HTTP endpoint adapter | ✓ | ✓ | ✓ | ✓ |
| Kafka endpoint adapter | ✓ | ✓ | ✓ | ✓ |
| Cross-platform tracking selectors (header/json) | ✓ | ✓ | ✓ | ✓ |
| Source-only reporting (destination optional) | ✓ | ✓ | ✓ | ✓ |
| Grouped correlation summary via GatherByField | ✓ | ✓ | ✓ | ✓ |
| Report formats: HTML, CSV, TXT, Markdown | ✓ | ✓ | ✓ | ✓ |
| Local dev cluster (coordinator + in-process agents) | ✓ | ✓ | ✓ | ✓ |
| Local runner key included | ✓ | ✓ | ✓ | ✓ |
| Local registered machines per runner key | 1 | 2 | 3 | Tailored |
| RabbitMQ endpoint adapter | — | ✓ | ✓ | ✓ |
| Azure Event Hubs endpoint adapter | — | ✓ | ✓ | ✓ |
| NATS endpoint adapter | — | ✓ | ✓ | ✓ |
| Redis Streams endpoint adapter | — | ✓ | ✓ | ✓ |
| Push Diffusion and delegate stream endpoints | — | ✓ | ✓ | ✓ |
| Distributed cluster using NATS | — | ✓ | ✓ | ✓ |
| CI/distributed runner support | — | ✓ | ✓ | ✓ |
| Simultaneous CI/distributed runner sessions | — | 1 | 2 | Tailored |
| Redis-backed correlation store | — | ✓ | ✓ | ✓ |
| Trace-To-Test Autopilot | — | — | ✓ | ✓ |
| Built-in vendor sinks: InfluxDB, TimescaleDB, Grafana Loki, Datadog, Splunk HEC, and OTEL Collector | — | — | ✓ | ✓ |
| Custom reporting sinks | — | — | ✓ | ✓ |
| Custom worker plugins | — | — | ✓ | ✓ |
| Runtime policy controls | — | — | ✓ | ✓ |
| Advanced threshold policy controls | — | — | ✓ | ✓ |
| Advanced coordinator/agent targeting and cluster tuning controls | — | — | ✓ | ✓ |
Direct answer
How is LoadStrike priced?
LoadStrike pricing is built around self-hosted plan tiers that keep the same core transaction-testing model while expanding runner access, transport coverage, distributed execution, and extensibility where the plan includes it.
Teams can start with a time-boxed trial and then choose the plan that matches how widely they need to run the workload, which transports and reporting surfaces they need, and whether they require broader team or distributed execution support.
The public pricing page automatically shows GBP for United Kingdom visitors, EUR for EU and EEA visitors, and USD for the rest of the world when a complete price is available for that plan. After signup, the account keeps the country captured at creation time so billing, renewals, and plan changes stay consistent.
Common questions
Pricing questions teams ask before rollout
These answers explain how the self-hosted pricing model changes as teams expand runner access, transports, and execution patterns.
What changes between LoadStrike pricing plans?
The plans keep the same core scenario model but change the surrounding entitlements, such as runner-key coverage, transport breadth, distributed execution eligibility, and advanced extensibility features. That lets teams grow the operational surface without relearning how scenarios, thresholds, and reports are modeled.
Is LoadStrike priced for self-hosted use?
Yes. The pricing page is centered on self-hosted usage, not on cloud load consumption. Teams run the product on their own infrastructure and choose the plan that matches the runtime access and product surface they need for that operating model.
How does regional pricing work on the public page and in the portal?
The public pricing page uses the visitor region to show GBP for the United Kingdom, EUR for EU and EEA countries, and USD everywhere else when a complete price is available for that plan. Once an account is created, the billing country captured at signup is reused for the customer portal so renewals and plan changes stay on the same regional pricing track.
How are plan changes billed?
Paid plan changes apply to the current subscription. If the change happens before the current billing period ends, the customer may receive a prorated charge or credit for the remaining time.
How do private Enterprise offers work?
When LoadStrike agrees custom Enterprise terms with an account, that account can see the private offer in the Enterprise Offers tab of the customer portal. The offer shows the monthly and yearly price, local and remote runner key counts, per-key device allowances, and any expiry date. The customer chooses a billing interval, accepts the current terms, and completes recurring payment through Stripe Checkout.
Do all paid plans use the same scenario and reporting model?
Yes. The core runtime shape stays consistent across the paid plans. What changes is how much of the surrounding product surface is available, such as broader transports, team entitlements, or distributed execution controls, rather than switching teams to a different workflow model.
Can a team evaluate LoadStrike before buying a paid plan?
Yes. The pricing surface includes a trial path so teams can validate the product on a real transaction before they commit to a broader rollout. That helps engineering teams test fit on an actual workflow instead of guessing from static feature lists alone.
Choose a rollout path
Validate fit first, then choose the plan that matches the rollout.
The cleanest buying path is usually quick start, report review, pricing decision.