← Back to home
Comparison · Infra & APIs

Headscale vs L1centrality

A side-by-side editorial comparison of Headscale and L1centrality — release velocity, themes, recent moves, and the top alternatives to consider.

Headscale vs L1centrality: at a glance

FeatureHeadscaleL1centrality
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesself-hosted, tailscale, access-control, aclgraph-analysis, centrality, r-package, visualization
Last editorial update12d ago52m ago
WebsiteVisit →Visit →

What is Headscale?

Headscale stops approximating Tailscale's control plane and starts matching it on purpose.

Headscale's visible work is a single long beta line, 0.29.0-beta.1 through beta.4, spread from late May to mid-June. The release notes are cumulative and identical across all four betas, describing a rebuilt ACL packet-filter implementation validated against real Tailscale clients and the official SaaS, plus support for SSH rules using the check action with OIDC or CLI approval. Minimum supported Tailscale client is pinned at v1.80.0.

Read the full Headscale trajectory →

What is L1centrality?

A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.

L1centrality implements L1 centrality and prestige for graphs, including group, local, and neighbourhood variants plus MDS-based visualization. The measure set has been stable since 0.3.0; the work since has gone into interfaces around it — S3 classes with print and summary methods, plot methods for every result class, and in 0.5.0 both multi-group evaluation and multicore computation for the local variant. The two releases since have been a warning-message pass and a typo pass.

Read the full L1centrality trajectory →

Headscale vs L1centrality: editorial side-by-side

H
Headscale
INFRA · APIS
0.0

Headscale stops approximating Tailscale's control plane and starts matching it on purpose.

◆ Current state

Headscale's visible work is a single long beta line, 0.29.0-beta.1 through beta.4, spread from late May to mid-June. The release notes are cumulative and identical across all four betas, describing a rebuilt ACL packet-filter implementation validated against real Tailscale clients and the official SaaS, plus support for SSH rules using the check action with OIDC or CLI approval. Minimum supported Tailscale client is pinned at v1.80.0.

◆ Where it's heading

The project is treating behavioural parity with the hosted service as something to be tested rather than assumed — generating ACL test cases systematically against the SaaS and fixing the differences that surfaced. Adding interactive SSH approval moves headscale past connectivity into access control, which is the harder half of what Tailscale sells. The long beta series without a stable cut suggests the maintainers are unwilling to ship that surface until the packet-filter differences are fully closed.

◆ Prediction

A stable 0.29.0 is the obvious next step once the beta line settles, since the feature set has been frozen across four betas. What remains unclear from these notes is what actually changed between the betas, as each restates the same cumulative text.

L
L1centrality
INFRA · APIS
0.0

A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.

◆ Current state

L1centrality implements L1 centrality and prestige for graphs, including group, local, and neighbourhood variants plus MDS-based visualization. The measure set has been stable since 0.3.0; the work since has gone into interfaces around it — S3 classes with print and summary methods, plot methods for every result class, and in 0.5.0 both multi-group evaluation and multicore computation for the local variant. The two releases since have been a warning-message pass and a typo pass.

◆ Where it's heading

The package has moved from defining measures to operationalizing them. 0.5.0 was the inflection: parallel local computation and list-valued group input both target users running these measures over many vertex sets or large graphs rather than illustrating them on one. The same release renamed weight_transform and eta to edge_weight_transform and vertex_weight, and added an explicit message when a distance matrix is received — the signature of a maintainer fielding the same misuse repeatedly.

◆ Prediction

The last two releases carry no functional change, so the near-term path is maintenance rather than new measures; a 0.6.0 would most likely extend parallelism beyond L1centLOC to the other computationally heavy variants.

Alternatives to Headscale and L1centrality

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Headscale or L1centrality.

See all Headscale alternatives → · See all L1centrality alternatives →

Recent activity from Headscale and L1centrality

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agoL1centralityTypo fixes only
  2. 2mo agoHeadscaleRegister user-lookup error reworded to match the CLI test
  3. 2mo agoHeadscalev0.29.0-beta.4
  4. 2mo agoHeadscalev0.29.0-beta.3
  5. 2mo agoHeadscalev0.29.0-beta.2
  6. 2mo agoHeadscale0.29.0 beta: SSH check actions and Tailscale ACL parity
  7. 3mo agoL1centralityWarning message wording updated
  8. 3mo agoL1centralityMulti-group prominence and multicore local centrality
  9. 9mo agoL1centralityPlot methods for every result class, plus edge-weight transforms
  10. 1y agoL1centralityHandles unnamed vertices; quantile type pinned
  11. 1y agoL1centralityS3 classes for all results, plus a Gini coefficient

Frequently asked questions

What is the difference between Headscale and L1centrality?

They serve adjacent needs but don't currently overlap on shipped themes. Headscale and L1centrality are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Headscale better than L1centrality?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Headscale and L1centrality are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Headscale?

Top Headscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Headscale alternatives" section above for the current picks, or visit /alternatives/headscale for the full list with editorial commentary on each.

What are the best alternatives to L1centrality?

Top L1centrality alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "L1centrality alternatives" section above for the current picks, or visit /alternatives/l1centrality for the full list with editorial commentary on each.