:::meta author=Docs-Team updated=2026-09-03 tags=networks,docker,isolated
:::
:::breadcrumb Docs > User Guide > Networks
:::
:::reading-time
:::
Networks are the private Docker networks your services run in. Grouping services into the same network lets them talk to each other by container name while staying isolated from everything else — a typical setup is one network per environment or per application stack. The Networks page manages the networks themselves; every service picks its network at creation and can move between yours at any time.
:::toc
:::
The page
The header shows the hub icon, the title Networks, the subtitle "Private Docker networks for your services", and the two actions: Refresh and Create network. Result alerts confirm actions or explain failures — including the guard message "Cannot delete a network that still has connected services."
| Column | Contents |
| --- | --- |
| Name | The network's name |
| Description | Free text, shown dimmed, — when empty |
| Services | A chip counting connected services — blue when non-zero, grey when empty |
| Actions | Edit and Delete |
Deleting a network with services attached is blocked twice: the delete button is disabled with the tooltip "Detach services before deleting", and even a forced attempt is refused by the backend. Move the services to other networks first (or delete them), then delete the network — the confirm dialog states the finality plainly.
Creating and editing
The Create network / Edit network dialog has two fields — Name (required, autofocus) and Description (optional, multiline) — with Cancel and Create / Save buttons. There is nothing else to configure: addressing is handled by the platform, and the service count column updates automatically as services attach and detach.
:::tip
Use the description to record intent — "production stack for shop-api + worker" reads much better than a bare name a year later, and it is visible right in the table.
:::
How services use networks
A service references exactly one network. You manage that relation from three places, all of which offer inline creation so you never have to detour:
:::tabs
=== Creation wizard
The Network step lists your networks as radio cards and includes the Or create network form; a fresh network is created and selected in one action.
=== Service settings
The Network section of the service's Settings tab (or its Edit dialog on the services list) shows the currently attached network with Detach, plus Show all networks (N) to attach another.
=== Settings dialog
The same cards with Current and Selected chips let you re-point the service and save — the change applies on save.
:::
:::note
Networks are per-account resources: services you own share your networks, and share recipients operate the service but never reorganize your network library. The Change network share rule governs who may re-point a shared service.
:::
Common setups
:::steps
• Create one network per environment
e.g. production and staging — the Services column then becomes a live map of what runs where.
• Attach services during creation
The wizard pre-selects nothing, so pick deliberately — or create the network inline right there.
• Reorganize from the service side
Moving a service later is a settings change, not a redeploy; the container joins the new network on its next start.
• Clean up safely
Empty networks are deletable in one click; attached ones tell you exactly what blocks them.
:::