Your AI. Your keys. Your boundary.
WPLoadTester 7 uses your own Anthropic, OpenAI, or AWS Bedrock key. Your enterprise contract already covers it, your security team already approved it, and your data stays wherever it already lives. No new vendor review. No AI markup.
Three providers, all of them yours
Paste a key. That's the integration. The AI call happens between WPLoadTester and the provider of your choice — WPI never sits in the middle, never sees your prompts, never stores your data.
Claude models direct via the Anthropic API. If your enterprise has an Anthropic contract, WPLoadTester just uses it.
GPT models direct via the OpenAI API. Same approval, same billing account, same audit trail you already have.
Any model available in your AWS region — Claude on Bedrock, Llama, Titan, and more. Your AWS governance, your IAM policies, your VPC.
What the AI sees once you've configured it
Once you've pasted your key, the AI Assistant lives inside WPLoadTester — analyzing your test cases, identifying auth patterns, and explaining what it's about to do before it does it.
When the AI hits something tricky, you see it think.
For harder configuration problems — extracting a JWT from a streaming Next.js payload, correlating dynamic variables across pages, debugging a regex that isn't matching — the AI walks through its attempts out loud instead of silently giving up. You see exactly what it tried, what it observed, and why it's refining.
And after the test runs, the AI interprets the results.
WPLoadTester 7's Load Test Analytics dashboard produces AI-written views of every run — a plain-English performance narrative, and a bottleneck analysis that picks out inflection points and traces root causes from the actual numbers.
Why security and procurement will like it
Every objection a security review raises against "another SaaS AI vendor" evaporates when the AI is one you've already approved.
No new vendor review
Your security team has already vetted Anthropic, OpenAI, or AWS. The path of an AI request is identical to what they approved.
Existing contracts apply
Enterprise pricing, volume commits, SLA, usage limits, cost-center tagging — whatever you negotiated with your AI vendor carries straight through.
Data stays within your boundary
Prompts and responses travel between WPLoadTester and the provider you chose. WPI isn't in the request path and never sees the payload.
No AI markup
You pay what the provider charges. Token pricing is transparent. WPLoadTester doesn't add a margin on AI usage.
The Bedrock angle: regulated and air-gapped buyers
If your organization is regulated (financial services, healthcare, federal) or operates in isolated AWS environments (GovCloud, dedicated regions), AWS Bedrock support is the wedge.
Bedrock runs inside your AWS account, subject to your IAM policies, within your compliance boundary. If Bedrock is already approved for your workloads, WPLoadTester using it for AI auto-configuration is the same data-residency story — not a new one. GovCloud regions and FedRAMP-authorized environments work identically.
- ✓ anthropic.claude-3-5-sonnet-20241022-v2:0
- anthropic.claude-3-opus-20240229-v1:0
- meta.llama3-70b-instruct-v1:0
- amazon.titan-text-premier-v1:0
- cohere.command-r-plus-v1:0
Region: us-east-1 · IAM: arn:aws:iam::••••••:role/WPLoadTester