Build your first inventory

Start with the topology you know, then let discovery fill in observations. A small, accurate inventory is more useful than a large speculative one.

1. Complete initial administration

If the database has no root user, the login screen offers bootstrap setup only when bootstrap-token is set under server.services.web-api.authentication in app-server/config.yml. Use a long random value, create the administrator, then remove the token from configuration.

2. Create a site

A site is the top-level operational boundary for a location. Give it a durable name such as Home, Workshop, or Branch Amsterdam; avoid names tied to a temporary router or ISP.

3. Add a network

Record the network CIDR, gateway, and VLAN information you actually use. Attach the network to its site. Add address pools if you need to distinguish DHCP ranges, static allocations, or reserved space.

4. Record known infrastructure

Add stable devices and servers first: routers, switches, access points, hypervisors, storage, and other infrastructure. Connect their interfaces and IP addresses so searches lead back to useful context. Record application listeners on those devices, then group them into logical services when you need an operator-facing view.

5. Add an agent when useful

An agent can observe a network from the inside and execute jobs requested by the server. Treat its findings as observed data to review, rather than automatically replacing intentional inventory.

Next, read Sites, networks, and addresses, learn the inventory model, or follow the discovery review workflow.