> Did you try Headscale? https://github.com/juanfont/headscale or netbird? Am aware of them but IIRC they are both unaudited which kind of brings us back to square one ? We would still end up running them at arms-length as we do with Tailscale at the moment. Also isn't Headscale server-side only ? - Source: Hacker News / 5 days ago

Did you try Headscale? https://github.com/juanfont/headscale or netbird? The latter has been great for me. - Source: Hacker News / 5 days ago

You'll need a config.yaml (server URL, IP ranges, DERP settings) — grab the template from the Headscale repo. Point your Tailscale clients at your server with tailscale up --login-server=https://your-domain, and you have a private mesh with nobody else in the loop. - Source: dev.to / 27 days ago

Headscale is a self-hosted, open-source implementation of the Tailscale control plane. Same WireGuard mesh, same clients — but your data stays on your infrastructure. If you're already running k3s with ArgoCD, adding Headscale is straightforward. - Source: dev.to / about 1 month ago

Headscale is the open-source implementation of the Tailscale coordination server. Self-hosting it gives you one thing Tailscale's SaaS doesn't: control over the DERP map. - Source: dev.to / about 1 month ago

Yeah, that's the biggest pain point I think. Syncing configs once changes are made (new peers, new access rules, pre shared key rotation etc). It's one of the reasons I'm working on wirehub[0], as a way to distribute configs to both end users (share a link) and machines (have a script to periodically pull from wirehub). Not the perfect solution, but one that does not require additional clients/agents/software to... - Source: Hacker News / over 1 year ago

It's not a saas but a tool to create, manage and share wireguard configs. You define networks, add devices, label them, and create access rules based on those labels so that working with addressess and allowed ips is more user friendly. Then you can create invites so that sharing the configs with the right people or machines also becomes much easier. https://wirehub.org. - Source: Hacker News / over 1 year ago

I'm experimenting to figure out the simplest setup possible that allows me to expose an internal web service (eg localhost:3000) to the public Internet (eg app.example.com). A million ways to do this, of course, but I'm focused on using wireguard so that eg only my wireguard peers can get access to my local service, and for internal traffic (ie vpn). At the moment I'm settling on having a simple script that I can... - Source: Hacker News / almost 2 years ago

It's https://wirehub.org Yeah, theres a typo right on the homepage, I know, I'll get to it.. :). - Source: Hacker News / over 2 years ago

I made wirehub.org[1] because I needed a way to setup a WireGuard VPN without giving out my private keys to anyone. Yeah I could self host an open source solution, but where's the fun in that? :p [1] https://wirehub.org. - Source: Hacker News / over 2 years ago