Skip to Content
Use CasesRemote Development

Remote Development

You develop on a powerful desktop at home but sometimes work from a laptop — or you have a cloud build machine you want to SSH into without exposing it to the internet.

The problem

Exposing SSH on a public IP means constant brute-force traffic and one more attack surface to harden. Bastion hosts and jump boxes work but add moving parts, and SSH keys scattered across laptops, CI, and phones are hard to rotate.

How Rabtly helps

  • SSH from anywhere — reach your desktop or cloud server by its private Rabtly IP, with nothing listening on the public internet.
  • Remote IDEs just work — VS Code Remote-SSH, JetBrains Gateway, and mosh all run over the Rabtly tunnel unchanged.
  • One identity, not scattered keys — devices join your network once; remove a lost laptop from the dashboard and its access is gone.

How it works

Install Rabtly on both machines

Put the daemon on your dev machine (the one you SSH into) and your laptop (the one you connect from).

Connect over the private IP

ssh you@<dev-machine> using its Rabtly IP or MagicDNS name. No port forwarding, no bastion.

Point your IDE at the same host

In VS Code Remote-SSH or JetBrains Gateway, use the same Rabtly hostname. The editor tunnels over Rabtly automatically.

Next steps