Concepts
How Retivo is built and how its parts relate: nodes, devices, groups, versions, matching, rules and roles.
The pages in this section explain the ideas behind Retivo. Read them when you want to know why something behaves the way it does; for step-by-step instructions, see Tasks.
Architecturedash.retivo.net, the Retivo Node, and what is stored where.Devices and groupsHow devices inherit settings from groups, nested groups and rule-based groups.CredentialsThe kinds of credential sets, where they are used and how they are protected.Config versionsWhen Retivo saves a new version, what it ignores, and how comparing and restoring work.Vulnerability matchingWhere the data comes from, how a CVE is matched to a device, and how the recommended upgrade is chosen.ComplianceService checks for Telnet, SSH, HTTP and HTTPS, and your own config rules.Roles and permissionsRoles on the node, the six permissions, group-limited access and superadmins.Accounts and sign-inCompanies, users, email codes, Microsoft Entra ID, Active Directory and verified domains.