The VS Code tunnel feature that lives in the account menu is one of the quietest changes to modern development. Sign in, run one command on the desktop tower under your desk, and the same editor opens in a browser on a budget laptop from a coffee shop, an iPad on the couch, or a locked-down work machine you cannot install anything on. The heavy compiler, the local files, and the private repos stay at home. The browser only handles the interface.
We tested seven tools that turn a physical machine into a browser-reachable coding environment. Some run through Microsoft’s official tunnel service, some self-host their own bridge, and a couple treat cloud-hosted development as a first-class product. The right pick depends on where the code should live and who is paying for the CPU.
What to look for in a remote coding setup
- Where the compute lives. Your own machine (tunnel), a self-hosted server, or a paid cloud VM. Each has cost and performance implications.
- Extension parity. A remote setup that cannot run the ESLint, Pylance, or Rust Analyzer extensions is just a fancy Notepad.
- Startup time. Cold-starting a workspace should take seconds, not minutes.
- Persistent state. Uncommitted edits, running dev servers, and terminal sessions should survive a laptop lid close.
- Network resilience. Reconnecting after a WiFi drop should not lose your cursor position or terminal buffer.
- Auth model. GitHub OAuth is fine for personal use. A team setup needs SSO and workspace-level access rules.
Quick comparison
| App | Best for | Where compute lives | Free plan | Starting price | Rating |
|---|---|---|---|---|---|
| VS Code Tunnels | Personal home-machine access | Your desktop | Fully free | Free | 4.7 |
| code-server | Self-hosted browser VS Code | Your server | Fully free | Free | 4.5 |
| Gitpod | Prebuilt cloud workspaces | Gitpod cloud or self-host | 50 hours/mo free | About $9/user/mo | 4.5 |
| Coder | Team-hosted dev environments | Your infrastructure | Free self-host | About $35/user/mo Premium | 4.4 |
| JetBrains Gateway | Remote JetBrains IDEs | Remote SSH host | Fully free client | JetBrains license needed | 4.6 |
| GitHub Codespaces | GitHub-integrated cloud IDE | GitHub cloud | 60 hours/mo free | About $0.18/hr per 2-core | 4.6 |
| Zed collab | Rust-fast collaborative editor | Zed cloud | Fully free | Free | 4.4 |
The apps
1. VS Code Tunnels — Best free personal setup
VS Code Tunnels is Microsoft’s official remote-access feature and the one everyone underestimates because it hides behind the account menu. Sign in on the desktop, run code tunnel (or click “Turn on Remote Tunnel Access” in the account menu), and any browser at vscode.dev/tunnel/
Latency stays low because the tunnel routes through Microsoft’s relay only for connection setup, then falls back on the browser’s WebSocket for actual editing traffic. Every installed extension keeps working because the code runs on the desktop, not the browser.
Where it falls short: The browser client is trimmed compared to the desktop. Some extensions that spawn child processes with special OS bindings misbehave. There is no per-repo access model, so anyone with your GitHub credentials sees the whole machine.
Pricing:
- Free: Full features, tied to a GitHub or Microsoft account
- Paid: None
Platforms: Windows, macOS, Linux for the server; any modern browser for the client
Download: VS Code, tunnel docs
Bottom line: Turn this on the moment you set up a new desktop. It is the fastest way to get a real editor onto a locked-down laptop.
2. code-server — Best self-hosted browser VS Code
code-server by Coder Inc. is a standalone binary that runs VS Code as a web application. Deploy it on a Raspberry Pi, a mini PC, or a cloud VM, then open the URL in any browser. Extensions install from the Open VSX registry rather than the Microsoft marketplace, which means most (but not every) extension is available.
Because it is self-hosted, you own the auth model. A reverse proxy with SSO, a Cloudflare Tunnel, or a plain Basic Auth setup all work. Team environments often pair code-server with Coder’s orchestration layer.
Where it falls short: Open VSX is missing some proprietary Microsoft extensions (C# Dev Kit, Pylance). No official tunnel service, so you handle port exposure yourself.
Pricing:
- Free: Fully free, MIT license
- Paid: None (Coder Enterprise is the orchestration layer sold on top)
Platforms: Linux, Docker, ARM64 (Raspberry Pi 4/5)
Download: code-server
Bottom line: The right pick when the tunnel service is a non-starter (compliance, air-gapped, offline) and you can run a Linux box.
3. Gitpod — Best prebuilt cloud workspaces
Gitpod is a hosted development environment tied to a repository. Push a .gitpod.yml file to your repo, and any contributor opens the project in a preconfigured cloud workspace with dependencies installed, ports proxied, and the dev server already running.
The prebuilt cache is the differentiator. A workspace that would take 8 minutes to install on a fresh laptop opens in under 30 seconds because Gitpod runs the setup ahead of time on every push.
Where it falls short: Free tier is 50 hours per month; a heavy user burns through it in a week. Self-hosted Gitpod (Flex) is available but more setup than Coder.
Pricing:
- Free: 50 hours/month, standard workspace
- Paid: About $9/user/mo Professional, $25/user/mo Enterprise
Platforms: Web browser (any), desktop VS Code via Gitpod extension
Download: Gitpod
Bottom line: The obvious choice when new contributors should be productive in the first hour, not the first day.
4. Coder — Best team-hosted dev environments
Coder is the enterprise sibling of code-server, focused on running many developer workspaces on your own infrastructure. Terraform templates define workspace shapes (image, CPU, storage), engineers pick from the catalog, and the platform provisions everything on your Kubernetes cluster or VM host.
The audit log and workspace lifecycle features (auto-stop, scheduled provisioning) are what teams pay for. A 20-person shop replaces “get your laptop set up” onboarding with a single URL.
Where it falls short: Self-hosting means you own the reliability. Small teams do not need this much orchestration and get more done with plain code-server or Codespaces.
Pricing:
- Free: OSS edition, self-host on your infrastructure
- Paid: About $35/user/mo Premium with SSO, audit, and support
Platforms: Kubernetes, Docker, AWS, Azure, GCP
Download: Coder
Bottom line: Right when the team is big enough that “install these 40 tools” is a real onboarding cost.
5. JetBrains Gateway — Best remote JetBrains IDEs
JetBrains Gateway is a thin client that connects to IntelliJ, PyCharm, GoLand, or any JetBrains IDE running on a remote SSH host or a cloud dev container. The IDE runs entirely on the server; the client renders the UI over a proprietary low-latency protocol.
For long compile projects (large monorepos, Rust workspaces, Kotlin builds), the offload matters. The client machine can be a laptop with 16 GB of RAM while the server has 128 GB and the SSD.
Where it falls short: Not a browser client (yet). Requires a JetBrains subscription for the IDE side. The connection UI is more setup than VS Code Tunnels.
Pricing:
- Free: Gateway client is free; JetBrains IDE license is separate
- Paid: About $16/mo IntelliJ Ultimate, $9/mo other IDEs
Platforms: Windows, macOS, Linux client; Linux/macOS remote host
Download: JetBrains Gateway
Bottom line: Pick this if your team lives in JetBrains and you want to move heavy compile work off developer laptops.
6. GitHub Codespaces — Best GitHub-integrated cloud IDE
GitHub Codespaces spins up a preconfigured Ubuntu container per repository, opens it in vscode.dev or the desktop, and links workspace state to your GitHub identity. Every repo remembers its container shape, and the “.” keybinding on any GitHub file opens the same editor over the raw file.
The pricing model is per-hour rather than per-user, so it fits both solo work and team use. Two-core workspaces are typically fine for anything that is not a native compile.
Where it falls short: Cloud storage costs add up quietly. Codespaces on private repos are gated by the paid GitHub plans. Not a fit for offline coding.
Pricing:
- Free: 60 core-hours/month for personal accounts
- Paid: About $0.18/hr per 2-core, $0.36/hr per 4-core, plus storage
Platforms: Browser, VS Code desktop, JetBrains IDEs via plugin
Download: GitHub Codespaces
Bottom line: The easiest way to code from an iPad on a private repo. Watch the hour meter.
7. Zed collab — Best Rust-fast collaborative editor
Zed is the newer editor from ex-Atom engineers, built in Rust with pair-programming and hosted collaboration as first-class features. The collab feature lets one host share a project over Zed’s cloud with editing, cursor, and voice for anyone invited.
It is not a tunnel replacement per se. It is the answer when two developers want to sit in the same buffer without screen sharing and its typing lag.
Where it falls short: Younger extension ecosystem. Windows support is early. Only useful if both sides are on Zed.
Pricing:
- Free: Full editor and collab
- Paid: Zed Pro tier launched with AI features priced around $10/mo
Platforms: macOS, Linux, early Windows
Download: Zed
Bottom line: The right pick when the goal is real-time pair programming, not solo remote coding.
How to pick the right one
- If you want free browser access to your own desktop: VS Code Tunnels. Nothing to host, nothing to install, works today.
- If you refuse to touch Microsoft services: code-server. Own the whole stack.
- If you onboard new contributors weekly: Gitpod. Prebuilds eliminate the “why is my dev server not starting” first day.
- If your team is 20 or more people with real infra: Coder. Templated workspaces at scale.
- If you write Java, Kotlin, or Rust in JetBrains IDEs: JetBrains Gateway. Offload the compile.
- If you already pay GitHub and want zero-setup coding on private repos: GitHub Codespaces.
- If pair programming is the actual problem: Zed collab.
FAQ
Is VS Code Tunnels free?
Yes. VS Code Tunnels is a free feature of Visual Studio Code. Sign in with a GitHub or Microsoft account and turn on Remote Tunnel Access from the account menu or the command palette. Microsoft does not charge for the tunnel service.
What is the difference between VS Code Tunnels and Remote-SSH?
Remote-SSH connects the VS Code desktop client to a remote machine over SSH. VS Code Tunnels routes that same client-server split through Microsoft’s tunnel service so the browser at vscode.dev can reach the machine without SSH open on your router. Same architecture underneath, different transport.
Can I use these tools offline?
code-server on your own hardware works offline over a local network. VS Code Tunnels needs both endpoints to reach the tunnel service, so it does not work fully offline. Everything else in this list is cloud-hosted.
Do remote coding tools work with private GitHub repos?
Yes. VS Code Tunnels, code-server, Gitpod, Coder, JetBrains Gateway, and Codespaces all authenticate against GitHub and clone private repos with the same credentials.
Is code-server safe to expose to the internet?
Not on its own. Put code-server behind a reverse proxy with authentication (Caddy with Basic Auth, Cloudflare Access, or an SSO gateway), or route it through a mesh VPN like Tailscale so it only listens on the private interface.
What is the cheapest way to code from an iPad?
VS Code Tunnels to a home desktop is free and needs no extra hardware. If you do not own a desktop, GitHub Codespaces at $0.18/hour is the cheapest cloud option for casual use.
