> ## Content Index
> Fetch the complete content index at: https://ping2prompt.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Tailcat vs Tailscale: same data plane, no control plane
- URL: https://ping2prompt.com/tailcat-vs-tailscale-no-control-plane/
- Published: 2026-11-16T19:18:07.000Z
- Updated: 2026-11-16T22:56:30.000Z
- Description: Tailcat, an open-source Go package and netcat-style CLI, carries bytes over Tailscale's data plane (WireGuard, NAT traversal, DERP) with no control plane or accounts. It suits quick two-machine links; Tailscale suits auditable access. Run your own relay for privacy.
- Author: Ping2Prompt Newsroom
- Tags: Tailscale, Under the Hood, #short-ping

## The problem they solve

Think of Tailcat as Tailscale's pipes without the management office. Tailcat is an open-source Go package and a netcat-style CLI that carries bytes over Tailscale's data plane (WireGuard, NAT traversal, DERP) with no control plane, accounts or IP addresses.

Tailscale targets ongoing, auditable connectivity, giving people, devices, services and agents identities with access rules. Tailcat targets connecting machines without an account, identity or tailnet first.

## How Tailcat does it

A connection takes six steps:

- **Server keys and address**: the server generates a keypair (ephemeral or named and reused), picks a DERP relay, and builds an address of the form tc + base64(CBOR(public key + DERP bootstrap info)).
- **Out-of-band sharing**: you pass the address on yourself, directly or through a DNS TXT record whose hostname you share. There is no control plane to do it.
- **Rendezvous**: the client connects to the DERP server named in the address and sends a MEOW message to the server's public key.
- **Accept**: if the server accepts the client's key (access can optionally be locked down), it sends a MEOW reply.
- **Transport**: the client opens TCP through an embedded userspace stack on WireGuard, using synthetic IPv6 addresses that users and the OS never see.
- **Path**: NAT traversal tries to get WireGuard UDP flowing directly between the peers. If both sides are behind hard NAT with no port mapping, traffic falls back to DERP.

The commands in this piece come from the documentation listed under Sources; check them against the release you have installed before running them. `tailcat` starts a server and prints an ephemeral address, and `tailcat <address>` connects as a client. `tailcat serve 8080,8443` exposes ports, and `tailcat forward <address> 18080:8080 3306` forwards them locally.

Forward listeners bind to 127.0.0.1 by default. Use `--bind=0.0.0.0` only when clients on other machines must connect, because it opens the listener beyond your own host.

## How Tailscale does it

Tailscale layers a server-side control plane on the same data plane, which Tailcat deliberately leaves out. Tailscale's core, DERP server and Linux and Android clients are open source. Its control plane is not, and Headscale is a self-hosted alternative that Tailscale partially funds.

## What each one trusts

- **Tailcat access**: whoever holds the address, plus the public keys each node shares. An optional key allowlist can restrict clients.
- **Treat the address like a password**: don't log it, commit it to source control, or share it with anyone who shouldn't have access.
- **Keys**: ephemeral on every run by default, or an optional long-lived keypair.
- **Traffic**: end-to-end encrypted with WireGuard, but the hosted relay keeps metadata logs, and Tailcat is not entirely anonymous.
- **Tailscale access**: identities with access rules, auditability and governance, backed by a control plane you cannot inspect in source form.

## Failure modes and cost

- **Userspace only**: Tailcat never creates TUN devices or changes the routing table.
- **Throttled relays**: Tailscale-hosted DERP servers are rate-limited, and the hosted relay is not meant for privacy or high throughput.
- **Fix**: run your own `derper`; that also removes the dependence on Tailscale as a company.
- **No policy layer**: Tailcat leaves out accounts, identity, policies, device management and persistent access.
- **Browser demo**: the experimental WebAssembly build relays over DERP only, with no direct connections yet.

## Which one, for whom

Tailscale's own guidance is to use Tailscale for ongoing, governable access and Tailcat for a quick link between two machines. Pick Tailcat for a one-off file transfer, a CI job or a temporary SSH session where an account is more trouble than the task. Pick Tailscale if several people or machines need access you can review, revoke and audit. If you need privacy or bulk throughput over Tailcat, plan on your own relay.

## What the sources don't cover

- The exact rate limit on Tailscale-run relays is not stated.
- The name of the allowlist option is not given, and the README usage section is cut off after `tailcat browse`.
- No security audit of Tailcat is mentioned.
- How Tailscale distributes keys and enforces ACLs is described only in general terms.

## Sources

- [tailscale.com/blog/tailcat](https://tailscale.com/blog/tailcat?ref=ping2prompt.com)
- [tailscale.com/tailcat](https://tailscale.com/tailcat?ref=ping2prompt.com)
- [raw.githubusercontent.com/tailscale/tailcat/main/README.md](https://raw.githubusercontent.com/tailscale/tailcat/main/README.md?ref=ping2prompt.com)

---

This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our [editorial methodology](https://ping2prompt.com/about-how-we-work/) and the [corrections log](https://ping2prompt.com/corrections/). Spotted an error? Email [editor@ping2prompt.com](mailto:editor@ping2prompt.com).