I self-host my mesh VPN with NetBird instead of Tailscale — here's the one reason, and where Tailscale still wins

Description and use

The author swapped Tailscale for NetBird to achieve a fully self‑hosted VPN mesh that integrates with their existing identity provider, keeping all access control in one place and avoiding a third‑party control plane.

Problem

Need a VPN that integrates with existing identity provider and keeps control plane self-hosted, avoiding a third‑party brain.

Outcome

NetBird provides a self‑hosted, OIDC‑integrated mesh VPN that keeps all access control within the user’s own identity system, eliminating the need for a separate VPN account system.

Workflow

• 1. Install NetBird server and client on devices
• 2. Configure NetBird to use OIDC with existing IdP
• 3. Set dashboard to use ID token for authentication
• 4. Verify peer connectivity and DNS resolution across sites
• 5. Manage user/device offboarding through IdP

Evidence

NetBird speaks OIDC to my existing self-hosted identity provider. So logging into the mesh is logging into everything else — same username, same 2FA, same place to revoke a person.

Source

The token format gotcha. Wiring NetBird to my identity provider, the dashboard authenticated fine but API calls failed. The cause: my IdP was handing out opaque access tokens, and NetBird's dashboard needed a JWT.

Source