Nautobot extends the NetBox heritage with a richer plugin ecosystem
and automation hooks. Netos treats it the same way — as a peer SoT
that already holds authoritative model data.
What Netos ingests
Sites, regions, devices, racks, and circuits
Custom fields, relationships, and tags as first-class attributes
Job and ChatOps results where useful as lifecycle evidence
Configuration context relevant for lifecycle reasoning
Use cases
Extend a Nautobot-based SoT into FinOps and lifecycle analytics
Use Nautobot Jobs as the change layer beneath Netos planning
Carry plugin-rich metadata into reporting without losing fidelity
