A browser-based SSH client
A browser-based SSH client moves the terminal off the machine in front of you and into your account. Nothing to install, nothing to configure twice, and the same saved hosts wherever you sign in.
Why run SSH in a browser at all?
The traditional model assumes the computer is yours: you install a client, save your hosts on it, and put your keys in its config. That assumption breaks constantly — a work laptop you cannot install software on, a shared machine, a rebuilt desktop, a borrowed computer at a client site, a Chromebook, a tablet on a train.
Running the client as a web application removes the assumption. The browser is already installed, your host list lives in your account, and a machine you have never touched is one login away from your servers.
- No installer, no admin rights, no per-machine setup
- Saved connections and preferences follow your account, not the hardware
- Works the same on Windows, macOS, Linux, ChromeOS and tablets
- Nothing sensitive left behind on a machine you borrowed
What you actually get
A web terminal is only useful if it behaves like a real one. NebulaSSH runs multi-tab sessions with full colour, password and private-key authentication, per-user font and scrollback preferences, and live CPU, memory and uptime for the host beside the shell.
- Multi-tab sessions with saved connections and import/export
- Password and standard OpenSSH private-key authentication
- An SFTP file manager in the same tab, with drag-and-drop uploads
- VNC remote desktop when a shell is not enough
- Command macros you can fire at a group of machines at once
Getting a shell in about a minute
For a host you can already reach, add the connection and open it — the same details you would type into any SSH client. For a machine behind NAT or a firewall, install a connector agent on it instead and claim it with a one-time enrollment token; the agent dials out, so nothing inbound needs opening.
Common questions
Is a browser SSH client secure?
Sessions are encrypted end to end and accounts use hashed credentials with per-user API keys and one-time enrollment tokens for agents. The practical security gain is that no keys or saved hosts are left behind on a shared or borrowed machine.
Do I need to install anything at all?
Not to connect to a host you can already reach. You only install something — the connector agent — when the target machine is behind NAT or a firewall and cannot accept an inbound connection.
Will it work on a Chromebook or a tablet?
Yes. Anything with a modern browser gets the same terminal, including ChromeOS, iPads and Android tablets.
Can I use my existing SSH keys?
Yes, standard OpenSSH keys. If your key is in PuTTY's .ppk format, export it to OpenSSH format from PuTTYgen first.
Try it on a machine you are sitting at
Open a browser, sign in, add a server. Nothing to install — and nothing left behind if the machine is not yours.