Skip to main content
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. As Axiom introduces additional edge deployments, you’ll be able to write event data to specific locations with ease while maintaining unified management and billing.

Available edge deployments

Axiom currently supports the following edge deployments:
Edge deploymentBase 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
The base domain of all other API endpoints is api.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.
OperationBehavior
Data ingestSelected edge deployment
Data storageSelected edge deployment
Query executionSelected edge deployment
Query resultsSelected edge deployment
Account dataUS 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

The default edge deployment of your organization determines where Axiom stores your event data. You can’t change your default edge deployment after creating your organization. To determine your organization’s default edge deployment:
  1. Click Settings > General.
  2. Find your organization’s default edge deployment in the Edge deployment section.

Roadmap for edge deployments

Axiom is evolving its edge deployment architecture to provide more flexibility and control.

SDK support

Feb 2026
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.

Integrations

The following integrations support edge deployments other than US East 1 (AWS): These integrations send data to your organization’s default edge deployment automatically, without any additional configuration.
Axiom is working on adding support for all edge deployments to more integrations.

Multi-edge organization

Q1 2026
You’ll be able to manage datasets across multiple edge deployments within a single organization. After selecting a default edge deployment, you can activate additional edge deployments and configure individual datasets to store data in any active edge deployment. This enables global operations without managing multiple Axiom organizations.

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.

Legacy EU instance

Axiom had previously operated two completely separate infrastructures to support an EU region:
InstanceConsole base domainAPI endpoint base domain
USapp.axiom.coapi.axiom.co
EUapp.eu.axiom.coapi.eu.axiom.co
These instances had independent user accounts, billing systems, and API endpoints. In time, this EU instance will be retired in favor of flexible edge deployments.

Migration to edge deployments

If your organization currently uses the legacy EU instance, Axiom will contact you directly about migration. The migration will move your data to the new unified model, keeping your data intact. Until migration, continue using your current EU instance endpoints. All API examples in Axiom’s documentation use the api.axiom.co base domain by default. If you’re on the legacy EU instance, replace this with the api.eu.axiom.co base domain in all API calls.