Performance gates in every pipeline
Add a load test step to your CI/CD pipeline and block deployments automatically when p99 latency or error rate exceeds your thresholds.
Challenges you face
Performance tested only at release time
Load tests run once before a major release — finding issues when they're most expensive to fix.
No automated pass/fail signal
Running a load test produces results, but someone still has to manually interpret them and decide whether to proceed.
Pipeline tooling doesn't support load testing
Existing CI/CD tools have no native integration for load testing — it requires custom scripts and brittle hacks.
How perfscale helps
Any CI system
Trigger tests via the REST API from GitHub Actions, GitLab CI, CircleCI, Jenkins, or any pipeline tool that supports HTTP.
One API call to run
POST to /api/v1/tasks with a test ID. Poll for completion. Get a structured result. Block the build if thresholds fail.
Threshold-based exit codes
Runs return a status of passed or failed based on your defined SLOs — no result parsing required.
Per-branch test runs
Run a load test for every pull request and block merges when performance regresses.
PR annotations
Post p95 latency and error rate as a pull request comment so developers see the impact of their changes immediately.
Notification hooks
Send results to Slack, PagerDuty, or any webhook endpoint when a load test fails in CI.
What you get
- Works with GitHub Actions, GitLab CI, Jenkins
- REST API for full automation
- Structured JSON results for custom tooling
- Pass/fail based on p50/p95/p99/error rate
- Test every PR, not just main branch
- Zero new infrastructure to manage
- Reuse the same test across environments
- Audit trail of every CI-triggered run
Automate performance testing in your pipeline
See how to add a perfscale step to your GitHub Actions or GitLab CI workflow.
Get in touch