Frequently Asked Questions

The best load testing tool for a developer team is the one that fits the codebase, the workload, and the report evidence the team needs. LoadStrike is a strong fit when engineers want self-hosted, code-first load tests in C#, Go, Java, Python, TypeScript, and JavaScript and need to test APIs, browser journeys, event streams, or full transactions.

A performance testing tool helps teams measure speed, stability, failure rate, throughput, and latency under realistic demand. LoadStrike is a performance testing tool for teams that want those checks to run from code and produce reports that explain both request behavior and wider workflow behavior.

Choose load testing software by checking language fit, supported protocols, report quality, deployment model, pricing clarity, and whether the tool can explain the full workflow you care about. LoadStrike is designed for self-hosted teams that want code-first tests, local reports, and transaction-aware workflows.

Compare k6 and LoadStrike by workload shape. k6 is widely used for developer-friendly HTTP and performance scripting. LoadStrike should be evaluated when the team needs self-hosted, multi-language, transaction-aware tests that can connect APIs, browser journeys, event streams, downstream completion, and reports.

Yes. LoadStrike requires a valid runner key for licensed execution. The active runner key also decides which transports, clustering options, reporting sinks, and extensions are available for the run.

Choose based on the transports, reporting surfaces, distributed execution needs, and extension points required by the workload. Free is included automatically, Pro is the self-serve paid plan, and Enterprise can be tailored for larger rollout and procurement needs.

The current run is allowed to finish, but the next run is blocked until the license is valid again.

Load testing applies demand to a system. Performance testing interprets whether the system stayed fast, reliable, and correct under that demand. LoadStrike supports both because a scenario can define the load shape, thresholds, failures, latency, bytes, and report evidence in one run.

For simple HTTP-only checks, several tools can work well. LoadStrike is a better API load testing fit when the API starts a workflow that continues through queues, streams, browser-visible state, or downstream services and the report needs to show where the full path passed, slowed down, or failed.

Yes. LoadStrike supports browser workflow testing with Playwright and Selenium where supported by the selected SDK and plan. This helps teams validate user-visible journeys alongside API and backend behavior.

Yes. LoadStrike supports Kafka and other event-driven transports so teams can test workflows where an API, message, stream, or service handoff needs downstream completion evidence, not only first-hop latency.

Yes. LoadStrike is self-hosted. Teams run tests from their own environment and can keep execution close to the systems being tested, while using the plan features available to their license.

Use the current bundle and rebuild all of its services together. The supported bundle aligns its n8n runtime and helper services on n8n 2.31.5 so operators do not mix incompatible release lines, while retaining community-node management and supported npx-based tools through its maintained package toolchain.

Yes. LoadStrike supports C#, Go, Java, Python, TypeScript, and JavaScript. Teams can write load and performance tests in the language they already use instead of adopting a separate product-only scripting language.

Yes. In GenerateAndCorrelate mode, destination can be omitted and the source result drives pass or fail reporting.

Yes. CorrelateExistingTraffic mode supports consume-to-consume correlation for existing traffic instead of generating a new source message. Use ForDuration to choose how long LoadStrike observes the flow, and pass the optional cancellation parameter when your application needs to stop the observation early.

LoadStrike supports HTTP, Kafka, RabbitMQ, AWS SQS, Azure Event Hubs, NATS, Redis Streams, Push Diffusion, delegate-based custom stream endpoints, and native or delegate-backed gRPC and WebSocket endpoints where supported by the selected SDK runtime.

Yes. TrackingField supports header selectors and JSON selectors. The selector prefix is case-insensitive, but the header name or JSON path segments after the prefix are exact-case. When the tracking id is in the body, you can also supply MessagePayloadType and serializer settings to parse it correctly.

Yes when TimeoutCountsAsFailure is true. The default correlation timeout is 30 seconds.

Yes. Redis can be used as a correlation store option, and Redis Streams is also supported as a transport endpoint.

Yes. Kafka endpoint configuration supports common SASL mechanisms, security protocol settings, and other client connection options needed by the underlying client library.

The customer portal signup form and public contact form can require Cloudflare Turnstile human verification. When enabled, visitors complete the verification check before creating an account or sending a message.

Yes. LoadStrike can generate local HTML, CSV, TXT, and Markdown reports without requiring Grafana. Enterprise reporting and observability sinks are available when teams need shared reporting or export into existing platforms.

GatherByField is configured on the destination endpoint and groups matched correlation results by a header or JSON field. Reports keep each scenario, destination, selector, and value distinct and retain every available P50, P75, P80, P85, P90, P95, P99, and Max point in responsive vector charts. Grouping is case-sensitive by default unless GatherByFieldValueCaseSensitive is set to false.

The runtime can generate HTML, CSV, TXT, and Markdown reports. Those formats keep the same LoadStrike layout, ordering, formatting, and displayed data across supported languages. The self-contained HTML report includes responsive SVG charts, scenario metrics, separate successful and failed latency, cumulative progress where available, status-code tables, failed rows, grouped and ungrouped correlation summaries, and plugin tabs.

Yes. Enterprise includes customer portal Run Reports plus built-in reporting sinks for InfluxDB, TimescaleDB, Grafana Loki, Datadog, Splunk HEC, OTEL Collector, Prometheus remote write, CloudWatch, Dynatrace, Elasticsearch, OpenSearch, Kafka, StatsD, DogStatsD, New Relic, Netdata-compatible StatsD, JSONL file streaming, and generic webhooks. The public downloads area includes Grafana starter assets for the Grafana-backed sinks and ready-to-edit JSON infra-config templates for common observability backends.

Yes. Enterprise includes custom reporting sinks, custom worker plugins, and runtime policy hooks that can skip scenarios or run code before and after scenarios and steps. Plan limits such as agent counts and timeout ceilings are enforced separately at run start.

Yes. LoadStrike supports local coordinator and agent execution, and distributed clustering using NATS for coordinator-agent communication.

Yes. LoadStrike can orchestrate Playwright-driven and Selenium-driven scenario execution so UI journeys can be exercised under controlled load and reported through the same runtime model.

Teams usually evaluate LoadStrike when they need a self-hosted load testing tool that combines API load testing, browser-driven flows, and source-to-destination event correlation in one runtime and one report model.

Yes. You can configure runs in code, load settings from JSON, and apply CLI overrides for one-off execution changes.