exe.dev routes SSH without Host header

This is the kind of behind-the-scenes infrastructure work that makes a product feel effortless even when the underlying protocol makes that impossible. The clever part is not magic SSH behavior; it is accepting the constraint and engineering around it cleanly.

• –SSH cannot multiplex like HTTPS, so shared-IP VM hosting needs a different routing signal than a domain header.
• –exe.dev’s `{user, IP}` approach preserves the nice UX of `ssh hostname` without forcing users into custom ports or manual tunnels.
• –The tradeoff is real operational complexity: IP allocation, NAT handling, and proxy state become part of the platform’s core.
• –The post is a good reminder that polished developer products often depend on unsexy network plumbing done very carefully.
• –For users, the win is predictability; for operators, the cost is bespoke management software that likely won’t generalize well.