Skip to content
LoadStrike
Portal

Search LoadStrike

GOOD PLACES TO START

↑ ↓ selectEnter openEsc close
TRANSACTION-AWARE LOAD TESTING

Load test the full path, not just the first request. Start from real traces.

APIs, queues, services, and browser steps. One self-hosted platform to see when the whole transaction actually finishes.

Run your first test Explore the platform
Start free trial See a sample report
Self-hosted executionCode-first SDKsYour infrastructure
TRANSACTION MAPcheckout_042
  1. 01 / SOURCE
    ↗HTTP API
    POST /checkout Request accepted
  2. 02 / HANDOFF
    ≋Kafka stream
    orders.created
  3. 03 / COMPLETION
    ▤Browser step
    Confirmation visible Outcome observed
shared tracking ID
One transaction. Every handoff.

Illustrative workflow · animation is a demo, not live traffic.

FROM EVIDENCE TO OUTCOME
  1. 01 Capture real behavior
  2. 02 Review your scenario
  3. 03 Test the full transaction
Transaction-aware load testing

LoadStrike is a self-hosted load testing, performance testing, and stress testing tool for real transactions.

Use one code-first runtime across APIs, queues, services, and browser steps.

See Trace-To-Test Start Free Trial
See Sample Report Compare With k6
  • Self-hosted load, performance, and stress testing.
  • APIs, streams, browser journeys, and services in one run.
  • Clear reports that show where the transaction slowed or failed.
FOLLOW THE WORK

The interesting part happens
after the first request.

Build tests around the outcome that matters. Keep the source action and downstream result in the same measured path.

01API → ASYNC

The response is just the beginning.

Follow the request into the downstream event that proves the work actually finished.

Transaction testing
02BROKERS → SERVICES

Keep the handoffs in the picture.

Connect a shared tracking value across APIs, queues, and services to measure completion.

Event-driven systems
03BROWSER → BACKEND

Measure the journey people feel.

Connect a browser action to the backend outcome, alongside the steps a user sees.

Browser journeys
ONE CORRELATED VIEW

Every handoff has a story.
Read the whole report.

Inspect latency, failed rows, and threshold outcomes together. Follow the trace through to completion.

▥Correlated reportcheckout / sample run
01 / ACROSS THE HANDOFFS DEMO

Full transaction latency

From trigger to observed outcome

331ms
015030045000:0000:3001:00
02 / YOUR LANGUAGE

Code-first. Same outcome.

Start with the SDK you already use.

using LoadStrike;

var httpClient = new HttpClient
{
    BaseAddress = new Uri("https://api.example.com")
};

var scenario = LoadStrikeScenario.Create("read-order", async context =>
{
    var orderId = $"ord-{context.InvocationNumber}";

    var step = await LoadStrikeStep.Run<string>("GET /orders/{id}", context, async () =>
    {
        using var response = await httpClient.GetAsync($"/orders/{orderId}");

        return response.IsSuccessStatusCode
            ? LoadStrikeResponse.Ok<string>(statusCode: ((int)response.StatusCode).ToString())
            : LoadStrikeResponse.Fail<string>(
                statusCode: ((int)response.StatusCode).ToString(),
                message: "Order lookup failed");
    });

    return step.AsReply();
})
.WithLoadSimulations(
    LoadStrikeSimulation.Inject(10, TimeSpan.FromSeconds(1), TimeSpan.FromSeconds(20))
);

LoadStrikeRunner.RegisterScenarios(scenario)
    .WithRunnerKey("rkl_your_local_runner_key")
    .Run();
Full quick start ↗

Defined limits. Clear outcomes.

↗
Completion p95381 ms✓ < 500 ms
Failed rows0.28%✓ < 1%
Matched outcomes99.72%✓ > 99%

Failed rows count

0007of 2,500
sample transactions
checkout_013timeout2.01s

Illustrative report with simulated telemetry. Results depend on your workload, configuration, SDK, and plan.

START WITH WHAT ALREADY HAPPENED

Real behavior.
A better starting point.

Bring a HAR, OpenTelemetry trace, browser recording, or message sample. Trace-To-Test Autopilot creates a starter scenario for you to review before replay.

Explore Trace-To-Test
Direct answer

What is LoadStrike?

LoadStrike is a self-hosted load testing, performance testing, and stress testing tool for teams that test full workflows, not only single endpoints.

It is strongest when a run must explain API traffic, event streams, browser journeys, and downstream completion in one report.

Trace-To-Test Autopilot

Turn production-like evidence into a reviewed load test draft.

Use existing evidence to create a safer first test draft.

Bring evidence

Use a HAR, OpenTelemetry trace, browser recording, or message pair.

Generate safely

Autopilot hides secrets and asks for review before replay.

Start ahead

Get endpoints, selectors, thresholds, and a starter scenario.

Read Autopilot Docs See Product Overview
Best-fit workloads

Use LoadStrike when the answer comes after the first hop.

Best for workloads that cross more than one system.

API to async completion

Measure the request that starts the workflow and the downstream event or service that proves it actually finished.

See transaction load testing

Browser plus backend correlation

Run Playwright or Selenium journeys and still connect the UI action to backend completion.

See browser load testing

How it works

Follow one clear path from workload trigger to final report.

Most teams only need four concepts to understand what LoadStrike is doing.

01 Start with the real trigger

Define the request, message, or browser action that begins the transaction.

02 Track the shared field

Use the same tracking selector across source and destination so the workflow can be matched correctly.

03 Correlate across the handoffs

Keep APIs, brokers, services, and browser steps inside one measured path.

04 Read one report

Review summary, failures, thresholds, and latency in one place.

Why it is different

Built for workflows that cross APIs, streams, services, and browser journeys.

Use it to see whether a transaction completed, timed out, duplicated, or failed.

Product proof

See the report before you go deep.

Start with the report model, then use the quick start and protocol guides.

  • Trace-To-Test Autopilot creates a first draft from real behavior.
  • HTML, CSV, TXT, and Markdown reports come from each run.
  • Grouped correlation shows latency by tenant, region, or event type.
  • The same model supports local runs, clusters, sinks, and browser journeys.
Read Report Overview Open Docs Hub
Diagram highlighting summary, scenario tabs, failed rows, thresholds, and grouped correlation within a LoadStrike report.
Move from summary to failures and grouped latency without guesswork.
Common questions

Questions teams ask before they move beyond endpoint-only testing

These answers keep the evaluation short before you step into the quick start, report guide, or comparison pages.

Is LoadStrike a load testing tool or a performance testing tool?

It is both. LoadStrike is a code-first load testing and performance testing tool that also supports stress testing when teams need to validate complete software transactions under pressure.

What is Trace-To-Test Autopilot in LoadStrike?

Trace-To-Test Autopilot turns HARs, OpenTelemetry traces, browser recordings, or message samples into a safer starter scenario that engineers can review carefully before running real load.

What does transaction load testing mean in LoadStrike?

It means measuring the full workflow that matters to the business, including the request, the async handoff, the downstream service, and the final completion signal.

When is LoadStrike a better fit than an endpoint-only load tool?

Use LoadStrike when success is visible only after another system, queue, browser step, or service finishes its work, and the report needs to explain that full path.

Which SDKs and workflow types does LoadStrike support?

LoadStrike keeps one model across C#, Go, Java, Python, TypeScript, and JavaScript so teams can test API traffic, browser journeys, stream transports, reports, and supported cluster execution in their preferred language.

Can LoadStrike combine browser, API, and async system behavior in one report?

Yes. A scenario can include browser actions, API calls, and async tracking so the report shows where the full journey passed, slowed down, or failed.

Start evaluating

Pick the next step.

Choose the shortest route for your role.

Start here

Model one real transaction and validate it under load.

One end-to-end result tells you more than another request-only benchmark.

Start Free Trial View Pricing
MAKE COMPLETION THE MEASURE

Start with one real transaction.

Define the trigger. Track the outcome. See the full path.

Open the quick start