Cloud continuity
The session outlives the screen.
Turn on sync and your work follows you. Every tab, every split, and the full scrollback mirror to Termuna Cloud as they happen, encrypted end to end. The relay stores ciphertext it cannot read.
How it works
A small daemon on your machine owns your shells and the authoritative session tree. When sync is on, it attaches your live sessions to Termuna Cloud as an encrypted host. Your dashboard lists every live session, and opening one in a browser or on your phone types into the very same shell, still running on your machine.
1. Runs on your machine
The daemon owns the real shells, where your code, keys, and tools already are.
2. Mirrors as it happens
Frames are sealed and streamed to the relay. Viewers subscribe and decrypt locally.
3. Continues anywhere
Open the same session from any browser or phone and keep typing.
What survives
Close the laptop, switch to your phone, then reboot the machine. Nothing is lost. History stays in the cloud, and the desktop app resurrects the whole layout, including tabs, splits, and working directories, into fresh shells with a single click. Read the deep dive on what honestly survives a reboot.
The relay never sees plaintext
This is the part that matters. Session keys are generated on your devices and never leave them unwrapped. Every frame is sealed with XChaCha20-Poly1305 before it touches the network, using a random nonce per message. The server relays and stores only ciphertext. We could not read your scrollback if we tried, and we built it that way on purpose.
Keys live in the share link, not on our servers. When you open a session in a browser, the decryption key travels in the link's URL fragment, which never reaches the server. That browser remembers the key locally so you only paste the link once. Read the full security model.
Your connections travel too
Sync is not only for live sessions. Save an SSH connection once and it follows you to your other computers, organized in encrypted vaults. Share a vault with a teammate, a few people, or the whole team, and onboarding becomes granting access instead of a credential handoff. Every connection is encrypted on your device with a passphrase that never leaves it, so the relay stores only ciphertext and public keys, never a host, a password, or a key.
On your phone
The web viewer is built for touch. It has a soft-key row for Esc, Tab, Ctrl, arrows, and common symbols, a keyboard-aware layout, and installs to your home screen as an app. You can open new tabs, split panes, and rename tabs from the phone, driving the same session that runs on your desktop. Read the deep dive on phone access.
Machines with no screen
Continuity is not only for the machine in front of you. Install the headless daemon on a server and it joins your account, appears in every client's device list, and hosts sessions on demand - even freshly rebooted, even with nothing running on it. The daemon dials out to the relay, so the box needs no open port and no jump host, and can sit behind NAT or a VPN while your phone opens a shell on it. Set it up in minutes.
Opt in, and export anything
- No account is required for local use. Sync is opt-in, and off by default.
- Full export of everything, at every tier, always.
- End to end encrypted. The server never holds keys.
- A recovery kit means a forgotten password never means lost history.
Try continuity free with one live session. Upgrade when you need more. See the plans.
Questions people ask
What happens if I close my laptop or lose the network?
Your Termuna session keeps running on your machine, where the daemon owns the real shells. Sync mirrors it to the cloud as it happens, so you can pick it up from the web or your phone and keep typing into the same shell.
Can I resume a session after a reboot?
Yes. History stays in Termuna Cloud, and the desktop app resurrects the whole layout, including tabs, splits, and working directories, into fresh shells with a single click.
Can Termuna read my synced sessions?
No. Termuna generates session keys on your devices and they never leave them unwrapped. Every frame is sealed with XChaCha20-Poly1305 before it touches the network, so the relay stores only ciphertext it cannot read.
Does a server need an open port or a jump host?
No. A server runs the headless Termuna daemon, which connects outbound to the relay over an encrypted WebSocket. The machine stays behind NAT, a firewall, or a VPN, and still answers from any signed-in device: no inbound port, no bastion, no jump chain.
Is sync on by default?
No. The local Termuna terminal needs no account and makes no network calls until you turn sync on. Sync is opt-in, and everything you sync can be exported, at every tier, always.