---
title: "On-prem or air-gapped deployment"
url: "https://axoflow.com/docs/axoflow/deployment-scenarios/on-prem-airgapped/"
last_modified: "2026-09-14T15:34:47+02:00"
---

> For the complete documentation index, see [llms.txt](https://axoflow.com/docs/axoflow/llms.txt).

# On-prem or air-gapped deployment

Regulated industries — finance, healthcare, government — and security-sensitive organizations often cannot send data outside their own infrastructure and cannot install software from the internet. In these environments, routing logs and telemetry through a cloud service is not an option, and internet connectivity may be restricted or entirely unavailable.

Axoflow supports fully on-premises deployments, when the [AxoConsole](https://axoflow.com/docs/axoflow/architecture/index.md#console), [AxoRouter](https://axoflow.com/docs/axoflow/architecture/index.md#router) nodes, and [Axoflow agents](https://axoflow.com/docs/axoflow/architecture/index.md#axoedge) all run inside your own datacenter. No data reaches external infrastructure, and the AxoConsole that manages the entire pipeline is also hosted on your own hardware. Air-gapped environments with no internet access are supported.

![On-premises deployment](https://axoflow.com/docs/axoflow/deployment-scenarios/on-prem-airgapped/on-prem.svg)

This approach gives you:

- Data sovereignty: all security data stays within your infrastructure. No component in the pipeline requires connectivity to Axoflow’s cloud services.
- Air-gapped support: you can deploy and operate Axoflow in environments with no internet access.
- Single management plane: the on-premises AxoConsole configures and monitors all Axoflow agents and AxoRouter nodes, giving you the same visibility and control as the SaaS offering.
- Local aggregation: AxoRouters [filter, enrich, and reduce](https://axoflow.com/docs/axoflow/concepts/classify-reduce-security-data/index.md) data before it moves between segments of your network, minimizing internal traffic.
- [Reliable transport](https://axoflow.com/docs/axoflow/concepts/reliable-transport/index.md): Axoflow uses the OpenTelemetry protocol (OTLP) between Axoflow agent and AxoRouter, so no messages are lost even under network instability.
- [Unified metrics](https://axoflow.com/docs/axoflow/metrics/index.md): every agent and router emits detailed per-component metrics, giving you end-to-end visibility into your data pipeline without leaving your perimeter.

For deployment instructions, see [On-premise](https://axoflow.com/docs/axoflow/deploy/onprem/index.md).