Netbird v0.74.0 released

Announcements Releases
1

netbird v0.74.0 released

Release Notes for v0.74.0

New Feature: Agent Network

This release introduces Agent Network, a per-account LLM gateway that gives people and agents keyless, identity-based access to LLM APIs and internal resources over the tunnel. It is built on top of the existing reverse proxy and private services, so the transport is still NetBird’s WireGuard overlay and the identity model is still your IdP. Have a tunnel, get access; no tunnel, no access.

Agents point at a tunnel-only endpoint instead of the provider’s URL. NetBird holds the upstream provider key server-side, injects it per request, and ties every call to a real identity from your IdP. Client-supplied auth headers are stripped before the request is forwarded, so a hardcoded key never reaches the provider. The whole thing is default deny: nothing reaches a provider until a policy explicitly allows it.

Core capabilities:

  • Keyless access to LLM APIs. No keys stored or shared on the client. The tunnel is the credential.
  • Provider catalog. First-party APIs (OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Google Vertex AI, Mistral), AI gateways (LiteLLM Proxy, Portkey, Bifrost, Cloudflare AI Gateway, Vercel AI Gateway, OpenRouter), and any custom/self-hosted OpenAI-compatible endpoint (Ollama, vLLM, local GPU hosts).
  • Policies. A policy connects a Source Group (users or agent devices from your IdP) to one or more providers.
  • Limits. Token caps and budget (USD) caps per user and per group, plus account-wide Global Limits that can only tighten a policy, never loosen it.
  • Guardrails. Model allowlist, optional prompt capture, and PII redaction on captured logs.
  • Usage and access logs. Per-request accounting (identity, provider, model, tokens, cost) plus a full access log (method, path, status, duration, and prompt/completion when capture is on), with denied-request reasons, 7-90 day or indefinite retention, and filtering by user or group.
  • Agentic access to internal resources. Databases, internal APIs, and self-hosted models reachable over peer-to-peer WireGuard, no proxy in the path, governed by the same identities and policies.
  • Bring your own gateway. When forwarding to LiteLLM, NetBird passes the calling identity along by writing IdP groups into metadata.tags and the identity into the x-litellm-end-user-id header.

The dashboard ships copy-paste Agent Config for Claude Code, Codex, the OpenAI SDK, and cURL, with the endpoint pre-filled and no API key involved.

Enabling Agent Network

Agent Network ships in the same backend. If you already run NetBird, set an environment variable on your dashboard and it appears in the left-hand menu:

# Enable alongside the rest of the platform
NETBIRD_AGENT_NETWORK_ENABLED=true

# Or run a stripped-down, Agent-Network-only dashboard
NETBIRD_AGENT_NETWORK_ONLY=true

For a fresh, minimal deployment focused on the LLM and agentic-access use case:

curl -fsSL https://pkgs.netbird.io/getting-started.sh | NETBIRD_AGENT_NETWORK=true bash

Note: Agent Network is self-hosted only for now; NetBird Cloud support is coming.

Learn more:

What’s Changed

Agent Network

Client Improvements

Management Improvements

Infrastructure & Miscellaneous

New Contributors

  • @dmitri-netbird
  • @Adel-Ayoub
  • @den-dw

Full Changelog: Comparing v0.73.2...v0.74.0 · netbirdio/netbird · GitHub

2

I’m not sure if it was intentional, but this version broke the P2P connection. At least for me, I was unable to ping to any of my peers and constantly receiving icmp timeouts. Had to roll back to the previous version for it to work.