BoostSSH

REMOTE ACCESS · ANDROID 16+

Your servers.
Your clusters.

SSH and Mosh terminals, Kubernetes management, and encrypted connection backups. Work with servers and clusters from your Android device.

Google Play testing

Currently available to invited Google Play testers. Public availability is subject to Google Play review and production access.

REMOTE SESSION

$ ssh ops@server.example

Connected over SSH.

ops@server:~ $ uptime

up 42 days, load average: 0.08

ops@server:~ $ ▌

Illustrative terminal output

A TOOLBOX FOR YOUR CONNECTIONS

01

Connect and work

SSH and Mosh sessions, port forwarding, reusable identities, connection groups, and terminal settings. Telnet and a local shell are also available.

02

Manage Kubernetes

Import kubeconfig contexts, browse cluster resources, follow container logs, open pod terminals and review YAML changes. Manage Helm releases and supported Argo CD and Flux resources.

03

Keep an encrypted backup

Optionally back up and sync SSH connections through your own Google Drive account. Personal backups use Drive’s private application storage and are encrypted on your device before upload.

04

Share a collection

Give a team access to selected SSH connections using Google Drive permissions and a separately shared collection code. Keep personal connections separate.

KUBERNETES

From cluster overview
to container shell.

Switch contexts and namespaces, discover resources including custom resources, inspect health and events, stream logs, transfer container files and forward Pod or Service ports.

Validate manifests, preview changes with server dry-run, and apply YAML. Scale and restart workloads, manage rollouts, and use node maintenance tools. Work with Helm releases, Argo CD applications and Flux reconciliation when the corresponding APIs are available.

Cluster actions follow your Kubernetes permissions. Connect directly or through a saved SSH route. Kubernetes profiles, credentials and drafts are encrypted locally and stay on the device; they are excluded from Google Drive sync, shared collections and SSH backup files.

YOUR DATA

No developer account.
No developer analytics.

Your saved connections and credentials are managed on your device. The developer does not receive your connection database, terminal sessions, or backup decryption keys. Google Drive is optional; local encrypted backup files work without it.

Google and the servers you choose have their own data practices. Read how backups, sharing and recovery work in our privacy policy.