Termphin

Product Introduction

1. Definition: Termphin is a mobile SSH (Secure Shell) client and terminal emulator application for Android. It is a technical tool designed for remote server administration, development, and command-line interaction from a smartphone.
2. Core Value Proposition: Termphin exists to solve the fundamental problem of unreliable mobile SSH connections. Its primary value is providing persistent SSH sessions that survive network drops, screen locks, and network switching (e.g., from Wi-Fi to mobile data). This ensures that long-running processes, such as AI coding agent tasks, system monitoring with htop, or file edits in vim, are not interrupted when the mobile device's state changes.

Main Features

1. Persistent Session Management: Termphin deploys a small, open-source helper agent on the remote server via the initial SSH connection. This agent runs the user's shell (e.g., bash, zsh) as a child process. When the mobile client's connection is lost, the agent keeps the shell process alive. Upon reconnection, the client reattaches to the exact same shell session, preserving the working directory and any running foreground processes. This is distinct from simple TCP keep-alives and works through actual network interruptions.
2. Native Terminal Emulation: The terminal is rendered natively within the Android app, not within a WebView component. This ensures correct rendering of full-screen Terminal User Interfaces (TUIs), complex Unicode characters, and control sequences used by applications like vim, tmux, htop, and ncdu. Box-drawing characters, colors, and cursor positioning behave as they would on a desktop terminal.
3. Integrated SFTP Client & File Management: A built-in SFTP (SSH File Transfer Protocol) browser allows direct filesystem navigation on the remote server from within the same app tab as the terminal. It includes a syntax-highlighting text editor for remote files, image preview capabilities, and seamless file upload from the local device to the server, with the remote path automatically copied to the terminal prompt.
4. Local-Only Security Model: All sensitive data—including SSH private keys, connection profiles, and snippets—is stored exclusively on the mobile device. Data is encrypted at rest using the Android Keystore system and is further protected by an optional PIN or biometric (fingerprint) lock on the app itself. No keys or session data are ever transmitted to Termphin's servers; connections are established directly between the phone and the user's server.
5. Advanced SSH Functionality: The app supports modern SSH features such as ed25519 and RSA key generation and management, SSH agent forwarding, and port forwarding (local and remote tunnels). It also supports jump hosts (ProxyJump), allowing seamless connection to servers within private networks via a bastion host, with end-to-end encryption maintained to the final target.

Problems Solved

1. Pain Point: The fragility of mobile SSH sessions. Traditional mobile SSH clients terminate sessions upon network loss, screen lock, or app backgrounding, killing running processes and losing state.
2. Target Audience: System Administrators / DevOps Engineers needing emergency server access or monitoring from anywhere; Software Developers who wish to check deployments, run commands, or use AI coding agents (like Claude Code) from their phone; Security Professionals requiring secure, reliable remote access for audits or incident response.
3. Use Cases: Running long AI agent tasks where the process must continue after locking the phone; Emergency server troubleshooting while on a poor cellular connection; Quick file edits or config checks on a remote server without fearing a dropped connection will lose work; Monitoring server dashboards (e.g., using btop or nmtui) from a mobile device.

Unique Advantages

1. Differentiation: Unlike most mobile SSH clients (e.g., JuiceSSH, Termius) that only maintain sessions while the app is in the background on a stable network, Termphin's server-side agent ensures session persistence through physical network disruptions. Its native renderer provides superior TUI compatibility compared to web-view-based terminals. Its business model (free, no ads, no subscriptions) contrasts with freemium competitors.
2. Key Innovation: The server-resident reconnection agent is the core technical innovation. By moving session state management to the remote server, it decouples the mobile client's connectivity from the shell process's lifecycle. This approach, combined with a fully local/encrypted data vault, creates a uniquely resilient and secure mobile SSH experience.

Frequently Asked Questions (FAQ)

1. How does Termphin keep my SSH session alive compared to other apps? Termphin uses a two-layer approach. First, it maintains the TCP connection while the app is backgrounded. Second, and uniquely, it runs a small agent on your server that holds the shell process open. If the network connection fully drops, the shell continues running on the server. When you reconnect, Termphin reattaches to that existing process, unlike other apps that start a new session.
2. Is Termphin secure for managing production servers? Yes. Termphin employs a security-first model. Private keys are stored encrypted on your device only, never on external servers. It validates and remembers server host keys to prevent man-in-the-middle attacks. Support for jump hosts (ProxyJump) maintains end-to-end encryption. The app can be locked with a PIN or biometrics.
3. Can I use Termphin with AI coding assistants like Claude Code or GitHub Copilot? Absolutely. Termphin is ideal for AI coding agents that run in a terminal. Since the session persists on the server, a long-running agent task continues even if you lock your phone. The integrated SFTP client allows you to upload files directly to the server to provide context to the agent.
4. What happens if my server reboots while I'm disconnected? The persistent shell session running under Termphin's agent will be terminated. However, when you reconnect, Termphin will automatically start a new shell session in the same working directory you were in prior to disconnection. The state of the previous session (e.g., running foreground commands) is lost, but you are returned to the correct location.
5. Does Termphin support two-factor authentication (2FA) and password prompts? Yes. Termphin handles interactive prompts from the SSH server natively. If your server requires a TOTP code (Google Authenticator) or a PAM password, the prompt will appear in the Termphin terminal, and your input is sent directly to the server.