Edge deployments
This page explains Axiom’s edge deployment architecture and how to control where your event data is stored.
Axiom is a unified data platform built on edge deployments.
When you create an organization, you choose a primary edge deployment like US East 1 (AWS), and your event data is stored at rest in that infrastructure. You manage everything through Axiom’s Console at app.axiom.co regardless of which edge deployment you select.
This edge deployment model provides flexibility that isn’t possible with separate regional instances. Within a single organization, you can create datasets in different edge deployments while maintaining unified management and billing.
Available edge deployments
Axiom currently supports the following edge deployments:
| Edge deployment | Base domain for ingest and query |
|---|---|
US East 1 (AWS) | us-east-1.aws.edge.axiom.co |
EU Central 1 (AWS) | eu-central-1.aws.edge.axiom.co |
Axiom prioritizes new edge deployments based on interest. Contact Axiom to discuss your requirements.
Current capabilities
Your organization’s default edge deployment determines where Axiom stores event data at rest and where queries execute. When you run a query, both the execution and results remain within your selected edge deployment.
| Operation | Behavior |
|---|---|
| Data ingest | Selected edge deployment |
| Data storage | Selected edge deployment |
| Query execution | Selected edge deployment |
| Query results | Selected edge deployment |
| Account data | US infrastructure |
When you select an edge deployment, event data is ingested, stored, and queried entirely within that edge deployment. Query results are returned directly from the edge without routing through other infrastructure. Account management operations (user settings, billing, organization configuration) are processed through Axiom’s centralized US infrastructure.
Compliance considerations
Axiom’s edge deployment architecture supports data-sovereignty requirements by keeping event data ingestion, storage, query execution, and query results within your selected edge deployment. This architecture is designed to meet frameworks that require both storage and processing of data to take place entirely within a designated region.
Account management operations (user authentication, billing, organization settings) are processed through Axiom’s centralized US infrastructure. Evaluate whether this meets your specific compliance requirements. For most data-sovereignty frameworks, the critical factor is where event data is stored and processed, which remains entirely within your selected edge deployment.
Determine your organization’s edge deployment
In multi-region organizations, you can specify the edge deployment for each dataset. This means that you can select where Axiom stores your event data when creating a new dataset. You can't change the edge deployment of a dataset after creating the dataset.
The default edge deployment of your organization is the option automatically selected when you create a new dataset. You can’t change your default edge deployment after creating your organization.
To determine your organization’s default edge deployment:
- Click Settings > General.
- Find your organization’s default edge deployment in the Edge deployment section.
Multi-edge organizations
To create datasets in an edge deployment other than your organization’s default edge deployment:
- Buy the add-on associated with the new edge deployment.
- When you create a new dataset, select the new edge deployment.
SDKs and edge deployments
Axiom SDKs will support edge deployments through environment variables. The SDKs will default to US East 1 (AWS). Until Axiom updates all SDKs, configure ingest endpoints manually.
Axiom-hosted MCP server
The Axiom-hosted MCP Server is located in the US. When you query your data using the Axiom MCP Server using a remote MCP connection, query results are routed through US infrastructure.
For more information, see Axiom MCP Server.