sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-08-25 01:01:27 +02:00
Code Issues Packages Projects Releases Wiki Activity

Clarify agent network overview

Browse Source
This commit is contained in:
braginini
2026-06-23 14:52:31 +02:00
parent 725f848db5
commit be09dba3cd
1 changed files with 11 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
src/pages/agent-network/index.mdx
View File

@@ -3,10 +3,14 @@ import { Note } from '@/components/mdx'
export const description =
'Agent Network is NetBird\'s control layer for AI agents — a keyless gateway to LLM APIs and scoped, identity-based access to your internal resources, all over the tunnel with per-identity policies, limits, and audit.'
# NetBird Agent Network
# What is NetBird Agent Network?
Agent Network is NetBird's access control layer for AI agents. It gives every agent a
real identity, tied to your identity provider (IdP), and governs what it can reach:
As AI spreads across organizations, humans, agents, tools, and workflows need access to LLM APIs
and internal systems. Too often, that access relies on shared API keys and broad network paths, creating credential
sprawl, weak identity, poor visibility, and limited control over cost, usage, and what each agent can reach.
Agent Network is NetBird's access control layer for AI agents and the people who run them. It gives every agent a
real identity, tied to an identity provider (IdP), and governs what it can reach:
LLM APIs and AI gateways it can call, and the internal resources it can access. Traffic
flows only over the encrypted NetBird tunnel, scoped by policy, with no API keys or other credentials
to leak.
@@ -59,10 +63,10 @@ define exactly which resources it can reach, just like any other NetBird peer in
It’s common for organizations to rely on a centralized identity provider like Okta, Microsoft Entra ID, Google, or others.
It’s also common for IT teams to manage access to internal resources while keeping costs under control.
Traditionally, IT has done this through the internal network, using VPNs to give employees access to databases, web servers,
Traditionally, IT has done this through the internal network, using ZTNA or VPNs to give employees access to databases, web servers,
internal APIs, and other private services.
AI agents should be treated the same way: as another trusted entity on the network. They need secure access to
AI agents should be treated the same way: as another entity accessing the network. They need secure access to
internal resources, and modern enterprise resources now include LLMs and API endpoints alongside traditional infrastructure.
That makes agent access a natural responsibility for IT.
@@ -71,4 +75,5 @@ their enterprise stack with minimal changes.
## Next steps
- [Quickstart](/agent-network/quickstart). Deploy NetBird Agent Network and make your first routed LLM call.
- [Quickstart](/agent-network/quickstart). Deploy NetBird Agent Network and make your first routed LLM call.
- [How Agent Network Works](/agent-network/how-it-works). Understand the core concepts and architecture of Agent Network.