No, it is extra-super complex infrastructure for a fairly simple thing.

Normal SSH still works, and is usually going to be what people end up using. You just have to have WireGuard installed and running.

The product feature here is less interesting than how we did it.

Please keep writing about WireGuard. If it wasn't already magical enough for its stated purpose (VPN), maybe the "truly" interesting thing is how it can enable tech that wasn't previously envisioned. After using WireGuard for a couple years I'm still excited about it because I feel like I've only glimpsed a small piece of the things that can be done with it.

It's not clear to me how much day-to-day use of Wireguard being a Fly customer requires, but I can't help but wonder if you guys should collaborate with Tailscale to make all of the micro-VMs appear on a Tailscale network, and authorize access between humans and the VMs that way.

(I admit that I haven't looked much into mesh networking / edge servers, so I don't know what the problems are. I always preferred Internet -> Identity Aware Proxy type thing -> mTLS mesh that is useless to humans. And, I don't ssh to stuff much anymore... I have my software collect debugging information and send it to something I can access through a browser or API, and control that software through an API. So everything is editing config files, basically, not SSHing places ;)

We'd love to; we don't want to build a crappy version of 1/11th of Tailscale ourselves.

> ...I can't help but wonder if you guys should collaborate with Tailscale...

I imagine a merger! Tailscale's mission is to "simplify the long tail of software development", and coincidentally, fly does just that (if only for server-side apps right now).