Run Your K6 Scripts
As They Are
Keep your K6 tests in Git with the rest of your code. OctoPerf runs them on distributed load generators and analyzes them in the same reports as JMeter™.
Get Started Learn More- No Script Rewrite
- K6, JMeter™ and Playwright in One Scenario
- SaaS or On-Premise
2 Ways to Bring Your K6 Tests to OctoPerf
Run your existing K6 tests on distributed load generators, with enterprise reports.
Get started with OctoPerf today
Schedule a DemoWhat’s next?
A Scenario From Your K6 Options
Paste the output of k6 inspect and OctoPerf creates one user profile per K6 scenario, with its load and its function.
A notification lists what could not be converted, so you can check how the load was translated.
Edit and Debug Before Scaling
The editor checks the syntax and completes the K6 API and the variables of your project.
A validation runs one iteration and records every request with its headers and body. When the script fails, the error points at the line of your file.
Test Data Split Between Load Generators
Constants and secrets reach the script through __ENV, CSV and random variables through a module OctoPerf generates.
CSV files are split between the load generators, so two of them never log in with the same account.
More Than HTTP
Load test gRPC, WebSocket, SQL, Redis and Kafka along with HTTP. Every call shows up as a request of the report, with its response time and status.
With an on-premise installation, you can also rebuild the K6 image with your own xk6 extensions.
The Same Reports as JMeter™
Requests, groups, checks, custom metrics and thresholds land in the OctoPerf reporting engine: history, comparison, trends and SLAs.
A scenario can mix K6, JMeter™ and Playwright Virtual Users, and the reports keep each engine apart.
Watch the Load Generators
The K6 Runtime monitor follows the CPU, memory, Go heap and garbage collection of each load generator.
It raises an alarm when the virtual users need more CPU or memory than the load generator can give them.
Load Tests in Your Pipeline
Import the scripts of your repository and run the test at every build, from any CI server.
SLAs and K6 thresholds can fail the build when the response times degrade.
Run Your K6 Tests on OctoPerf
Import your K6 scripts and run them on distributed load generators, with split test data, reports and monitoring.