A corporate VPN for teams that work in Cursor
Cursor sits in the editor all day, and its chat, completions and agents depend on its service. Guard Tun gives the team a stable route to that service without sending all of their traffic through a VPN.
An editor that is always online
Most tools are used in bursts. An AI editor is different: completions appear as you type, chat answers while you read the code, and agents run in the background. All of it calls the service constantly, so the editor feels the network more than most applications do.
An unstable route shows up as stalls: a completion that arrives late, a chat that hangs, an agent that stops halfway. When a whole team works this way, the route has to be a managed part of the workplace, not something each developer fixes alone with a consumer VPN app.
Only Cursor's traffic in the tunnel
The client sends the Cursor domains through an encrypted tunnel to a node on your own server. The address the service sees is your server's address, the same for every developer. Everything else, from package downloads to video calls, goes direct, so nothing else is slowed down.
The same client also routes the domains of Anthropic, OpenAI and JetBrains, so a developer who uses Cursor next to Claude Code or Codex has one route for all of them.
Lists you control
AI tools add and change domains over time. The routing lists are yours to manage:
- Administrators add domains and networks by hand.
- Public lists are refreshed every hour.
- Additions suggested by AI are only proposals. They take effect after an administrator approves them, and not before.
The people who run the installation stay in control of what goes through the tunnel.
If the tunnel drops
Reliable leak protection runs on Windows, macOS and Linux. If the tunnel drops, traffic to the listed Cursor domains stops instead of going out directly from the developer's own address. The protection is part of the client itself, so it does not depend on a setting inside the editor, and it works the same on Windows, macOS and Linux.
For the administrator
The console lists every device with its status and client version, and every node with its live state. The nodes and the console run on your servers, and every change an administrator makes is written to the audit log.
A developer installs the client, opens the profile link you send, and goes back to work.
Questions
Do developers have to change Cursor's settings?
No. Routing is by domain on the device. The client sends the Cursor domains through your node, and the editor itself needs no proxy setting or extension.
Will the rest of my internet be slower?
No. Only the listed AI domains go through the tunnel. Package downloads, video calls, the browser and everything else go direct, as they do now.
What if Cursor starts using a new domain?
The lists are refreshed. Public lists are updated every hour, administrators can add domains and networks by hand, and additions suggested by AI take effect only after an administrator approves them.
Is this affiliated with Anysphere?
No. It is an independent product that works with Cursor. The footer of every page carries the trademark notice.
Read next
- VPN for Claude Code Long agent sessions in the terminal on one route and one egress address.
- VPN for Codex The Codex CLI and the IDE extension use the same route as the rest of the team.
- Domain lists that stay current Your own domains, public sources refreshed every hour, and additions an administrator approves.
Request a demo or a pilot
Tell us about your team, and we will come back with a time for a call and a plan for a pilot.