WPLoadTester 7 runs load engines inside your own AWS account. Our license is flat. EC2 bills at AWS's rate, straight to your account. No per-VU-hour. No compute premium. Savings grow with scale.
SaaS load-test platforms charge per virtual-user-hour. Your costs scale with their margin. WPLoadTester's Cloud license is a flat fee — your only variable cost is raw EC2 in your own account.
Worked example, using BlazeMeter's published rate of ~$0.15/VU-hour:
| Test size | SaaS per-VU-hour (~$0.15) | WPLoadTester Cloud: license + EC2 in your account |
|---|---|---|
| 10,000 VU × 1 hr | ~$1,500 | license + $5 EC2 |
| 50,000 VU × 2 hr | ~$15,000 | license + $50 EC2 |
| 100,000 VU × 4 hr | ~$60,000 | license + $200 EC2 |
| 500,000 VU × 8 hr | ~$600,000 | license + $2,000 EC2 |
EC2 figures come directly from our published cloud pricing table — $5/hr at 10k VU, $50/hr at 100k VU, $250/hr at 500k VU — billed straight to your Amazon account with no markup from us. Other per-VU-hour SaaS platforms (k6 Cloud, LoadRunner Cloud, Flood) use comparable pricing models to BlazeMeter. The shape of the curve is what matters: SaaS cost scales linearly with test size; WPLoadTester's doesn't.
Test traffic stays inside your VPC. The only thing that ever crosses your boundary is a low-bandwidth license check.
Test payloads, user credentials, and response data stay inside your VPC for the entire run.
Because load generators and target app are both in your account, AWS doesn't charge cross-region or inter-AZ egress you weren't already paying.
No new data-processing agreement to negotiate with a SaaS vendor. No new vendor in your SOC 2 scope.
You've already approved AWS. You've already got an enterprise agreement. You've already got reserved capacity, volume discounts, credits, and tagging. WPLoadTester 7 Cloud just slots into that — your load-test compute shows up on your existing AWS invoice alongside everything else, with the same tags, in the same cost center.
Compare that to onboarding a new SaaS vendor: security review, data-processing agreement, procurement cycle, a separate invoice in a different currency, and — when test volume spikes — a bill that's on their margin, not AWS's margin.