Collection
Every API request lives in one shared collection, built once and reused across projects.
WinScale
Your API collection. A real load test.
Point WinScale at APIs you already have, set a Load Profile, and it generates and runs the K6 plan itself. No scripts to hand-write, and a run you can repeat every release.
POST /checkout 200 142ms GET /cart 200 88ms POST /payment 500 310ms
Go
42 of 43 checks passed · 1 flagged for review
- Collection
- Flow
- Feature
- Load Profile
- Run
- Report
Six words
Learn the vocabulary. Every screen uses it.
Six concepts underpin WinScale. Once they make sense, so does the whole tool.
Environment
Point the same collection at dev, staging or production without editing a single request.
Flow
Chain requests into an ordered sequence, with data passed from one step into the next.
Feature
Combine Flows into the actual end-to-end journey you want under load.
Load Profile
Set virtual users, concurrency and ramp-up. WinScale turns it into a K6 plan.
Threshold
Define what counts as a pass, so a run ends with a verdict, not just numbers.
Load profiles
Four ways to shape the load.
Pick the curve that matches what you are actually testing for.
A flat, steady number of virtual users for the whole run.
Users increase step by step, so you can see exactly where response times start to bend.
A sudden burst of load, then back to baseline, for testing how the system recovers.
A gradual rise and fall, matching a realistic pattern like a sale or a release window.
What you get back
A dashboard, not a log file.
- Response time distribution
- Throughput
- Error rates and failures
- Bottleneck analysis
- An executive summary for the release call
First engagement
Configure one load profile. Get a release recommendation.
- You send
- One API set: a Postman collection or an OpenAPI spec
- You get
- A load profile and bottleneck report
- Time
- One week