Softwr

Networking · head to head

Headscale vs Hookdeck

Headscale logo

Headscale

Networking

Open source reimplementation of the Tailscale coordination server for a single organisation

From
Free
Free plan
Yes
Hookdeck logo

Hookdeck

Developer Tools

Event gateway that receives, queues, retries and replays inbound webhooks

From
Free
Free plan
Yes

The short version

  • Headscale is free; Hookdeck starts at $39/mo.
  • Only Headscale lists self hosted control server; only Hookdeck lists ingest and persist.
  • Where Headscale falls short: it is deliberately single tenant, so a managed service provider cannot use one deployment to serve several customer networks.
  • Where Hookdeck falls short: pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries.
  • Prices and features on this page were last checked on 20 November 2026.

How do Headscale and Hookdeck differ?

Headscale and Hookdeck differ on pricing model, platforms and category (Networking against Developer Tools). Only the attributes on which Headscale and Hookdeck actually diverge.

Attributes where Headscale and Hookdeck differ
AttributeHeadscaleHookdeck
Pricing modelOpen source, no licence feePer month by delivered event count
PlatformsLinux, Self-hostedWeb, Linux, macOS, Windows
CategoryNetworkingDeveloper Tools

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

They share no listed features; 6 appear only for Headscale and 6 only for Hookdeck. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Headscale

  • Self hosted control server
  • Access control policies
  • User separation
  • Pre-authentication keys
  • Subnet routers and exit nodes
  • Own or shared DERP

Only in Hookdeck

  • Ingest and persist
  • Automatic retries
  • Filters and fan-out
  • Transformations
  • Local development CLI
  • Rate limiting

What is each one used for?

Headscale is most often brought in for running a mesh network where no third party may hold the device registry. The jobs each tool is most often brought in to do.

Headscale

  • Running a mesh network where no third party may hold the device registrynot Hookdeck
  • A homelab or personal fleet where paying per user for a hosted control plane is not worth itnot Hookdeck
  • Air gapped or restricted environments that cannot reach an external coordination servicenot Hookdeck
  • Keeping the Tailscale client experience while removing the vendor from the trust pathnot Hookdeck

Hookdeck

  • A payments integration where losing a Stripe event during a deploy causes an order to go unfulfillednot Headscale
  • Fanning one provider webhook out to several internal services without each subscribing separatelynot Headscale
  • Debugging a partner integration by replaying the exact failing payload after shipping a fixnot Headscale
  • Receiving production-shaped webhooks on a developer laptop without running a public tunnelnot Headscale

Where do Headscale and Hookdeck fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Headscale

  • The clients are proprietary software maintained by a company with no obligation to Headscale, so a client update can change protocol behaviour and break your control server until volunteers catch up
  • Features that live on the vendor side, including the admin console, Funnel and app connectors, do not exist here and cannot be added, so feature comparisons against Tailscale are misleading
  • There is no official web interface, so day to day administration is a command line tool or one of several unofficial front ends of varying quality and maintenance
  • It is deliberately single tenant, so a managed service provider cannot use one deployment to serve several customer networks
  • Upgrades have required database migrations and policy format changes between releases, and with no support contract a failed migration on the control server is your problem alone

Hookdeck

  • Pricing meters delivered events, so fan-out multiplies the bill: one inbound event routed to four services counts as four deliveries
  • Free-tier retention is three days, which is shorter than the time it typically takes to notice a failing integration, so the payloads needed for a replay are often already gone
  • It becomes a single point of failure in front of every third-party integration, and an outage there means every provider webhook queues or fails at once
  • The transformation layer runs JavaScript in a constrained environment, so anything that needs a database lookup or an external call has to happen downstream instead
  • For a team already running Kafka or SQS the value is mostly the console and the replay UI, which is a hard cost to justify against infrastructure they already operate

How much do Headscale and Hookdeck cost?

Headscale is free to use; Hookdeck has a free plan, with paid plans from $39/mo. Plan by plan below, from each vendor's own pricing page.

Headscale

Free
  • HeadscaleFree
    • Full functionality, no node limit
    • Official Tailscale clients on every platform
    • No vendor account required

Hookdeck

Free
  • DeveloperFree
    • Up to ten thousand events per month
    • Three-day retention
    • One user
  • Team$39/mo
    • Ten thousand events included
    • Unlimited users
    • Pay as you go metering above the included events
  • Growth$499/mo
    • Ten thousand events included plus metered usage
    • Thirty-day retention
    • Uptime and latency SLAs
  • EnterpriseOn request
    • Negotiated event volume
    • Custom retention
    • Dedicated support

Which should you pick?

Choose Headscale if

  • You need self hosted control server.
  • You want to start without paying.
  • You work on Linux, Self-hosted.
  • You also want access control policies.

Choose Hookdeck if

  • You need ingest and persist.
  • You want to start without paying.
  • You work on Web, Linux, macOS, Windows.
  • You also want automatic retries.

Questions people ask

Is Headscale or Hookdeck better?
Neither clearly leads. Headscale starts at Free and Hookdeck at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Headscale or Hookdeck?
Headscale starts at Free and Hookdeck at Free.
Does Headscale or Hookdeck run on more platforms?
Headscale runs on Linux, Self-hosted. Hookdeck runs on Web, Linux, macOS, Windows.
Can I use Headscale for free?
Both have a free tier, so you can try either at no cost before committing.
What is Headscale best used for?
Headscale is most often used for running a mesh network where no third party may hold the device registry, a homelab or personal fleet where paying per user for a hosted control plane is not worth it, air gapped or restricted environments that cannot reach an external coordination service, keeping the tailscale client experience while removing the vendor from the trust path. Of those, running a mesh network where no third party may hold the device registry and a homelab or personal fleet where paying per user for a hosted control plane is not worth it are not what Hookdeck is typically brought in for.
What can Headscale do that Hookdeck cannot?
Headscale covers Self hosted control server, Access control policies, User separation, Pre-authentication keys. Hookdeck covers Ingest and persist, Automatic retries, Filters and fan-out, Transformations.

Answered from the vendors’ own pages

Headscale: Is Headscale made by Tailscale?

No. It is an independent community project. Tailscale acknowledges it but does not support it, and the clients it relies on are the vendor ones.

Hookdeck: Is there a free plan?

Yes, ten thousand events a month with three-day retention and one user.

Headscale: What do I lose compared with the hosted service?

The admin console, the vendor relay network unless you use the public DERP servers, and hosted only features such as Funnel and app connectors.

Hookdeck: How is usage counted?

By delivered events, so a single inbound webhook fanned out to three destinations counts as three.

Headscale: Can I still use the public relay servers?

Yes, the default configuration can use them, though many self hosters run their own DERP to remove that dependency.

Hookdeck: Can I replay a failed webhook?

Yes, individually or in bulk from the console, with the original payload.

Headscale: Is it suitable for a company network?

For a technical team, yes. There is no vendor to escalate to, so it needs someone on staff who is willing to own the control server.

Hookdeck: Does it work for outbound webhooks too?

Yes, the same queueing, retry and observability applies to webhooks you send.

Share

Related pages

Other head to heads