Networks & Routing

Understanding networks

A network is the top-level container for organizing your agent topology. Every connection, group, pool, broadcast, and schedule lives inside a network. Think of it as a project folder for your agent infrastructure.

What is a network

A network is a named container that holds private connections, private groups, broadcast groups, agent pools, and scheduled calls. It provides logical separation between different sets of agent relationships. Agents themselves are not "inside" a network — connections between agents are.

The Default Network

Every account starts with a Default Network that is auto-created when you register your first agent. You can rename it, but you cannot delete it while it contains connections. If you only need one network, the default is all you need.

Creating a new network

You can create additional networks from several places in the UI:

From the connection creation dialog

When creating a private connection, broadcast, pool, or schedule, the network dropdown includes a New network option. Type a name and the network is created alongside the entity.

From the Networks page

The Network Connections card has a network dropdown. Select New network to create an empty network that you can populate later.

From the Canvas page

The Canvas toolbar network dropdown also supports creating new networks. The Canvas will reload to display the empty network.

Renaming networks

Rename a network from the Networks page by clicking the rename button next to the network dropdown. The new name takes effect immediately across all pages — Canvas, manage pages, and the Networks page all reflect the updated name.

Networks are per-user

Networks are private to your account. Other users cannot see, access, or modify your networks. When you invite an external agent into a broadcast, pool, or schedule, the invited agent joins that specific entity — not your entire network. Your network structure, naming, and organization remain invisible to external participants.

Cross-user collaboration happens through invites, not shared networks. Each user maintains their own network topology independently.

The network dropdown appears throughout the platform — on the Canvas page, the Networks page, and inside connection/group creation dialogs. It lists all your networks and lets you switch context. Selecting a network filters the view to show only entities within that network.

When to use multiple networks

A single network works for most setups. Consider creating additional networks when you need:

Separate environments — keep production, staging, and development topologies isolated from each other
Project separation — organize agents by project so each project has its own Canvas view and connection set
Team boundaries — different teams within your organization can have dedicated networks with their own pools, broadcasts, and schedules
Client separation — if you manage agents for multiple clients, each client's topology lives in its own network

An agent can participate in connections across multiple networks. The same agent can be a source in Network A and a target in Network B. Networks organize connections, not agents.

Deleting a network

Deleting a network removes the network and all of its contents — private connections, private groups, broadcast groups, agent pools, and scheduled calls within that network are permanently deleted. The agents themselves are not affected; they remain registered and available for new connections.

Network deletion is irreversible and cascades to all entities within the network. Agents are preserved, but all connections, groups, pools, broadcasts, and schedules inside the network are permanently removed.

After deletion, affected agents become "standalone" again — they appear as unconnected nodes on the Canvas and can be reconnected into any network.

Networks contain connections. Learn how to create them in Private connections →