Porta has shipped its first stable release, 1.0.0, an AGPL-3.0 open-source SSH client that keeps hosts, identities and keys in an encrypted vault behind a single master passphrase. It offers a terminal UI and a desktop app driven by the same core, plus an Android app, and syncs devices through a Git repository the user owns that only ever receives ciphertext. The release landed on GitLab on November 10, 2026, and the project says it ships with no telemetry.
Porta 1.0 in 20 seconds
- Free AGPL-3.0 SSH client with a terminal UI, a desktop app and an Android app.
- The vault uses Argon2id and XChaCha20-Poly1305; generated keys never hit the disk in plaintext.
- Sync goes through your own Git repository, which only sees ciphertext.
- SFTP, port forwarding, ProxyJump and hybrid post-quantum key exchange are included.
The project, created in July 2026 and hosted on GitLab under the Porta-SSH group, enters a space shared by free clients and commercial services that sync connections through their own cloud. Its pitch is the opposite: secrets stay on the machine, and if you want sync, you bring the repository and Porta only pushes records that are already encrypted.
A local vault and sync that does not trust the server
According to its documentation, the master passphrase is stretched with Argon2id into a key that seals every secret with XChaCha20-Poly1305. The passphrase is never stored, so there is no recovery path: lose it and you lose the vault, while anyone holding the disk or the sync remote cannot read a key or password without it. Ed25519 keys generated by Porta are written straight into the vault, never to a plaintext file, and existing OpenSSH keys can be imported. Version 1.0 also supports rotating the master passphrase, re-encrypting every secret in place.
Sync relies on a Git repository you own. Every record (host, identity or key) is encrypted with the vault key before it leaves the device. Conflicts resolve last-writer-wins per entity, and deletions replicate as tombstones. On the first device the command seeds the remote; on the others it adopts the remote’s key-derivation parameters, so unlocking with the same passphrase is enough:
porta # open the terminal UI
porta import # import hosts from ~/.ssh/config
porta join [email protected]:you/porta-sync.git # sync through a remote you ownCode language: PHP (php)
After that, Porta syncs on unlock, when it returns to the foreground and shortly after each change. The repository can be a private one on GitLab, GitHub or a self-hosted Gitea; the server only stores encrypted files.
Features for day-to-day admin work
- Post-quantum key exchange: connections negotiate the hybrid
mlkem768x25519-sha256, combining ML-KEM with X25519, when the server supports it. - Host key pinning: host keys are pinned on first use, and a later mismatch always fails the connection.
- Jump hosts and folders: ProxyJump chains with every hop’s host key verified, nestable folders with icons and colors, and fuzzy search by name, address, user or folder.
- Tunnels: local and remote port forwarding declared per host in ssh notation.
- SFTP: a file browser to upload, download, create and delete, with cancelable transfers.
- 2FA and PAM: keyboard-interactive challenges answered in either frontend, at every hop.
- Key install: pushes a public key to a host’s
authorized_keys, the wayssh-copy-iddoes. - Autofill: detects password prompts and injects a chosen secret.
The terminal UI uses single-key shortcuts: enter to connect, / to search, f to browse a host over SFTP, K to manage keys and s to sync. The desktop app renders the same core with Wails, Svelte and xterm.js, with sessions as tabs and native file dialogs.
Installation and caveats
Binaries are on the GitLab releases page: porta for the Linux terminal (make it executable and move it to ~/.local/bin/), porta.exe for the Windows terminal, porta-gui for the Linux desktop, which needs GTK3 and WebKit2GTK, a Windows installer and an APK for arm64 Android devices. Both apps flag when a newer release is out.
Keep in mind this is a young project with a single release and no announced third-party security audit. Claims about its encryption model come from its own documentation, which spells out what is encrypted, what is not and what a sync remote can observe. Before trusting it with production keys, try it against lab hosts, review that security model and store the master passphrase in a password manager, because there is no way to recover it.
Frequently asked questions
What is Porta?
An AGPL-3.0 open-source SSH client with a terminal UI, a desktop app and an Android app that stores credentials in an encrypted vault.
How does Porta sync between devices?
Through a Git repository you own. Every record is encrypted before it leaves the device, so the server only sees ciphertext.
What happens if I forget the master passphrase?
It cannot be recovered: the passphrase is never stored, so the vault cannot be opened without it.
Sources:
