Use cases
Performance workflows for real release pressure.
Start with the outcome you need: prove an API can scale, keep traffic near private systems, gate a release, or keep watch after the deploy.
- API performance testing
Validate API latency, throughput, and correctness before releases using engine files and result signals your team can review.
For: Backend engineers and API platform teams
- CI/CD performance gates
Use repeatable performance runs as release-candidate gates with explicit latency, error, and runner-health criteria.
For: Release engineering, SRE, and backend teams
- Private load generation
Generate load from a private location when the target API, staging system, or partner path should not be exposed publicly.
For: Platform, security, and regulated-industry engineering teams
- Cloud load testing
Run repeatable load tests on managed runner capacity without rebuilding runner infrastructure for every release.
For: SREs, platform teams, and backend leads