Developer through Enterprise all stay self-hosted.
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, reporting, and extensibility requirements.
Developer is the first paid tier for a single engineer validating one real transaction path.
Yearly billing lowers cost without changing the selected plan entitlements.
Eligible new accounts can validate the product before choosing a paid plan.
Choose a plan for supported execution patterns, reporting, 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.
7-day Trial
Use the trial to validate one real transaction path before you commit to a broader rollout.
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
- Single-license trial for one account
- Self-hosted runtime access for evaluation
- Started directly by the signed-in account holder
- Available only before an account has any paid license history
- Expires automatically after 7 days
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 performance workloads.
Best for: Individual engineers validating one real transaction path.
Monthly $99.00 /month
Yearly $1,069.20 /year
Annual discount: 10.00%
- Scenario, step, and simulation runtime
- HTTP endpoint adapter
- Cross-platform tracking selectors (header/json)
- Source-only reporting when destination is omitted
- HTML, CSV, TXT, and Markdown reports
- Scenario targeting and scenario completion timeout controls
- Local dev cluster (coordinator + in-process agents)
- Grouped correlation summary via GatherByField
- One license for self-hosted execution
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%
- Includes all Developer features
- Kafka endpoint adapter
- NATS endpoint adapter
- Redis Streams endpoint adapter
- RabbitMQ endpoint adapter
- AWS SQS endpoint adapter
- Azure Event Hubs endpoint adapter
- Push Diffusion and delegate stream endpoint adapters
- Distributed cluster using NATS
- Redis-backed correlation store
- One license for self-hosted execution
- Distributed execution support for team workflows
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%
- Includes all Team features
- Trace-To-Test Autopilot starter generation
- Traffic Mix workload distribution across weighted scenario lanes
- Accessibility testing and browser Web Vitals helper scenarios
- Delegate-backed gRPC and WebSocket endpoint adapters
- Customer portal Run Reports with a query explorer, scenario-first graphs, run-derived scenario sets, saved views, exports, sharing, percentile selection, and byte metrics
- 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, scenario counts, sinks, plugins, and cluster-command timeout ceilings
- Advanced threshold policy controls
- Advanced coordinator/agent targeting and cluster tuning controls
- One license for self-hosted execution
- Distributed execution support for business workflows
Enterprise
For teams that need enterprise capabilities with tailored configuration and commercial terms.
Best for: Quote-led configuration, tailored terms, and procurement-heavy rollout.
- Includes all Business features
- Trace-To-Test Autopilot starter generation
- Custom reporting sinks
- Custom worker plugins
- Runtime policy controls for agents, scenario counts, sinks, plugins, and cluster-command timeout ceilings
- Advanced threshold policy controls
- Advanced coordinator/agent targeting and cluster tuning controls
- Enterprise license configuration tailored to the rollout
- Distributed execution capacity configured for enterprise needs
- Private portal checkout for agreed monthly or yearly Enterprise offers
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 configuration, tailored terms, and procurement-heavy rollout.
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 | ✓ | ✓ | ✓ | ✓ |
| Scenario targeting and scenario completion timeout controls | ✓ | ✓ | ✓ | ✓ |
| Trace-To-Test Autopilot | — | — | ✓ | ✓ |
| Traffic Mix workload distribution | — | — | ✓ | ✓ |
| Accessibility testing and browser Web Vitals helper scenarios | — | — | ✓ | ✓ |
| HTTP endpoint adapter | ✓ | ✓ | ✓ | ✓ |
| Kafka endpoint adapter | — | ✓ | ✓ | ✓ |
| RabbitMQ endpoint adapter | — | ✓ | ✓ | ✓ |
| AWS SQS endpoint adapter | — | ✓ | ✓ | ✓ |
| Azure Event Hubs endpoint adapter | — | ✓ | ✓ | ✓ |
| NATS endpoint adapter | — | ✓ | ✓ | ✓ |
| Redis Streams endpoint adapter | — | ✓ | ✓ | ✓ |
| Push Diffusion and delegate stream endpoints | — | ✓ | ✓ | ✓ |
| Delegate-backed gRPC and WebSocket endpoints | — | — | ✓ | ✓ |
| Cross-platform tracking selectors (header/json) | ✓ | ✓ | ✓ | ✓ |
| Source-only reporting (destination optional) | ✓ | ✓ | ✓ | ✓ |
| Grouped correlation summary via GatherByField | ✓ | ✓ | ✓ | ✓ |
| Redis-backed correlation store | — | ✓ | ✓ | ✓ |
| Report formats: HTML, CSV, TXT, Markdown | ✓ | ✓ | ✓ | ✓ |
| Customer portal Run Reports | — | — | ✓ | ✓ |
| Built-in vendor sinks: InfluxDB, TimescaleDB, Grafana Loki, Datadog, Splunk HEC, and OTEL Collector | — | — | ✓ | ✓ |
| Custom reporting sinks | — | — | ✓ | ✓ |
| Local dev cluster (coordinator + in-process agents) | ✓ | ✓ | ✓ | ✓ |
| License model | One self-serve license | One self-serve license | One self-serve license | Tailored configuration |
| Distributed cluster using NATS | — | ✓ | ✓ | ✓ |
| Advanced coordinator/agent targeting and cluster tuning controls | — | — | ✓ | ✓ |
| Custom worker plugins | — | — | ✓ | ✓ |
| Runtime policy controls | — | — | ✓ | ✓ |
| Advanced threshold policy controls | — | — | ✓ | ✓ |
How is LoadStrike priced?
LoadStrike pricing is built around self-hosted plan tiers that keep the same core transaction-testing model while expanding transport coverage, distributed execution, reporting, 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.
Pricing questions teams ask before rollout
These answers explain how the self-hosted pricing model changes as teams expand transports, reporting, extensibility, and execution patterns.
What changes between LoadStrike pricing plans?
The plans keep the same core scenario model but change the surrounding entitlements, such as transport breadth, distributed execution eligibility, reporting surfaces, 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 agreed monthly and yearly price, enterprise configuration, 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.
Validate fit first, then choose the plan that matches the rollout.
The cleanest buying path is usually quick start, report review, pricing decision.