# SSH into your servers from your phone: keys, Tailscale, and an AI safety net > Source: > Published: 2026-08-17 01:48:50+00:00 Every on-call engineer has lived this: an alert fires, you're not at your desk, and all you have is your phone. The laptop-and-VPN scramble takes ten minutes you don't have. Here's a setup that lets you actually fix things from a phone — safely. You want an SSH/SFTP client that behaves like a terminal. On iOS/Android the usual names are **Termius**, **Blink Shell**, **Termux**, and **TermAI**. Whichever you pick, make sure it supports: Password auth on an internet-facing box is asking for trouble. Generate an ed25519 key: ``` ssh-keygen -t ed25519 -C "phone" ``` Put the public key in the server's `~/.ssh/authorized_keys` , import the **private** key into your mobile client's key store, then turn password auth off in `sshd_config` : ``` PasswordAuthentication no ``` Most of your boxes shouldn't expose SSH to the internet at all. Instead of port-forwarding, put them on a mesh VPN like **Tailscale** — your phone joins the tailnet and you SSH straight to the private IP. Some mobile clients ship Tailscale built in, which saves you juggling two apps and a login. Typing `systemctl restart` against the wrong host, on a phone keyboard, half-awake, is a real failure mode. This is where an AI **assistant** earns its keep — but the *mode* is everything. You want **suggest-then-confirm** (the tool proposes a command, you read it, then you run it), not an autonomous agent that executes on its own. On a production box, "read before you run" is the whole game. Phone-based ops isn't about replacing your laptop. It's about the five minutes that stop a small incident from becoming a big one. **Keys + a mesh VPN + a suggest-then-confirm assistant** is a setup you can actually trust while you're on call. *Disclosure: I build TermAI, a mobile SSH terminal that bundles SFTP, built-in Tailscale, and a suggest-then-confirm AI assistant — but the setup above works with whatever client you prefer.*