# How to Ship Code From Your Phone (2026 Setup) > Termius + Tailscale + Claude Code on a $5 VPS: the full phone-to-prod stack that indie makers use daily. Source: https://boringpush.com/blog/ship-code-from-phone ## Production only breaks when the laptop is closed Every founder knows the timing: the outage SMS arrives at dinner, on the train, at the playground. The laptop is home. What follows is either a frantic drive or a prayer that it can wait — because shipping from a phone on a normal codebase is genuinely reckless. Unchecked migrations, secret-less env files, deploys that need six dashboard clicks and a prayer: the phone didn't cause the fragility, it just exposed it at the worst moment. Meanwhile the other half of indie Twitter already lives there. [Pushing code from phones](https://x.com/jackfriks/status/2087270902761193846) "is only possible since agents handle massive context better now." [Can't believe I ship from my phone now](https://x.com/kentdebruin/status/2093336834004680815). [Coding features and closing tickets from the couch after dinner](https://x.com/jackfriks/status/2086964360824475776). And the one that started it: [half of all coding from a phone with Termius into Claude Code](https://x.com/levelsio/status/2008302286183842222). The difference between them and the frantic drive home isn't talent — it's a stack built for remote hands. ## The stack: four apps, one mesh, zero open ports **Termius** (iOS/Android) is the terminal: SSH keys in the secure enclave, snippets for the five commands you actually type (`pm2 logs`, `pm2 reload`, `git push production main`, rollback, status). **Tailscale** is the network: every device — phone, laptop, VPS — on a private WireGuard mesh with stable `100.x.y.z` addresses, so SSH works identically from anywhere and port 22 stays closed to the entire public internet. **Claude Code** runs on the VPS itself, where the warm production context and server RAM live. **Telegram or Discord** is the pager: plain-English incident pings with 1-tap fix buttons, so the phone tells you before users do. Setup is one evening, and most of it is waiting on install bars: ```bash # on the $5 VPS: private mesh + deploy target curl -fsSL https://tailscale.com/install.sh | sh sudo tailscale up --ssh sudo ufw delete allow OpenSSH # port 22: closed to the world sudo ufw allow in on tailscale0 # open only to your mesh ``` Add the phone to the same Tailscale account, connect Termius to the mesh IP, and the loop is live: prompt the agent, watch the gate run, push, get pinged. BoringPush ships every script for this — mesh setup, zero-downtime deploys, nightly backups — in a Next.js stack where phone sessions follow the same `AGENTS.md` guardrails as desktop ones. Ship from anywhere stops being a stunt the day the guardrails, not your presence, guarantee safety. ## The week-one playbook (steal this) - **Day 1:** mesh + Termius + one `pm2 status` from the couch. Feel the latency (it's fine). - **Day 2:** smallest real fix via phone prompt. Time it door to door. - **Day 3:** staged failure on a branch — watch the gate refuse it. Trust arrives here. - **Day 4+:** support tickets from the phone. Close one from a cafe and feel smug, legally. The honest limits: deep refactors still want a big screen and a quiet room, and reviewing a 40-file diff on glass is nobody's idea of fun — keep sessions small and the phone handles everything else. Review on laptop weekly, ship from anywhere daily. That split is exactly how the [couch shippers](https://x.com/jackfriks/status/2086964360824475776) describe their lives: laptop for architecture, phone for everything with a short diff. ## The three rules taped to the phone case Phone sessions fail in exactly three ways, so rule them out explicitly: 1. **Small diffs only.** If the change touches more than five files, it waits for the desk. The phone is for tickets, tweaks, copy, config, and single-feature pushes — the shape with nothing to misunderstand on a small screen. 2. **Gate always, no exceptions.** Never `--no-verify`, never skip lint "just this once," never push what the agent merely claims works. The gate is the senior dev looking over your shoulder; on the phone you need that shoulder more, not less. 3. **Rehearsed rollback.** The rollback command lives in Termius snippets next to deploy, tested on day three during the staged failure. Panic + unfamiliar command = outage. Panic + muscle memory = anecdote. ## FAQ ### iPhone or Android — does it matter? No. Termius and Tailscale both ship excellent iOS and Android apps. Pick the phone already in your pocket. ### Is SSH over Tailscale safe on public wifi? Safer than your home network: WireGuard encrypts everything, nothing inbound is exposed, and the VPS accepts SSH only from mesh members. Cafe wifi sees ciphertext. ### What breaks most often for beginners? SSH keys. Generate on the phone in Termius (not by pasting a laptop private key through notes apps), approve the Tailscale login once in a browser, then `ssh-copy-id`. Ten minutes, once. ### Can the whole team use one mesh? Yes — Tailscale teams with per-device ACLs. Give contractors the app boxes, never the database host, and revoke in one click when they leave. ### Do I still need a laptop at all? For architecture days, yes. For everything else — tickets, small features, deploys, rollbacks, invoice checks — the phone has quietly become enough.