/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

juanfont/headscale

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T19:59:22.052Z

1mo ago

juanfont/headscale

Headscale is a Go-based, self-hosted open source implementation of the Tailscale control server. It has strong adoption signals from the repo itself: 36,966 stars, 1,991 forks, and recent activity as of 2026-03-29. Forks are likely interesting if you care about self-hosted tailnet control, Tailscale-compatible infrastructure, or codebases with active testing and documentation work.

Loading tags...

Stars36,966

Forks1,991

Default branchmain

Last pushed2026-03-29T00:36:56Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if the WebUI and operator workflow matter more than staying close to upstream Headscale. Choose upstream if you want current fixes, active maintenance, and the lowest compatibility risk.

Prefer this fork only if its packaging and local control-plane changes match a specific deployment need and you are willing to own long-term rebasing. For most adopters, upstream Headscale is the safer choice because this fork is significantly diverged and behind on recent fixes.

Choose upstream instead unless you specifically need this exact historical revision; this fork adds nothing observable and is behind on recent fixes and operational improvements.

Choose upstream Headscale unless you specifically need this fork's older customizations or are prepared to maintain a divergent codebase. The fork looks substantially stale and heavily modified, so it is better suited to niche adopters than to anyone wanting the safest default deployment.

Prefer upstream unless you specifically need one of the fork’s custom auth or release behaviors and are willing to maintain a deeply divergent codebase yourself.

Choose this fork only if you specifically want a legacy Headscale snapshot or are willing to maintain a large rebase yourself. For normal self-hosted tailnet use, upstream is the better choice because this fork is far behind and appears stale.

Choose this fork only if you want a bespoke Headscale branch and are prepared to verify core tailnet behavior yourself. If your priority is stability and upstream compatibility, the divergence and removed coverage are significant red flags.

Choose this fork if multi-tenancy and the added admin/tooling surface matter more than staying close to upstream. Avoid it if you need maximum upstream compatibility or a low-risk, drop-in Headscale deployment.

Prefer this fork only if you specifically need PMOVES.AI-oriented docs or agent hints. If you want improved Headscale capabilities, the fork offers little beyond upstream and is materially behind it.

Choose this fork only if its added operator/auth/storage changes matter more than staying close to upstream. If you mainly want stable Headscale compatibility and active upstream maintenance, upstream is the safer default.

Fork comparison

gps949/Mirage

38/100

stale

significant_divergence

Choose this fork if the WebUI and operator workflow matter more than staying close to upstream Headscale. Choose upstream if you want current fixes, active maintenance, and the lowest compatibility risk.

Likely purpose

A self-hosted Tailscale control server fork for users who want Headscale functionality plus a web-based admin console and a more productized operator workflow.

Best for

Self-hosters who want Headscale plus a browser UI.; Users who prefer a more product-like controller experience over upstream parity.; Operators comfortable accepting stale upstream sync in exchange for a customized management interface.

Additional features

WebUI for managing the controller through a browser instead of only CLI/config files.
GUI-oriented administration for DNS and control-panel operations, suggested by Vue files and commits about DNS page changes.
User-facing management workflows for routes, ACL-like policy behavior, and device/session state reflected by the large UI and policy test footprint.
Localized branding and documentation changes aimed at a non-upstream audience.
Introduces more operational workflow surface such as server-side handling, auth, session control, or admin tooling.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

Falls far behind upstream Headscale, with the fork last pushed in 2023 while upstream was active in 2026.
Misses a large amount of upstream testing, docs, and control-plane hardening work added later, including servertest coverage and race/consistency fixes.
Likely lacks or lags recent upstream docs/site and warning/UX improvements added in later commits.
The fork’s large deletion count and older base suggest some upstream capabilities or maintenance paths are harder to use or no longer current.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Adds a web-admin layer that should reduce friction for operators who do not want to manage Headscale purely through CLI and config files.
Better fit for people who want an opinionated, UI-driven self-hosted controller experience.
Large divergence means the fork can optimize for a specific workflow instead of staying strictly upstream-compatible.

Risks

Very stale relative to upstream, so security fixes, protocol compatibility, and operational behavior may lag.
Large code divergence increases upgrade and merge risk if you want to follow upstream later.
Because the fork is old and heavily altered, documentation and community support are likely thinner than upstream.

juanfont/headscale · Discofork