Per-site Collector (the default)
Each site has one Collector on its local AV VLAN, which reaches devices over the LAN. Each site’s firewall allows outbound HTTPS only.Shared central Collector
One Collector, at head office or in a data centre, reaches every site’s AV VLAN over your corporate WAN.Hybrid
Each major site runs its own Collector, and a central Collector serves the smaller regional offices.Cloud-hosted Collector
The Collector runs in your own cloud tenant (AWS, Azure or Google Cloud). It reaches your sites over your existing private connectivity: site-to-site VPN, AWS Direct Connect, Azure ExpressRoute or Google Cloud Interconnect.Which one is right for you?
Do you already run workloads in a particular cloud tenant?- Yes: deploy the Collector in that tenant. Use your existing Kubernetes platform (see Run on Kubernetes) or the cloud’s managed container option (see Run on a managed container platform).
- No: deploy on-premises.
- One site, or several sites on a reliable WAN: use a shared central Collector.
- Many sites with separate AV VLANs and no reliable link between them: use a Collector at each site.
- A mix of both: use the hybrid pattern.
- Native services: Linux (see Install on Linux) or Windows Server (see Install on Windows Server).
- Docker, without Kubernetes: Docker (see Run with Docker) or a managed container platform (see Run on a managed container platform).
- Kubernetes: a
Deploymentin your cluster (see Run on Kubernetes).
Updated 23 Oct 2026 15:20 · page a6ecd46