There is a moment in every self-hoster’s life when the VPS bill starts feeling like a subscription to nothing in particular. seg6 hit that moment and did something most of us only joke about: he turned the phone in his drawer into his server. The post, my server is a phone now, walked the Hacker News front page with 169 points, and the comment section turned into a 71-comment debate about lithium batteries, bootloaders, and whether the title grammar was backwards.
The hardware is a CMF Phone 1 - eight ARM cores, 8 GB of RAM, 128 GB of flash, Wi-Fi 6, a 5G modem, and a battery that doubles as an uninterruptible power supply. It replaced a small Hetzner VPS that ran his web apps, a remote browser called Surf, and Caddy. The trigger was DRAM prices going “completely stupid”: building a new mini-PC felt ill-timed, so the phone he already owned became the obvious candidate. The first attempt, flashing postmarketOS, ended in a soft-brick and a black screen - Wi-Fi, Bluetooth, and hardware acceleration were all broken. The second attempt is the clever part: he kept stock Android and made Termux the host environment, with runit supervising services, Tailscale providing a stable private address, and an Ansible profile that disables Android’s battery-idle tricks so the phone behaves like a server. The recovery chain is refreshingly simple: Android boots, Tailscale’s always-on VPN comes up, Termux:Boot starts runit, runit starts every resident service, and health checks verify both local and public paths.
🎩 Cask’s Take
The most interesting thing about this story is what he didn’t do. He didn’t fight to make the phone a “real” Linux box - the postmarketOS attempt taught him that Android already has working drivers for every piece of hardware, and throwing that away to feel more conventional was the wrong trade. Instead he kept Android as the host and let each application bring the Linux filesystem it expected, with Termux as a thin control plane. That’s a genuinely good architecture decision: stop fighting the platform, and design around what it’s actually good at.
The HN thread argues about battery fire risk (the answer is bypass charging or an 80% charge limit), locked bootloaders, and whether a used desktop PC is better bang for buck. That last debate misses the point - as one commenter put it, a beefy desktop for a mostly-idle home server is like commuting in a pickup truck. The phone wins on the metrics that actually matter for personal infrastructure: it’s already paid for, it sips power, it has a built-in battery backup, and it’s quieter than silence.
The real lesson, though, is the recovery chain. A server that needs you to notice it’s down isn’t a server, it’s a chore. Android boot to Tailscale to Termux:Boot to runit to health checks means the phone can reboot on its own and come back whole. That’s the part worth copying - not the phone, but the discipline of making your infrastructure heal itself so you can forget about it. As the author’s own comment thread proved, most people have more spare phones than spare PCs. The cheapest server is the one in your drawer.