VPN for Internal Environments
Test private staging apps, internal APIs, and resources behind your firewall without exposing them publicly.
Start for free • No credit card required
Supported protocols
OpenVPN and WireGuard are supported for secure access to internal resources.
Per-run isolation
Each test run gets its own dedicated VPN connection to prevent cross-run leakage.
Private resource access
Reach staging environments, internal hostnames, and private APIs when DNS and VPN configuration are set correctly.
When VPN is configured at the project level, Mechasm automatically creates an isolated network namespace, establishes the VPN connection inside it, and routes the browser through that tunnel. Your tests still navigate to internal URLs normally.
Secure access without workflow changes
VPN-backed execution is designed to work automatically once the project-level integration is configured.
Automatic routing
The browser is routed through the VPN-backed connection without requiring special test commands.
Isolated network namespace
Each run establishes the connection inside an isolated network environment for cleaner execution boundaries.
Internal URL support
Navigate to internal staging URLs normally once the VPN and DNS settings are in place.
Operational guardrails
This capability should be described narrowly and truthfully around internal environments and private resources.
No custom test steps
VPN usage is automatic after integration setup rather than something test authors have to script manually.
Safer parallel execution
Connection isolation reduces the risk of one test polluting another during concurrent runs.
Truthful scope
This is for internal environments and private resources, not a blanket claim about arbitrary localhost access.
Explore the rest of the platform
Dive deeper into the product surface around this capability and see how it connects to the rest of Mechasm's autonomous testing workflow.