Developers

The GPU stays under the desk. Your dev workstation, from anywhere.

Reach the real Xcode, Android Studio, VS Code, JetBrains, Docker Desktop, and tmux session on your workstation from a MacBook Air, iPad Pro, or phone. Glass-to-glass around 8 ms on a wired LAN. No VPN, no web wrapper, no vendor lock-in.

Same three windows

The same three windows you opened this morning.

An SSH session for the long-lived host, a dev server with hot reload, and a container stack feeding the API. Remio streams them all to your laptop or tablet exactly as they appear on the workstation — no second editor, no browser-tab IDE, no port forwards to maintain.

Real Xcode. Real Cargo. Real Docker Desktop.

A Mac dev workstation streamed live through Remio

A day on the workstation, streamed to whatever you carry

SSH, hot reload, and the container stack all keep running on the host. Remio mirrors their windows to whatever screen you have with you.

workstation.local — zsh
~ $ ssh ngo@workstation.local
~ $ cd projects/remio && git status
On branch main — nothing to commit, working tree clean
~/projects/remio $ cargo build --release
Compiling remio v0.4.0 — Finished release [optimized] in 41.2s
~/projects/remio $ pnpm dev && docker compose up
▲ Vite ready on http://localhost:5173
✔ postgres · redis · api → listening on :8080

The build finishes on the host GPU. You watch it scroll at 60 fps on the iPad from the kitchen table.

Built for sub-frame keystrokes, not for video calls

The frame path is tuned so typing lands instantly and the CPU stays free for your build.

From keystroke to host process

Keystrokes and trackpad events ride a FlatBuffers data channel with no per-frame buffering. Modifier keys, shortcuts, and gestures forward natively — the host sees a real keyboard, not a virtual one.

Hardware encode, hardware decode

Frames are captured on the GPU and encoded by the hardware video encoder on Apple, NVIDIA, AMD, Intel, or Android silicon. The CPU stays free for your build, test suite, and IDE indexer.

VS Code with Remote-SSH

VS Code Remote-SSH keeps working because Remio does not touch SSH. Run both: Remote-SSH for plain editing on the road, then the streamed VS Code on the host when you need the GUI debugger or Live Share.

Xcode and JetBrains Gateway

SwiftUI previews, Instruments, the iOS Simulator, IntelliJ run configurations, Rider, GoLand, and PyCharm all render natively on the host — no display server tricks, no missing GPU features.

8 ms
Glass-to-glass, LAN, M2 Pro host
60 fps
Terminal scrolling, 120 Hz on M-series MacBook
Ops work too

The stack runs unchanged on the host

tmux, SSH, Docker, and kubectl live on your workstation. Remio just puts their windows on whatever screen you carry — the cluster stays behind your firewall.

tmux, SSH, and the shell

tmux sessions persist across reconnects exactly as they do over SSH. Detach, close your laptop, reconnect from a phone, and tmux attach drops you back into the running Cargo build, pnpm test watcher, or kubectl logs tail.

Docker Desktop and kubectl

Docker Desktop, Compose dashboards, and Kubernetes UIs run on the host as normal. Streamed logs scroll at 60 fps. CLI tools — docker, kubectl, helm — work over SSH or in the streamed terminal.

No VPN, no exposed ports

Remio's direct-P2P-first model means you do not open ports or maintain a VPN to reach your office workstation from home. A connection negotiates the path; an encrypted relay covers networks where direct P2P fails. All traffic is end-to-end encrypted.

Your CLI toolchains, unchanged

Cargo, go, bun, npm, pnpm, and Vite run on the host. The streamed terminal renders their output at 60 fps with full ANSI colour. Long compiles keep going if the client disconnects; reattach to view the trailing output.

Questions

Direct answers, no marketing detour

Can I forward SSH ports through Remio?
Yes. SSH runs unchanged on the host workstation. Remio streams the full desktop in parallel, so you can keep your existing SSH tunnels, port forwards, and tmux sessions open while also reaching the GUI tools that SSH cannot reach — Xcode previews, Docker Desktop, JetBrains run configurations.
Does Remio work with Docker Desktop and kubectl?
Yes. Docker Desktop runs on the host as normal and Remio streams its window. Container logs, the Compose dashboard, and the GUI all work. For pure CLI workflows, docker, docker compose, and kubectl continue to run over SSH or directly in the streamed terminal.
Will VS Code Remote-SSH work alongside Remio?
VS Code Remote-SSH continues to work because SSH is unaffected by Remio. Many developers run both — Remote-SSH from a laptop for text editing, then switch to the streamed VS Code on the host when they need the integrated debugger, Live Share, or extensions that need a real display.
Can I access tmux sessions from Remio?
Yes. tmux runs on the host and persists across reconnects exactly as it does over SSH. From the Remio session you can open a terminal, attach to a named tmux session, and pick up exactly where you left off — including long-running builds with Cargo, pnpm, or kubectl.
What is the input latency on a LAN?
Glass-to-glass latency is around 8 ms on a wired LAN with an M2 Pro host and an iPad Pro client. Terminal scrolling stays at 60 fps, and 120 Hz is supported on M-series MacBooks. WAN latency depends on the route to the host but typically stays below 40 ms over a direct peer-to-peer connection.
Remio app icon

Bring your workstation with you.

Install Remio Host on the workstation that has the GPU, the build cache, and the tmux session. Install the client on the device you carry. Pair once with a 4-digit code — the same Xcode, the same Cargo, the same Docker Desktop, now reachable from anywhere.

Free foreverNo VPNEnd-to-end encrypted