Everything Shely does

Saved connections

Keep the hosts you use in one place and reopen them in a click. No retyping addresses, no hunting for the right key, no scattered notes.

Reopen in a click

A saved connection carries what it needs to start a session, so getting back into a server is a single action rather than a small ritual.

A real live terminal

Not a shell emulator. A genuine SSH session, rendered in the browser.

The gateway path

Your keystrokes travel over a dedicated WebSocket gateway speaking shely.terminal.v1, and xterm.js draws the terminal. It behaves like the terminal you already know.

Reconnects that resume

When your network drops, a reconnect resumes the session where it was instead of starting over, so a flaky connection does not cost you your place.

Dual-pane SFTP

Move files without leaving the browser.

Upload and download

A two-pane view puts your local side and the remote side next to each other, so uploads and downloads are a matter of moving between them.

Inline editor

Edit a remote file in place with the inline editor when a full round trip to a local copy would be more work than the change is worth.

Session recording

Keep an encrypted record for its configured administrator recipients.

Sealed per administrator

The gateway seals each recording to your organisation’s admins and then discards the ordinary playback key. The gateway still handles readable session data while recording. Redaction can miss secrets in commands or output.

End-to-end encrypted vault

Your keys and keychain items are encrypted with a key we never hold.

Two independent keys

Your account password never leaves your device. It derives two independent keys: one proves who you are to the server, the other opens your vault. The server only ever sees the first. A password you save for a server is different: we encrypt it and keep it so Shely can connect for you, which means our gateway can decrypt it. A private key used for a browser connection can also reach the gateway for authentication. Encryption of stored vault contents does not hide every credential used in a connection. The security page explains which is which.

Teams

Work together on shared servers without ever passing a secret around.

Create or join a team, invite by email

Any user can create a team or join one. Founders and admins invite members by email, and every team has three roles: founder, admin and member.

Shared servers, revealed by role

Members can connect to a shared server without being told its password. We keep that password encrypted on our gateway, and only admins and above can reveal it, which keeps a share from becoming a secret pasted into a chat window. SSH keys are not shared with a team yet.

Personal and team views without dropping sessions

Switch between your personal connections and a team view without ending a live session. If you belong to more than one team, a picker remembers the last team you were in and puts you back there.

Two-factor authentication and passkeys

Protect the account itself, not just the vault.

2FA and passkey sign-in

The account service supports two factor authentication and passkeys. Use the supported controls in settings; availability differs by platform and app version. These protect account access, not every risk on a connected server.