QA.tech + IP Access Control
IP Access Control covers environments gated by network rules. You allowlist QA.tech's egress IPs so agents can reach IP-restricted deployments, and for private-network or internal-DNS environments there's an SSH proxy tunnel.
Set it up
Connecting IP Access Control
- 01
Copy QA.tech's egress IP range from Integrations settings.
- 02
Allowlist it on the environment's firewall or load balancer.
- 03
For internal-DNS or private networks, set up the SSH proxy tunnel instead.
Full reference in the QA.tech docs.
Where teams use this
IP Access Control in practice
This is the route into environments that never touch the public internet. Internal staging in regulated industries is the typical case: fintech and healthcare teams keep environments behind network controls and tunnel the agent in rather than opening anything up.
FAQ
Common questions
- Our staging has internal DNS only. Can QA.tech reach it?
- Yes, through the SSH proxy tunnel.
Related integrations
Cloudflare WAF & Turnstile
Next →Status Badges
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.