Create a company account to bring your team onto one plan.
Invite members by email, manage who can do what, and handle billing and seats
from a single place, without ever sharing plaintext.
The person on call opens the session that is already mid-problem, from whatever screen is closest. No screen share, no credential paste, no "what did you try already".
Create it from your phone and choose the team. The vault key is generated on that device and only ever stored sealed; the people you invite get it wrapped to their own key.
09:41●●● ⏻
new vault
Members you invite get the vault key wrapped to their own public key. You can add and remove them afterwards.
A key is generated on this device and stored only sealed to your
account key: the server never sees it.
Move a host into the team vault.
Connections live in named vaults: Personal, Production, one per client. A shared vault is wrapped to each member's own key, so moving a host into it is sharing it.
termuna
termuna: ssh
sshesc
ssh connections
6 connections synced · keys are sealed on this device.
personal2 hosts · private
nova-labnova@nova-lab:22
bastionnova@bastion.novalabs.dev:2222
grafanadeploy@grafana.novalabs.dev:22move to vault · nova labs
nova labs3 hosts · shared with 2
relay eu-centraldeploy@relay.novalabs.dev:22
k8s-prodops@k8s.novalabs.dev:22
grafanadeploy@grafana.novalabs.dev:22wrapped to mira's and jon's keys
aurora · ~/dev/aurorakey→glyph 6.2 ms87 MBe2e
The right people have it a moment later.
Every host is encrypted on a device before it is uploaded. Our server syncs hosts it cannot read, and your teammate's machine decrypts them.
termuna
termuna: ssh
sshesc
ssh connections
5 connections synced · 1 new from the cloud · keys are sealed on this device.
personal1 host · private
mira-pimira@192.168.1.24:22
nova labs3 hosts · shared with 2
relay eu-centraldeploy@relay.novalabs.dev:22
k8s-prodops@k8s.novalabs.dev:22
grafanadeploy@grafana.novalabs.dev:22decrypted on this device · from nova
aurora · ~/dev/aurorakey→glyph 6.2 ms87 MBe2e
Read-only, precisely.
A vault you only read: connect and clone, never edit. The owner's changes reach you; nothing you do changes theirs.
09:41●●● ⏻
hosts
personal2· private
nova labs3· shared
staging-shared1· shared · read-only
A vault you only read: connect and clone, never edit. Its owner's changes reach you, yours cannot reach it.
09:41●●● ⏻
Connected to nova@lab.novalabs.dev.
nova@lab:~$ uptime
09:41:12 up 41 days, load average: 0.12
nova@lab:~$
What our server holds.
Hosts, users, keys and passwords are sealed on a device before they leave it. We store the ciphertext, its size and each member's wrapped key: nothing anyone could connect with.
what our server stores · vault nova labs
item 7f3a02 9f 3a c1 7e 44 b0 d2 61 0c 8a f5 3e 91 27 cc412 B
item 91c202 5b e8 14 a0 76 d9 03 4f 1d 88 c4 2e 70 b9 5a388 B
item e04d02 c3 11 fa 9d 62 07 b8 e5 3a 4c 90 d7 26 5f 81401 B
wrap mira02 8e 44 0a 71 c9 3d f2 16 ab 5e 07 94 c8 21 6b96 B
no hostname, no user, no key, no password
09:41●●● ⏻
hosts
nova labs3· shared
Opened with mira's own key, on this phone.
One roster, three roles.
Invite by email, assign a role, share the
vaults. Every member holds the vault keys wrapped to their own key,
and nothing else.
Day one is three grants. Owners hold billing and the organization, admins invite and remove, members use the team's plan. Seats and the invoice follow by themselves.
team · nova labs4 seats · one invoice
novaownerBilling, seats, and the organization itself.key wrapped
miraadminInvites and removes members, manages settings.key wrapped
jonmemberUses the product with the team's plan.key wrapped
anamemberInvited by email just now. The shared vaults follow.key wrapped
Hand the company over.
Ownership moves in one step, so the organization is never without an owner. The old owner stays on as an admin, with the seat and the access they had.
team · nova labs4 seats · one invoice
novaadminHanded the company over. Keeps the seat and the access.key wrapped
miraownerBilling, seats, and the organization itself.key wrapped
jonmemberUses the product with the team's plan.key wrapped
anamemberUses the product with the team's plan.key wrapped
orgownerMoved in one step: never a moment without an owner.transferred
Offboarding is one removal.
Their wraps are deleted and they stop receiving changes. Rotating a credential afterwards is one vault update, not an every-machine scramble.
team · nova labs3 seats · one invoice
novaownerBilling, seats, and the organization itself.key wrapped
miraadminInvites and removes members, manages settings.key wrapped
jonmemberUses the product with the team's plan.key wrapped
leoremovedRemoved just now. His wraps were deleted.no access
k8s-prodvaultNew key, one vault update: nova, mira and jon have it.rotated
Security your security team will accept
Everything in Termuna Cloud stays end to end encrypted, including for
teams. The relay never holds keys and never sees plaintext, whether it is a
live session or a shared connection.
Read the security model.
On the way: single sign-on through SAML and OIDC, and a
team audit trail surfaced in the dashboard. Want these for your team?
Tell us what you need.