Anchor VPN is a premium feature enabled by the Anchor team upon request. It can be scoped to an entire project or to a specific identity. Contact the Anchor team to get started.
Why it matters
Unstable IPs, low-reputation shared exits, and slow proxy hops are the root cause of most browser automation failures at scale. They lead to session drops, failed auth, elevated risk scores, and sluggish page loads — all of which compound when you’re running many sessions. Anchor VPN addresses all three at once.Secure
Your assigned egress IP is used by you alone. It is not shared with other customers in a multi-tenant pool where unrelated traffic degrades the address’s reputation and broadens the blast radius of any incident. There is no third-party proxy operator sitting between the browser and the internet. Traffic stays on Anchor-operated infrastructure under Anchor’s security program, so no outside vendor can observe, log, or mishandle your sessions.Reliable
Which egress IP you use — and whether the same IP is reused across sessions — is driven by your Anchor VPN configuration. Once an assignment is active, all HTTP(S) traffic follows it. There is no routine mid-session rotation for load-spreading; downstream sites see a steady origin for the lifetime of the assignment. Exits are health- and latency-monitored. If a node goes unhealthy, failover is policy-driven and designed to minimize geographic jumps rather than silently dumping you onto a random replacement.Fast
Traffic leaves the browser through exits provisioned for Anchor sessions — not through oversubscribed shared proxy endpoints that add latency on every request. The stack is tuned for interactive pages and APIs: TLS optimization, connection reuse, and direct peering. Because the IP stays stable, you also avoid the hidden performance tax of proxy churn: fewer captchas, fewer re-auth flows, and less wall-clock time lost to recovery loops that fire every time the origin IP changes.How it works
Consistent routing is applied at the browser networking layer before requests are dispatched.| Component | Role |
|---|---|
| Session router | Applies your VPN configuration — selecting an exit and, where enabled, reusing an egress IP across sessions |
| Exit node pool | Regionally grouped endpoints monitored for health and latency |
| Routing policy engine | Enforces assignment rules, stickiness settings, and failover behavior |
Get started
Anchor VPN is enabled by the Anchor team upon request. Contact us to enable it for your project or identity.Related capabilities
Proxy
Country, region, and city targeting with Anchor’s proxy or bring your own.
Dedicated Sticky IP
A fixed IP reserved per profile across sessions.