- 1 dedicated IP address
- 10 devices
- 5 open ports
- 100 GBbandwidth
- 20 Mbpsspeed
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.
Updated
| Price | $5/mo | Per IP address, billed with that IP's renewal. The first charge is prorated from your credit balance. |
|---|---|---|
| In your tailnet | One node, named after your IP, for example getastatic-203-0-113-10 | |
| You provide | A pre-auth key from the headscale CLI, and your login server URL (server_url) | |
| Approval | Approve its exit route once with headscale nodes approve-routes, or let an autoApprovers rule do it | |
| Devices | Any device with the Tailscale app, signed in to your Headscale server | |
| Removal | One link in the dashboard. Unused time goes back to your credit balance. |
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 →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.
You need shell access to the Headscale server for the headscale CLI. Step-by-step detail: the Headscale setup guide.
Plus for light use, Pro for most people, Ultra for full gigabit.
5× speed · 10× bandwidth · 2 IPs — only $2/mo more
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.
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.
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.
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.
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 →