---
title: "Multi-cloud and multi-datacenter scenario"
url: "https://axoflow.com/docs/axoflow/0.86/deployment-scenarios/multi-cloud/"
last_modified: "2026-09-14T15:34:47+02:00"
---

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

# Multi-cloud and multi-datacenter scenario

Organizations running workloads across multiple cloud providers (AWS, Azure, GCP) and private datacenters face a common challenge: each environment produces security and observability data in different formats, volumes, and locations, making it hard to collect, [normalize](https://axoflow.com/docs/axoflow/0.86/concepts/normalization/index.md), and route it consistently.

Axoflow is designed for exactly this scenario. You deploy [Axoflow agents](https://axoflow.com/docs/axoflow/0.86/architecture/index.md#axoedge) and [Axoflow Cloud Connectors](https://axoflow.com/docs/axoflow/0.86/architecture/index.md#axoedge) close to your data sources in each cloud and datacenter. The agents forward data to one or more [AxoRouter](https://axoflow.com/docs/axoflow/0.86/architecture/index.md#router) nodes, which you can place per region to minimize egress costs, or centralize for simpler operations.

![Multi-cloud and multi-datacenter deployment](https://axoflow.com/docs/axoflow/0.86/deployment-scenarios/multi-cloud/multi-datacenter-deployment_hu_925e13126b781f85.webp)

This approach gives you:

- Single management plane: You configure and monitor all Axoflow agents and AxoRouter nodes from the AxoConsole, regardless of which cloud or datacenter they run in.
- Local aggregation: AxoRouters automatically [filter, enrich, and reduce](https://axoflow.com/docs/axoflow/0.86/concepts/classify-reduce-security-data/index.md) data before forwarding it, so you only pay cross-cloud or cross-datacenter egress for the data that matters.
- [Reliable transport](https://axoflow.com/docs/axoflow/0.86/concepts/reliable-transport/index.md): Axoflow uses the OpenTelemetry protocol (OTLP) between components (Axoflow agent to AxoRouter and Axoflow Cloud Connector to AxoRouter), so no messages are lost when crossing network boundaries between environments.
- [Unified metrics](https://axoflow.com/docs/axoflow/0.86/metrics/index.md): Every agent and router emits detailed per-component metrics, so you have end-to-end visibility into your data pipeline across all environments.
- Flexible routing: You can route data to environment-specific [destinations](https://axoflow.com/docs/axoflow/0.86/destinations/index.md) (for example, a regional [SIEM](https://axoflow.com/docs/axoflow/0.86/destinations/index.md) or local archive) or aggregate it centrally — or both — using [policy-based routing](https://axoflow.com/docs/axoflow/0.86/concepts/policy-based-routing/index.md).