fly-tailscale-exit VS headscale

I used to do Algo with a VM on GCP. But fly.io and tailscale has made this really simple. Try this if you are looking for an easier alternative https://github.com/patte/fly-tailscale-exit

Yes, fly.io allows you to expose a UDP port. See the [fly.toml](https://github.com/patte/fly-tailscale-exit/blob/main/fly.to...) in the repo. To make, the tailscale port [is pinned](https://github.com/patte/fly-tailscale-exit/blob/main/start....) to the exposed port (41641 in that case).

I just tested it again and the connections are made directly (after the first 2,3 go via DERP):

headscale - Open source implementation of Tailscale control server. Can be used with Tailscale's official open source client. Written in Go.

Headscale

You can always use headscale. https://github.com/juanfont/headscale

One more thing, you can host Tailscale Control Server yourself if you want, which is a plus.

https://github.com/juanfont/headscale not to mention but Tailscale has a very good culture, I’m sure they would give notice if they pull the rug. There are also many alternatives such as Zerotier and more are showing up every day and open source options.

How about self-hosted Tailscale, known as Headscale

Would be nice if https://github.com/juanfont/headscale can be managed by the Tailscale operator.

You can run your own "head scale" control server and use their clients with it: https://github.com/juanfont/headscale

Requires a lot more setup, but it is an option. I've been self-hosting headscale for some time and it is quite stable.

There's an alternative to tailscale service called headscale https://github.com/juanfont/headscale (CLI only server compatible with official tailscale clients)