About SSH Ache Teams

SSH Ache started as a fast, native SSH client for people who live in the terminal. SSH Ache Teams extends it into something teams have always wanted but rarely get: a way to share SSH access without ever sharing the secrets in plaintext.

Why we built it

Sharing SSH keys and passwords over chat, wikis, and shared password managers is how credentials leak. The usual "team" tools fix the workflow but still decrypt your secrets on their servers — so a breach on their side is a breach on yours. We thought that was backwards.

Our approach

Everything is end-to-end encrypted with standard, widely-reviewed primitives — X25519, Ed25519, XChaCha20-Poly1305 and Argon2id — assembled into a wire format that is frozen and covered by known-answer tests shared between the web, desktop and mobile clients. Keys are derived and held on your own devices; our servers only ever store ciphertext and wrapped keys. We designed the system so that we cannot read your secrets even if we wanted to — zero-knowledge is the architecture, not a checkbox. To be straight with you: the design has not yet had a third-party audit. The security model is published in full so you can judge it yourself, and an external review is on the roadmap.

Open at the core

The community edition is open source under Apache-2.0 — the individual-use build, free forever, and free to use commercially with no permission. The Teams client is source-available under PolyForm Noncommercial and builds on the same frozen, reviewed encryption wire format — free for noncommercial use, with a paid commercial licence for business use. You can read either one before you trust it.