QA.tech + Vercel Preview Protection
This setup lets QA.tech reach Vercel preview deployments that sit behind deployment protection. It uses Vercel's Protection Bypass for Automation secret, set as custom headers in your QA.tech device preset, and bypasses password protection, Vercel Authentication, and trusted-IP restrictions for the test traffic.
What you can do
- Test password-protected preview deployments
- Keep protection on for humans, open for test agents
- Combine with per-build preview URLs from CI
Set it up
Connecting Vercel Preview Protection
- 01
In Vercel, enable Protection Bypass for Automation and copy the secret.
- 02
In QA.tech, add the bypass headers to the device preset used for the project.
- 03
Run the plan against a protected preview URL to confirm the agent gets through.
Full reference in the QA.tech docs.
Where teams use this
Vercel Preview Protection in practice
This is an enabler, not a feature: it's what makes per-PR testing on Vercel previews possible at all. Without it, protected previews block the agent and multi-environment setups stall at the front door. Same mechanism applies to protected feature-flag builds.
FAQ
Common questions
- Does this weaken protection for real users?
- No. The bypass applies only to requests carrying the secret headers.
Related integrations
Custom MCP Integrations
Next →Vercel Firewall
Your team moves fast. Can your testing keep up?
QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.