Map the network. Keep the map true.
Everything a team needs to put the Infrality agent on a network, read what it finds, document the estate on boards, and decide who sees what.
Start with the agent
Section titled “Start with the agent”The agent is a single binary that runs on a machine inside the network. It sweeps the segment it is told to, works out what each host is, and streams it onto a board as it goes. It only ever connects out, and it scans nothing until somebody asks it to.
How the agent worksWhat it does from start-up to a finished sweep, and what it never does.
Install itLinux, macOS and Windows: the signed installer, packages, or the bare binary.
Connect it to your organizationAn API key, a board, a range — then the first sweep from the dashboard.
Configuration referenceEvery key in config.yaml, its default, and which ones the dashboard decides.
What it sends on your networkEvery probe, every port, and the one outbound connection — for the firewall review.
TroubleshootingAn empty board, a refused key, sweeps that end Partial, hosts with no name.
Then the rest of Infrality
Section titled “Then the rest of Infrality”BoardsFolders, layers and relations, imports from thirty-odd tools, history, comments.
Access and sharingRoles, how access is decided, grants, links and restricted folders.
Administer an organizationMembers, API keys, security policy, single sign-on, SCIM and the audit trail.
ReferenceThe API, limits, a glossary, and what is not built yet.