Deployment scenarios

Sample architectures for inserting AxoRouter into your existing data pipeline, and for deploying Axoflow agents or onboarding your existing log collectors.

Thanks to its flexible deployment modes, you can quickly insert an Axoflow and its processing node (called AxoRouter) transparently into your data pipeline and gain instant benefits:

  • Data reduction
  • Improved SIEM accuracy
  • Configuration UI for routing data
  • Automatic data classification
  • Metrics about log ingestion, processing, and data drops
  • Analytics about the transported data
  • Health check, highlighting anomalies

After the first step, you can further integrate your pipeline, by deploying Axoflow agents to collect and manage your security data, or onboarding your existing log collector agents (for example, syslog-ng). Let’s see what these scenarios look like in detail.


AxoConsole deployment

Use AxoConsole as a SaaS service, or deploy it on premises in your own environment.

Transparent router mode

Deploy AxoRouter in front of your SIEM, and point your sources to it to get classification, parsing, enrichment, and metrics.

Router and edge deployment

Collect data with Axoflow agents on Kubernetes, Linux, and Windows hosts, and send it to AxoRouter for processing.

AxoRouter high availability

Deploy multiple AxoRouter instances in a high availability cluster, either behind a load balancer or sharing a virtual IP managed by keepalived.

Onboard existing syslog/syslog-ng infrastructure

Bring an existing syslog or syslog-ng architecture into Axoflow with managed or unmanaged AxoRouter instances, or in read-only mode.

Multi-cloud and multi-datacenter scenario

Collect security data from several cloud providers and datacenters with local agents and Cloud Connectors, and manage it from one place.

On-prem or air-gapped deployment

Run AxoConsole, AxoRouter, and the Axoflow agents inside your own datacenter, without sending data or metrics outside.