What the v0.1 collector does today
A plain list of what the native v0.1 collector supports right now versus what is designed but not yet active, and what the DEV build badge means.
Updated Aug 24, 2026Product v0.14 minMSP operator, Internal IT, Platform admin, Developer
Overview
The native collector is at v0.1. This article is the single source of truth for what it actually does today, so other collector articles that describe the longer-term design are not mistaken for current behavior.
Supported today
- Enrollment, heartbeat and observation reporting to the AssurIQ control plane over the API v1 endpoints
- Explicit CIDR-based scan scopes with exclusions and blocked targets
- Conservative TCP-connect discovery of hosts and their common open ports within the approved scope
- Windows x64 and Linux x64 native builds
Not active yet
- SNMP discovery and polling
- LLDP/CDP neighbor-protocol topology building
- ARP or ICMP sweep-based discovery
- Credentialed scanning (WinRM or SSH)
- Vulnerability probes
- Banner grabbing
- Docker/container image (roadmap)
- ARM64 packages and a hardened VM/appliance form factor (roadmap)
Discovery method is always tcp_connect and scan scopes are always discovery_only: credentialed is not offered by the current server or collector.
What the DEV badge means
Windows and Linux v0.1 builds are unsigned and shown with a DEV badge until code signing is in place. A DEV build is functionally the same binary that will later be signed, but operating systems and endpoint protection may warn about or block an unsigned executable, and it should not be treated as production-hardened.
Was this helpful?