A Headscale exit node with a dedicated static IP

You already run Headscale. GetAStatic adds an exit node to it for $5/mo per IP address, on top of a plan from $2/mo. Paste a pre-auth key and your login server URL, approve the route, and your devices reach the internet from your own dedicated IPv4. No VPS to run.

GetAStatic is not affiliated with Headscale or Tailscale. Headscale steps from the Headscale docs, checked 2026-11-02.

Instant setup US-based IP

Updated

Facts

The add-on at a glance

Price$5/moPer IP address, billed with that IP's renewal. The first charge is prorated from your credit balance.
In your tailnetOne node, named after your IP, for example getastatic-203-0-113-10
You provideA pre-auth key from the headscale CLI, and your login server URL (server_url)
ApprovalApprove its exit route once with headscale nodes approve-routes, or let an autoApprovers rule do it
DevicesAny device with the Tailscale app, signed in to your Headscale server
RemovalOne link in the dashboard. Unused time goes back to your credit balance.
The problem

Headscale gives you the control server, not the exit node

Headscale is an open-source, self-hosted control server for Tailscale clients. You run the coordination server, and your devices run the standard Tailscale apps. An exit node is still a node in the tailnet that offers the default route, and its public IP is the address websites see.

So a fixed outbound IP means one more machine to look after: a VPS with a static IP, Tailscale installed, IP forwarding on, logged in to your server and kept patched. A node at home only offers your home IP, which can change.

Your own static IP over WireGuard. No VPS.

Dedicated IPv4 from $2/mo →
Why use GetAStatic?

What the Headscale exit node is for

  • A fixed outbound IPv4 for your self-hosted tailnet, without a VPS whose only job is to be the exit node
  • One address to allowlist for work systems, SSH bastions and admin panels
  • Your control plane stays on your own server; only exit traffic goes through our node
  • Select it per device in the Tailscale app's Exit node menu, like any other exit node
  • Pairs with a static IP for the Headscale server itself: see the Tailscale static IP page
How it works

We run the exit node; you approve it in Headscale

The add-on runs a Tailscale node in an isolated container on our host. It logs in to your Headscale server with a pre-auth key that you create and your login server URL, and it offers itself as an exit node. It appears with a name made from your IP, for example getastatic-203-0-113-10.

Exit traffic leaves through its own WireGuard device on your static IP and counts against that IP's plan. Your Headscale server, users and policy stay where they are. The key lets one node join: it gives us no access to your server or the headscale CLI.

This is the other direction from hosting Headscale itself on a static IP. To give the control server a fixed public address, see Tailscale static IP. Both work together.

Setup

Set up the Headscale exit node

You need shell access to the Headscale server for the headscale CLI. Step-by-step detail: the Headscale setup guide.

  1. Choose a plan. Your static IP shows in the dashboard.
  2. Create a pre-auth key. On the Headscale server, run headscale users list, then headscale preauthkeys create --user <USER_ID>. The default key is single-use and valid for one hour, which is enough. Do not add --ephemeral.
  3. Find your login server URL. It is server_url in Headscale's config.yaml: the URL your devices use with --login-server, for example https://headscale.example.com.
  4. Add the exit node. In the dashboard, open the Devices tab, then Settings. In the Exit node row, select Add, choose Headscale, and paste the key and the URL. We use the key once and do not store it.
  5. Approve the exit route. When getastatic-203-0-113-10 shows in headscale nodes list, run headscale nodes list-routes, then headscale nodes approve-routes --identifier <NODE_ID> --routes 0.0.0.0/0,::/0.
  6. Select it on your devices. In the Tailscale app, open Exit node and select the getastatic node. That device now reaches the internet from your static IP.
Good to know

Good to know

  • Our node connects to your login server over the internet. A URL that works only on your LAN, or only inside the tailnet, cannot work.
  • Exit traffic counts against your static IP's plan: the same speed cap and the same data quota.
  • The address is a datacenter IP, not a residential one.
  • Each IP address takes one exit node. For a second exit node, add another IP address.
  • If the tunnel to your static IP drops, the exit node blocks the traffic. It never sends it out from another address.
  • Built for a stable address, not anonymity: the IP your devices connect from is logged.
Pricing

Choose your plan

Plus for light use, Pro for most people, Ultra for full gigabit.

Plus
$2/mo

 

  • 1 dedicated IP address
  • 10 devices
  • 5 open ports
  • 100 GBbandwidth
  • 20 Mbpsspeed
Ultra
$10/mo

 

  • 2 dedicated IP addresses
  • Unlimited devices
  • Unlimited open ports
  • 5 TBbandwidth
  • 1 Gbpsspeed
Unlimited
Need unlimited data?
  • 100 Mbpsspeed
  • Unlimitedbandwidth
  • 1 dedicated IP address
$15/mo
  • Inbound + outbound access
  • Instant activation
  • 7-day money-back guarantee
  • Cancel anytime
Add-ons, per IP addressCustom hostname $5·Addtl. IP $2/mo (Ultra $7/mo, Unlimited $15/mo)·Gigabit Speed (Plus & Pro) $5/mo·Exit node (Tailscale, NetBird, Headscale) $5/mo·SMTP $25
FAQ

Questions, answered.

01Is this the same as running Headscale on a static IP?

No, it is the other direction. Here your Headscale server stays where it is, and we add an exit node to it. To give the Headscale server itself a fixed public address that every device can reach, run WireGuard on its host with a static IP: see Tailscale static IP.

02Why must I approve the exit node?

Headscale does not route internet traffic through a node until an admin approves its exit route. Run headscale nodes approve-routes once. To approve exit nodes automatically, add an autoApprovers rule for exit nodes to your Headscale policy. Older Headscale versions use headscale routes enable instead.

03What do you see?

The exit node sends your devices' internet traffic out from your static IP, and the IP your devices connect from is logged. GetAStatic is built for a stable address, not anonymity. The pre-auth key lets one node join your tailnet. Your Headscale policy decides what that node can reach, like any other node.

04How fast is the exit node?

As fast as your plan: 20 Mbps on Plus, 100 Mbps on Pro and 1 Gbps on Ultra. A device whose connection goes through a DERP relay instead of directly can see lower speed.

05Which pre-auth key should I create?

The default single-use key works: we use it once, within minutes. Do not create it with --ephemeral: Headscale deletes an ephemeral node after it is offline for a while, and it cannot rejoin without a new key. If the key is rejected, the dashboard row shows the error and a Retry with a new key link, with no extra charge.

Have more questions? See the full FAQ →