Build a browser-based RDP client with grdpwasm

If you’ve ever needed to jump into a Windows machine from a locked-down environment, you know the pain of installing proprietary RDP clients. Most IT environments block non-standard ports or forbid third-party software entirely. That’s where grdpwasm changes the game. By leveraging Go and WebAssembly, it allows you to run a full-featured RDP client directly inside your browser.

The core challenge with browser-based remote desktop tools is the sandbox. Browsers simply cannot open raw TCP sockets, which is the native language of the RDP protocol. To get around this, grdpwasm uses a clever architectural bridge. You run a lightweight Go proxy that acts as a translator, converting WebSocket traffic from your browser into standard TCP packets that the Windows host can understand.

How to deploy your own RDP bridge

Getting this running is straightforward if you’re comfortable with the Go toolchain. First, ensure you have Go 1.24 or later installed. Clone the repository and run make all. This generates your main.wasm binary and the necessary wasm_exec.js runtime.

Once built, the proxy server handles both the static file serving and the WebSocket-to-TCP bridging. You can launch it with make serve. Here is the part most people miss: the proxy is essentially a transparent pipe. If you are planning to expose this to the internet, you must put it behind a TLS-terminating reverse proxy like Nginx or Caddy. Sending RDP credentials over an unencrypted WebSocket is a recipe for disaster.

Why this approach beats native clients

Most guides get this wrong by suggesting you need complex gateway software. With grdpwasm, you get a clean, plugin-free experience. It supports standard keyboard scan codes and mouse input, and it even handles remote audio via the Web Audio API.

Here are the specific advantages of this setup:

1. Zero-install: Your users don't need to download or update client software.
2. Cross-platform: It works on any device with a modern browser, including Chromebooks or locked-down kiosks.
3. Lightweight: The Go proxy is minimal, making it easy to containerize and deploy in a sidecar pattern.

That said, there’s a catch. Because the browser tab must maintain focus to capture keyboard events, you’ll occasionally find that keys stop responding if you click outside the canvas. If that happens, just click back into the remote desktop area to re-establish focus. It’s a minor quirk of the browser security model, but it’s something you’ll want to warn your users about.

Security considerations for production

If you are deploying this in a corporate environment, don't just run the proxy and call it a day. The default configuration accepts connections from any origin. You should implement an authentication layer in front of the proxy or restrict access via a VPN.

How do you handle secure remote access in your current stack? If you're tired of managing client-side software, building a custom RDP gateway using Go and WebAssembly is a robust alternative. Try this today and share what you find in the comments.