Auvik deploys through a collector agent installed on a Windows Server or Linux host within each managed network. The collector needs outbound connectivity to Auvik's cloud platform on TCP 443 — no inbound firewall rules are required. Discovery uses SNMP community strings or SNMPv3 credentials for device polling; these credentials are entered in the Auvik interface and distributed to the collector automatically. A typical collector deployment and initial discovery cycle completes in under two hours for a standard SMB network.
SNMP credential configuration is the most common setup friction point. Devices that do not have SNMP enabled or that use non-standard community strings will show in the topology as unmanaged nodes with limited visibility.
Before deploying Auvik in a new client environment, it is worth confirming that SNMP is enabled on routers, switches, and firewalls, and that community strings or SNMPv3 credentials are documented. Auvik's device support library covers hundreds of vendor models — Cisco, Juniper, Palo Alto, Fortinet, Ubiquiti, Meraki, HP/Aruba — but device-specific monitoring depth varies by how much each vendor exposes via SNMP.
PSA integration setup requires creating an API key in the PSA platform and entering it in Auvik's integration settings. ConnectWise and Autotask integrations are the most mature — alert-to-ticket routing, company mapping (matching Auvik client to PSA company record), and configuration item sync have all been stable features. IT Glue integration syncs Auvik-discovered network devices into IT Glue documentation automatically, which is a substantial time saving for MSPs that maintain manual IT Glue device records today.