Roadmap

After updating SSHive, a small number of users see the app go back to the Free tier even though they bought Pro. The cause sits in the StoreKit receipt refresh path during the first launch after update. The workaround today is one tap: Settings, Subscription / Purchases, "Restore Purchases", and Pro comes right back. A permanent fix is being worked on so the restore is not needed anymore. If this happens to you and the restore does not fix it, write to contact@netmesafe.com with your App Store country and the time you upgraded, and we will check the receipt on our side.

Today, profiles created on your Mac stay on your Mac, profiles on iPhone stay on iPhone, and you exchange them with the .sshive JSON export. The next step is opt-in iCloud sync via CloudKit so that adding a host on your Mac shows up on your iPhone within seconds, with the same tags, notes and jump-host chain. We will not sync the secrets themselves. Passwords, SSH passphrases and private keys stay on each device, in the per-device Keychain. iCloud will only carry the host, port, username, tags, notes and tunnel definitions, so the security model does not change. You will be able to turn the sync off per device, and we will document exactly what fields move across.

For teams that already use a YubiKey 5 NFC for SSH, the missing piece on iPhone is reading the key through the iPhone Core NFC stack and using it as the SSH agent. The plan is to support FIDO2/PIV-backed SSH keys (`ssh-ed25519-sk`, `ecdsa-sk`) so an iPhone can authenticate to a server that requires a hardware key, with a Face ID confirmation on the SSHive side and an NFC tap on the YubiKey. This closes a gap where iPhone is currently the weak link in 2FA SSH policies. iPad keeps Lightning / USB-C YubiKeys via the USB-C port; Mac already uses the YubiKey through SSHive's normal agent integration.

Mosh is the resilient mobile shell that survives Wi-Fi switching, 5G handoffs and the phone going to sleep, instead of dropping the SSH session every time. On a desk that does not matter much, but on a train going through tunnels with a long-running `tail -f` open, it changes the experience. We are looking at adding Mosh as an alternative transport on top of an SSH bootstrap (the standard `mosh-server` pattern). The blocker is that Mosh needs `mosh-server` installed on the remote side, which is not universal. We are also evaluating whether a SSHive-side resume scheme could give you 80 percent of what Mosh provides without requiring server changes. Tell us which you would prefer.

iPad Pro with a Magic Keyboard is close to a real laptop, but the current SSHive iPad layout still treats the window as a single workspace. The plan is to support real multi-window: open the prod SSH session in one Stage Manager window, the staging RDP in another, an SFTP browser in a third, all alongside Notes or Safari. Drag-and-drop between SSHive windows for SFTP transfers, native Magic Keyboard shortcuts (Cmd+T for new tab, Cmd+W to close, Cmd+1..9 to switch). The goal is that an iPad Pro with Magic Keyboard becomes a comfortable primary workstation for remote work, not just a backup device.