Tailscale Aperture and the Border0 Acquisition: The Sovereign NetBird Alternative

With Aperture and the acquisition of Border0, Tailscale is building a central control plane in March 2026 for the access of AI agents and privileged users to servers, databases and LLMs, and according to the vendor this very control plane runs on AWS. Technically this is an elegant move: an identity-bound point of control for humans and autonomous agents. For European decision-makers, however, it shifts the central question. No longer just "how secure is my VPN" but "whose law governs the identity, key and policy control that orchestrates these agents". In this article we put into fact-checked context what Tailscale announced, why it becomes a US-centric control plane, and why self-hosted NetBird with managed hosting from birdhost is the sovereign counter-position. This is not about "safer than Tailscale" but about a different legal and data architecture.

What Tailscale Announced in March 2026: Aperture and the Border0 Purchase

Within a single week in March 2026, Tailscale unveiled two building blocks that together mark a new product direction.

On 17 March 2026, Tailscale announced the acquisition of Vancouver startup Border0. According to BetaKit, this is Tailscale's first acquisition ever, and the entire seven-person team is joining Tailscale.[2][3] Border0 founder Andree Toonk has since been Director of Engineering, driving the build-out of the PAM capabilities.[2]

On 23 March 2026, Tailscale made Aperture available self-serve without a waitlist, explicitly as an alpha, that is, an early release of an experimental product. The official announcement puts it this way: "Aperture by Tailscale is now available in alpha via self-serve! No more waitlist or waiting around on approvals", combined with the note "this is an early alpha release of an experimental product".[1] Aperture can be purchased for use separately from paid Tailscale plans.[1] As of August 2026, little has changed: the Aperture product page still speaks of an alpha and beta phase with one-on-one customer support and lists no published prices.[15]

Both steps target the same problem: controlling the access of humans and AI agents to sensitive resources at an identity-bound point.

Aperture: The Identity-Based AI Gateway as a Central Point of Control

Aperture addresses a concrete operational problem of modern AI architectures: LLM credentials are scattered across applications, scripts and agents. Aperture centralizes those credentials and routes requests through a single point of control.[1] Clients authenticate via their Tailscale identity (tailnet), and the gateway authenticates to the model providers. This creates a central point for control, observability and audit across users, services and agents.[1]

Aperture supports common LLM providers; the exact provider list is a matter for the official Aperture documentation and not the subject of this article. What matters for the sovereignty question is the architecture: whoever speaks through Aperture has their identity, authorization and audit trail flowing through the Tailscale control plane.

Border0 and PAM: Access Control for Humans and AI Agents

Border0 delivers classic privileged access management (PAM), integrated into tailnet, identities and policies. Specifically, Tailscale names: SSH and Kubernetes access, remote administration via RDP and VNC, database access controls, session recording, and detailed command and query visibility.[2] Tailscale intends to build a native PAM offering from this.[2]

PAM is the control point for the most powerful access in a company: who may connect to which server, which database, which cluster, and what they do there. This is precisely the layer that becomes relevant for AI agents with Aperture, because an agent that autonomously accesses production systems is, from an access-control perspective, a privileged actor. How identity-based access control intersects with NIS2 and network security we explore elsewhere.

Why It Becomes a US Control Plane: Control Plane on AWS and the CLOUD Act

This is where the sovereignty question becomes concrete. The coordination server is a single, centralized control-plane component operated by Tailscale that handles device discovery, authentication, key distribution and policy enforcement.[5] And according to Tailscale's security page, this control plane runs on Linux servers in Amazon Web Services (AWS), in AWS Virtual Private Clouds (VPCs). Coordination server data is stored in SQLite and backed up to AWS S3, with analytics held in Snowflake.[4]

An important clarification to avoid overstatement: the data plane is WireGuard peer-to-peer and end-to-end encrypted. Tailscale does not route any traffic through the coordination server.[5] No one "reads your traffic". The CLOUD Act exposure concerns the control plane and its metadata: identities, keys, policies, coordination data in SQLite and S3, analytics in Snowflake. That is exactly the layer that Aperture and the future PAM turn into the orchestration point for agent and privileged access.

By consistent reporting from BetaKit, Bloomberg and The Logic, Tailscale is a company headquartered in Toronto, Canada, funded among others by Accel, CRV and Insight Partners.[14][3] The Canadian domicile, however, is not decisive for the CLOUD Act question. The CLOUD Act (18 U.S.C. 2713) requires US providers to disclose data in their possession, custody or control, "regardless of whether such communication, record, or other information is located within or outside of the United States".[6] Because the control plane sits with a US provider (AWS), the exposure arises via the cloud provider, not via the company domicile. In addition, a substantial share of Tailscale's DERP relay servers are in the US, around 37 percent by the documented locations (10 of 27 cities).[13]

GDPR, Article 48 and Schrems II: The Legal Tension

This architecture creates a legal conflict that is relevant for GDPR-bound organizations. GDPR Article 48 makes clear that judgments or orders from a third-country authority may only be recognized or enforceable if they are "based on an international agreement, such as a mutual legal assistance treaty" in force between the requesting third country and the Union or a member state.[7] The CLOUD Act is a unilateral US rule without that basis.

In the Schrems II context this intensifies: an EU storage location alone does not prevent US access at a US provider, because jurisdiction follows control, not location. The EDPB Recommendations 01/2020 are decisive here: contractual measures alone are not sufficient; supplementary technical measures such as customer-side key control are required when the provider falls under US jurisdiction.[12] In practice this means: anyone running identity, key and policy control for privileged and agent access through a US cloud carries a compliance risk that cannot be fully resolved contractually. We described this in detail in GDPR-compliant VPN: why US cloud VPNs are a compliance risk.

The Sovereign Counter-Position: NetBird with a Self-Hosted Control Plane

The answer to a US-centric control plane is not "more encryption" but a different legal jurisdiction over the control plane. This is exactly where NetBird comes in.

NetBird is open source including the control plane and fully self-hostable. The repository is under the BSD-3-Clause license; the management/, signal/ and relay/ directories are under AGPLv3.[10] This means the entire control plane, management server, signal, relay and STUN, can be operated yourself, for example via a combined Docker Compose configuration; an optional proxy exposes internal resources selectively, and with the proxy enabled CrowdSec can be added for IP reputation blocking.[11]

The difference from the Tailscale architecture is fundamental: with Tailscale the control plane is proprietary and sits on AWS; with NetBird it is open and can run within your own legal jurisdiction. You can find the full technical comparison in NetBird vs. Tailscale 2026: the big comparison, and if price is the trigger, in Tailscale price increase 2026: the sovereign NetBird alternative.

NetBird Series A and the European Sovereignty Strategy

A legitimate question with open-source alternatives is: will the project last? With NetBird, the numbers argue in its favor. The Berlin-based company closed a Series A of $10M, or €8.5M, on 13 January 2026, led by Pace Capital, with Nauta Capital, InReach Ventures and Antler.[8]

More important strategically than the amount is the orientation: NetBird explicitly names European digital sovereignty as an important part of its long-term strategy, as demand grows for security infrastructure developed within Europe.[9] The open-source repository has around 28,000 GitHub stars (as of August 2026), an indicator of a broad, active community.[10] A sovereign alternative is therefore not the niche project of a single maintainer but a funded, Europe-based platform with a clear sovereignty agenda.

What You Get Concretely with NetBird and birdhost

NetBird's technical substance covers the building blocks relevant for agent and privileged access without handing control out of your own legal jurisdiction:

• Identity-based access control via SSO/OIDC, with posture checks for device compliance, comparable to the principle of an identity-bound point of control.
• Native, identity-aware SSH/SFTP/SCP, exactly the access type that forms the core of the PAM context.
• Selective exposure of internal services via an optional proxy on your own infrastructure, without traffic flowing through third-party relays.[11]
• WireGuard foundation, the same state-of-the-art cryptography as Tailscale; switching does not touch the cryptographic foundation.

With managed hosting from birdhost, this very control plane runs in ISO 27001 certified data centers in Germany (certification held by the data center operator). No control-plane metadata flows to US cloud providers; data processing agreements (DPA) are available. Commercially this is a predictable flat rate from €99.90/month with unlimited users and devices, decoupled from seat counts and agent volumes. If you are coming from a classic setup, setting up WireGuard in the enterprise covers the basics, and for current networking topics, NetBird v0.71: IPv6 overlay addressing offers a look at the ongoing development.

Migration and Parallel Operation: Step by Step, Not Big Bang

Switching need not be a risk. Because both solutions use WireGuard and the NetBird clients can run in parallel to an existing Tailscale installation, migration can be planned in phases:

1. Set up a pilot network: birdhost provisions a dedicated NetBird instance in Germany, connecting your existing IdP via SSO/OIDC.
2. Map policies: existing access rules are rebuilt in the NetBird web UI, including the SSH and service rules relevant to PAM-like scenarios.
3. Run in parallel: individual teams, sites or agent workloads are migrated first, the rest stays on Tailscale for now.
4. Cutover and decommission: after successful validation, the old control plane is retired.

birdhost accompanies this process including setup, monitoring, updates and incident response. If you are evaluating other solutions, Twingate alternative 2026: NetBird vs. Twingate and Fortinet VPN alternative 2026 are also worth a look.

Conclusion: When the US Control Plane Fits and When the Sovereign Alternative

With Aperture and Border0, Tailscale is making a strategically smart move: an identity-bound control plane for the world of AI agents and privileged access, with the fastest onboarding on the market. For teams that want maximum convenience and accept the processing of control-plane metadata on US cloud infrastructure (AWS), this is a compelling choice.

For European organizations that prioritize data sovereignty, GDPR and NIS2, however, this very new control plane shifts the risk. Running identity, key and policy control for the most powerful access in a company through a US cloud cannot be fully secured contractually. NetBird with managed NetBird hosting from birdhost is the sovereign counter-position here: an open-source control plane in a German ISO 27001 data center, with no metadata leaking to US providers, with a DPA and migration support.

The honest lever is not "better than Tailscale" but data sovereignty within your own legal jurisdiction. Anyone who needs the new agent and PAM control plane but must keep control in Europe should evaluate the sovereign alternative. A 7-day free trial is available; a credit card is required to start.

Sources

• [[1]] Tailscale Blog: Aperture by Tailscale is now self-serve (self-serve alpha, 23 March 2026)
• [[2]] Tailscale Blog: Border0 joins Tailscale (acquisition, 17 March 2026, Andree Toonk)
• [[3]] Bloomberg: Canada Cyber Startup Tailscale Buys Border0 as AI Agents Spill Onto Servers (17 March 2026)
• [[4]] Tailscale Security: control plane runs on AWS (VPCs, S3 backup, Snowflake)
• [[5]] Tailscale Docs: Control and data planes (coordination server)
• [[6]] Cornell LII: 18 U.S.C. 2713 (CLOUD Act, required preservation and disclosure)
• [[7]] GDPR Article 48: Transfers or disclosures not authorised by Union law
• [[8]] tech.eu: NetBird announces $10M Series A (13 January 2026, Pace Capital)
• [[9]] EU-Startups: Berlin's NetBird raises EUR 8.5M (European digital sovereignty)
• [[10]] NetBird GitHub Repository (BSD-3-Clause / AGPLv3, approx. 28k stars)
• [[11]] NetBird Docs: Self-Hosted Quickstart (management, signal, relay, STUN)
• [[12]] Wire Blog: What the CLOUD Act Really Means for EU Data Sovereignty (EDPB / Schrems II)
• [[13]] Tailscale Docs: DERP servers (locations, approx. 37 percent US)
• [[14]] Tailscale Company (VC-funded: Accel, CRV, Insight Partners)
• [[15]] Aperture by Tailscale – product page (alpha/beta phase, no published pricing; as of August 2026)
• BetaKit: Tailscale makes first acquisition with Border0 purchase
• NetBird – Open Source Zero Trust Networking