How Secure Tunnels Power Remote Access

When you access your local VS Code through MR Coder, your traffic never touches a relay server we operate. Instead, it flows through our global edge network of 300+ data centers. Here's how that works under the hood.

The Architecture

Our tunnels create an outbound-only connection from your machine to the edge network. No inbound ports need to be open on your firewall. The flow looks like this:

Browser (anywhere)
    ↓ HTTPS
Edge Network (nearest POP)
    ↓ Encrypted tunnel (QUIC/HTTP2)
Tunnel client (your machine)
    ↓ localhost
VS Code Server (local)

Why This Is Secure

Traditional port forwarding punches a hole in your firewall and exposes a service to the entire internet. Our tunnel architecture inverts this model:

• No open ports — The tunnel client initiates outbound connections only. Your firewall stays closed.
• TLS everywhere — Browser to edge is HTTPS. Edge to your machine uses an encrypted tunnel. No plaintext.
• Authentication proxy— MR Coder adds a session-based auth layer in front of VS Code. Even if someone knows your URL, they can't access your IDE without credentials.
• No relay servers— We don't operate middlebox servers. Traffic routes directly through the edge network to your machine.

Performance

An anycast edge network means your traffic is routed to the nearest data center. In practice, this means sub-50ms latency for most connections. WebSocket connections (which VS Code uses heavily) are kept alive through the tunnel, so keystrokes and file operations feel local.

What MR Coder Adds

Setting up a secure tunnel manually involves DNS routing, config files, and credential management. MR Coder automates all of this. One click in VS Code or the dashboard, and the tunnel is live with a custom subdomain, proper DNS records, and authentication — all managed through our API.

Want to try it? Get started in 2 minutes.