juanfont

Headscale creator here.

> Fun fact: Tailscale have an almost-assuredly-accurate count of Headscale users due to how few people disable the Tailscale client's telemetry which by default sends them real-time events about everything you do on a Headscale network. See KB1011: https://tailscale.com/kb/1011/log-mesh-traffic

That is not true. We actually instruct all the clients to send no logs - since at least three years:

https://github.com/juanfont/headscale/blame/main/hscontrol/t....

And also in the config example:

https://github.com/juanfont/headscale/blob/main/config-examp...

That said, I would have loved to know how many nodes use Headscale... :)

We have definitely improved a lot the stability and test coverage in the last year. Really, really a lot. Still a bit to go, but overall there have been many changes :)

But indeed we are not meant to replace the full frictionless experience of Tailscale SaaS.

Ah, I was not stating anything else than linking their blog post :)

I am pretty sure they would have eventually published a control server.

We just happened to be quicker (and come up with a great name, IMHO).

> even though I understand that it is (unofficially?) supported by Tailscale these days.

https://tailscale.com/blog/opensource/

Headscale dev here!

What issues did you face? :)

Or they would not be supporting the development of Headscale.

Yes?

And it's fully supported by Headscale.

It was the only possible one really.

Headscale dev here.

Companies looking into this will pay Tailscale.com service. You really need commercial support if you plan a large enterprise deployment. Tailscale even now offers a self-hosted version of their service - for those with concerns about using the public SaaS.

We do have support for separate namespaces/tailnets, and we will be adding ACLs soon...

PRs welcome :)

Yup.

Btw, there is no IdP support in Headscale. You need to have access to the machine where you are running it, and use the CLI to register your machines (or use a authkey, ofc).

Cool.