termuna

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.

It runs on your machine.
It follows you.

Your code, keys and tools stay where they are. Continuity is the same session, seen from another screen.

Every live session, on every screen.

A small daemon on your machine owns the real shells. With sync on, it attaches your live sessions to Termuna Cloud as an encrypted host, and every signed-in screen lists them.

Keep typing into the same shell.

Open one on your phone or in a browser and you are typing into the very shell still running on your machine: same tabs, same splits, same scrollback.

What survives.

Close the laptop, switch to your phone, then reboot the machine. Nothing is lost.

What honestly survives a reboot

Reboot, and nothing is lost.Solo

History stays in the cloud, sealed. Open the layout after a reboot and the dormant session comes back as it was: tabs, splits, directories and scrollback.

A line where you stopped reading.Solo

Each device remembers where you stopped, and the position travels with your account. Come back and the screen shows that line and a count of what ran while you were away.

Keep a working set.

Save the live session as a named layout: what the panes are, never what they printed. Ctrl+K opens it on any machine that opens your vault.

The relay never sees plaintext.

This is the part that matters. We could not read your scrollback if we tried, and we built it that way on purpose.

Read the full security model

The relay stores frames it cannot read.

Session keys are generated on your devices and never leave them unwrapped. Every frame is sealed with XChaCha20-Poly1305, a fresh nonce each, before it touches the network.

Your connections travel too.

Save an SSH connection once and it follows you to your other computers, in encrypted vaults. Share a vault and onboarding becomes granting access instead of a credential handoff.

Save a host once.Solo

Add it on one computer and it is on all of them. It is encrypted on the device before it leaves, so what syncs is a sealed item our server cannot open.

Share by moving it into a team vault.Team

A shared vault is wrapped to each member's own key. Move a host into it and the right people have it a moment later; nobody pastes a credential into a chat.

Machines with no screen.

Install the headless daemon on a server and it joins your account and hosts sessions on demand, even freshly rebooted, even with nothing running on it.

Set it up in minutes

Servers join without a screen.

termuna-daemon is the same engine without a window. Log in once on a box and it dials out: no open port, no jump host, fine behind NAT or a VPN. Its sessions sit in your drawer beside your laptop's.

Start a session from your phone.Solo

A signed-in machine stays reachable with nothing running. Pick it on your phone and open a shell on it, from the couch.

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.

Create a cloud account