Tailscale introduces netmap caching, a client feature that saves a copy of the tailnet network map to disk so nodes start faster and can still reach peers when the coordination server is unavailable. The post explains the netmap contents, how only changed chunks are written, and how DISCO keys are exchanged through encrypted DERP-relayed WireGuard messages to re-establish direct connections without the coordination server. It also notes the staleness tradeoff over time.
Tailscale engineering blog
Loading
Tailscale's Aperture now lets teams import, create, and share agent skills from one place, with import paths including file upload, GitHub sync, .well-known URL discovery, and MCP. Skills can be distributed to agents and computers over the new Skills over MCP spec, with admins controlling access by identity. The post is mostly a feature overview with limited architectural detail.
Tailscale has made OAuth apps generally available, letting agents provision devices on a user's tailnet through standard OAuth 2.0 with the user's identity, so tailnet policies, audit logs, and quotas still apply. The post includes an example policy that uses custom device posture attributes to give agent devices narrower access than the user's own devices.
Avery Pennarun argues that AI will create a billion new programmers who need simple, self-hosted ways to run and share what they build. He ties this to networking complexity, the risks of AI vendor lock-in, and the case for replaceable, open components in AI stacks.
A Tailscale blog post describing how a private mesh network could have replaced port forwarding, dynamic DNS, and VPN servers for a student's remote desktop access. It walks through Taildrive, MagicDNS, Funnel, and declarative node sharing for group projects, with the vendor's features as the main focus.
Tailscale describes vulnerabilities in Tailscale SSH and related features, reported in the 'Tailworm' report, that let an authenticated session exceed its local user's privileges, including through SSH forwarding. The post explains that the flaws were in post-authorization permission enforcement, that exploitation requires an existing foothold on an authorized tailnet peer, and that they are fixed in v1.104.4. It also recommends reviewing SSH policies and enabling SSH check mode for sensitive...
Tailscale PAM, now in beta, layers privileged access management onto Tailscale's VPN mesh using connectors that sit beside target networks. The post covers how connectors mediate access to SSH, databases, Kubernetes, and web apps, and how credential injection and session recording (query logs, SSH replays) work. It frames PAM as the logging and access-control layer that complements the VPN's peer-to-peer connectivity.
Tailscale describes MagicRoute, a beta routing system that scores subnet routers, app connectors, exit nodes, and Services from each client's perspective. It replaces DERP-region matching, which caused connector flapping and broke custom DERP setups, with coarse-location distance scoring, sticky connector selection, and ranked failover. The post also explains why the design uses one tailnet-wide option instead of per-node rules.
A step-by-step guide to self-hosting the FreshRSS feed aggregator and reader with Docker, using Tailscale to give it a private tailnet URL. It also covers connecting third-party RSS apps and LLM agents through FreshRSS's Greader-compatible API.
Tailscale announces a multi-year, multi-million-dollar investment in sovereign AI, led by newly appointed General Manager Patricia Prewitt. The post argues that control over data, dependencies, and providers requires interoperable open infrastructure, but it presents no roadmap or technical details and says more will be announced later.
Tailscale explains how Codex Cloud connects to private tailnet resources without a custom partnership or API. The post covers auth-key configuration, supported protocols and networking limitations, and practical controls such as tags, grants, expiry, device approval, and flow logs for safely constraining agent access.
Andrew Cunningham explains how Meta’s Muse joins a Tailscale network as a separately authenticated node, enabling access to self-hosted services and SSH-managed devices. The post details least-privilege controls, explicit access confirmation, outbound-only connections, encrypted communication, and tailnet policies for limiting agent risk.
Tailscale details performance improvements across its networking data plane, including lower-memory packet handling, multi-queue processing, Linux writev support, and cached network maps. The changes improve throughput, latency, and startup times for subnet routers, app connectors, exit nodes, and clients operating under poor connectivity.
Andrew Cunningham examines why VPN servers built into consumer routers and NAS devices can suffer from NAT traversal failures, limited performance, uncertain security support, and administrative overhead. He contrasts these centralized setups with Tailscale’s peer-to-peer connections, identity-based access controls, split tunneling, and centralized policy management.
Tailscale’s Kubernetes Operator 1.102 introduces a PeerRelay custom resource for managing in-cluster relays, improving cross-cluster connectivity in restrictive VPC environments. It also adds IPv6 egress support and optimizes Let’s Encrypt certificate retries, issuance, and deletion handling to reduce deployment delays and rate-limit pressure.
Tailscale explains how to embed secure networking into applications with the Go-based tsnet library and provision isolated tailnets through APIs. It also covers automating certificates, sharing policies, ACLs, key rotation, and administrative workflows through code and GitOps.
Tailscale introduces tailcat, an open-source Go package and CLI that uses WireGuard, NAT traversal, and DERP without the Tailscale control plane or accounts. The post explains its address exchange, userspace TCP stack, direct and relayed connections, SOCKS mode, and self-hosted DERP options.
Tailscale integrates Control D DNS filtering directly into a tailnet, letting teams apply security rules to users, groups, tags, or devices through ACLs. The post explains nameserver setup, encrypted DNS queries, custom filtering rules, and user-based billing.
Tailscale introduces its PAM beta, combining private connectivity with identity-aware privileged access controls. The product supports just-in-time approvals, resource-level policies, connector-based access to infrastructure, and session logging or recording for audits and investigations.
Tailscale announces Aperture’s general availability as an AI gateway for managing model access, MCP endpoints, and agent tools. The release adds built-in model tokens, tailnet and Tailscale SSH controls, chat Projects, fine-grained permissions, and audit-friendly access controls.