netbird/agent-network at main · netbirdio/netbird · GitHub
//files/disambiguate" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
//files/disambiguate;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading. Please reload this page.
netbirdio
netbird
Public
Uh oh!
There was an error while loading. Please reload this page.
Notifications<br>You must be signed in to change notification settings
Fork<br>1.5k
Star<br>26.9k
FilesExpand file tree
main
/agent-network<br>Copy path
Directory actions
More options<br>More options
Directory actions
More options<br>More options
Latest commit
History<br>History<br>History
main
/agent-network<br>Copy path
Top
Folders and files<br>NameNameLast commit message<br>Last commit date<br>parent directory<br>..<br>README.md
README.md
View all files
README.md<br>Outline<br>NetBird Agent Network
Agent Network is NetBird's access control layer for AI agents and the people who run them.<br>It gives every agent a real identity, tied to an identity provider (IdP), and governs what it can reach: LLM APIs and<br>AI gateways it can call, and the internal resources it can access. Traffic flows only over the encrypted NetBird tunnel,<br>scoped by policy, with no API keys or other credentials to leak. It also gives you control over cost and token usage.
Because every LLM request passes through an<br>identity-aware proxy, you can:
Set spending and rate limits per agent, per user, or per team — with hard caps<br>that stop requests once a budget is reached.
Restrict models and providers so agents can only call approved (and cost-appropriate)<br>endpoints, keeping expensive models off-limits unless explicitly allowed.
Attribute usage by tracking token consumption and cost per identity, group, or cost center so every<br>request is tied back to the agent and person responsible.
Reuse your existing AI gateway — point the proxy at a gateway you already run,<br>keeping its routing and config in place while it adds identity on top, so you skip<br>API key distribution.
ScreenRecording2026-07-08at16.38.51-ezgif.com-video-speed.mov
Beta. Agent Network is in beta, but it's stable and already running in<br>production environments. It's fully open source and can be self-hosted on your own<br>infrastructure, with no vendor lock-in and no data leaving your environment.
How it works
Say you have a simple use case: your Engineering or IT team needs access to Claude Code or Codex, and you want visibility into usage plus the ability to enforce budgets.<br>How can you do that without creating a dedicated API key for every team?
With Agent Network you get a private endpoint inside your network, for example: https://mirror.netbird.ai<br>Teams configure their agents to point to that endpoint instead of using individual API keys directly.
This endpoint is only reachable when users are connected to your NetBird network and authenticated through your IdP. Otherwise, it is not accessible from the public internet.<br>You can then use this private endpoint to configure your AI agents, whether that is Claude Code, Codex, or another tool.
Quickstart
Full step-by-step setup:<br>https://docs.netbird.io/agent-network/quickstart
Architecture
Agent Network is built on two existing NetBird capabilities:
Overlay network — the encrypted WireGuard mesh between peers.
Reverse proxy — a NetBird peer that terminates LLM requests, establishes the<br>caller's identity, evaluates policies/limits/guardrails, injects the upstream provider<br>key server-side, forwards to the API or gateway, and records usage.
LLM traffic is routed through the proxy's identity-aware pipeline, while internal<br>resources (databases, internal APIs, self-hosted models) are reached directly over<br>peer-to-peer WireGuard tunnels, governed by the same identities and access policies.
Where the code lives
There is no separate "agent-network" service — it reuses the reverse-proxy and management<br>components:
proxy/ — the NetBird reverse proxy that serves the agent network endpoint<br>and runs the per-request middleware pipeline.
management/internals/modules/reverseproxy/<br>— the management-side control plane: providers, policies, guardrails, limits, routing,<br>and usage/access logs.
Documentation
Full documentation, architecture, and...