axiomhq · manototh · Nov 26, 2025 · Nov 24, 2025 · Nov 24, 2025 · Nov 25, 2025
diff --git a/docs.json b/docs.json
@@ -1040,7 +1040,7 @@
     },
     {
       "source": "/reference/eu-domain",
-      "destination": "/reference/regions"
+      "destination": "/reference/edge-deployments"
     },
     {
       "source": "/reference/sharing",

diff --git a/reference/cli.mdx b/reference/cli.mdx
@@ -72,7 +72,7 @@ The easiest way to start using Axiom CLI is by logging in through the command li
 
 While most users will only need to manage a single Axiom deployment, Axiom CLI provides the capability to switch between multiple organizations for those who require it. You can easily switch between organizations using straightforward CLI commands. For example, `axiom auth switch-org` lets you change your active organization, or you can set the `AXIOM_ORG_ID` environment variable for the same purpose.
 
-Every setting in Axiom CLI can be overwritten via environment variables configured in the `~/.axiom.toml` file. Specifically, `AXIOM_URL`, `AXIOM_TOKEN`, and `AXIOM_ORG_ID` are important for configuring your environment. Set `AXIOM_URL` to your Axiom domain. For more information, see [Regions](/reference/regions). You can switch between environments using the `axiom auth select` command.
+Every setting in Axiom CLI can be overwritten via environment variables configured in the `~/.axiom.toml` file. Specifically, `AXIOM_URL`, `AXIOM_TOKEN`, and `AXIOM_ORG_ID` are important for configuring your environment. Set `AXIOM_URL` to your Axiom domain. For more information, see [Edge deployments](/reference/edge-deployments). You can switch between environments using the `axiom auth select` command.
 
 To view available environment variables, run `axiom help environment` for an up to date list of env vars:
 

diff --git a/reference/edge-deployments.mdx b/reference/edge-deployments.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Edge deployments'
+title: Edge deployments
 description: 'This page explains Axiom’s edge deployment architecture and how to control where your event data is stored.'
 keywords: ['eu', 'regions', 'edge', 'deployment']
 ---
@@ -15,70 +15,72 @@ This edge deployment model provides flexibility that isn’t possible with separ
 
 ## Available edge deployments
 
-Axiom currently supports the following edge deployments for data ingest:
+Axiom currently supports the following edge deployments:
 
 <BaseDomains />
 
 <Note>
-All other API operations use `https://api.axiom.co` as the base domain.
+The base domain of all other API endpoints is `https://api.axiom.co`.
 </Note>
 
-New edge deployments are prioritized based on interest. [Contact us](https://www.axiom.co/contact) to discuss your requirements.
+Axiom prioritizes new edge deployments based on interest. [Contact Axiom](https://www.axiom.co/contact) to discuss your requirements.
 
 ## Current capabilities
 
-Your organization’s default edge deployment determines where event data is stored at rest. Query execution and account operations currently route through centralized infrastructure, which will change as edge deployment capabilities expand.
+Your organization’s default edge deployment determines where Axiom stores event data at rest. Axiom currently routes query results and account operations through its centralized US-based infrastructure. In the future, Axiom will route query results in the same edge deployment where your data is stored.
 
-| Operation | Current behavior | Evolution |
+See the table below for current and planned behavior:
+
+| Operation | Current behavior | Planned behavior |
 | :--- | :--- | :--- |
-| **Data ingest** | Your selected edge deployment | - |
-| **Data storage** | Your selected edge deployment | - |
-| **Query execution** | Your selected edge deployment | - |
-| **Query results** | US infrastructure | Planned to move to regional edge deployment  |
+| **Data ingest** | Selected edge deployment | – |
+| **Data storage** | Selected edge deployment | – |
+| **Query execution** | Selected edge deployment | – |
+| **Query results** | US infrastructure | Selected edge deployment |
 | **Account data** | US infrastructure | - |
 
-**Non-US edge deployments:** Event data is ingested and stored in your chosen edge deployment. When you run a query through Axiom’s Console, API, or monitors, that query will currently execute in US infrastructure. Your event data remains stored in your chosen edge deployment, but query processing involves cross-edge access to that data.
+Currently, if you select a non-US edge deployment, event data is ingested and stored in your selected edge deployment. When you run a query through Axiom’s Console, API, or monitors, that query executes in your selected edge deployment, but the query results are routed through the US infrastructure. Your event data remains stored in your chosen edge deployment, but query processing involves cross-edge access to that data.
 
 ### Compliance considerations
 
 Some data-sovereignty frameworks may accommodate this architecture when supported by appropriate transfer mechanisms (for example, SCCs).
 
-Strict public-sector or regulated-industry frameworks might not permit cross-border processing. This is typically because these frameworks require that both storage and processing of personal data take place entirely within the designated edge. Evaluate based on your specific requirements. If your compliance obligations prohibit query results from crossing regional boundaries, wait for within-edge query execution.
+Strict public-sector or regulated-industry frameworks might not permit cross-border processing. This is typically because these frameworks require that both storage and processing of personal data take place entirely within the designated edge. Evaluate based on your specific requirements. If your compliance obligations prohibit query results from crossing regional boundaries, wait for complete within-edge query processing.
 
-### Check your organization’s edge deployment
+### Determine your organization’s edge deployment
 
-To see which edge deployment your organization uses:
+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.
 
-1. In the Axiom console, go to **Settings > General**
-2. Look for the **Edge deployment** field
+To determine your organization’s default edge deployment:
 
-You can’t currently change your edge deployment after creating your organization.
+1. Click <Icon icon="gear" iconType="solid"/> **Settings > General**.
+1. Find your organization’s default edge deployment in the **Edge deployment** section.
 
-## What’s coming
+## Roadmap for edge deployments
 
 Axiom is evolving its edge deployment architecture to provide more flexibility and control.
 
-#### Integration support
+### Integration support
 
-<Badge>Jan 2026</Badge> [Integrations](/apps/introduction) like Vercel, Netlify, and Cloudflare Logpush will include edge deployment selection in their setup flows, automatically routing ingest to the correct edge endpoint based on your dataset configuration. Until then, choose `US East 1 (AWS)` to access these integrations.
+<Badge>Jan 2026</Badge> [Integrations](/apps/introduction) will be available for edge deployments other than `US East 1 (AWS)`. The integrations will include edge deployment selection in their setup flows, automatically routing ingest to the correct edge endpoint based on your dataset configuration.
 
-#### Within-edge query execution
+### Complete within-edge query processing
 
 <Badge>Jan 2026</Badge> Query processing will move to regional edge deployments. For example, when you query data stored in an EU edge deployment, the entire operation, from query execution to results, will happen within EU infrastructure.
 
 ### Multi-region organization
 
 <Badge>Q1 2026</Badge> 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.
 
-## SDKs and edge deployments
+### SDKs and edge deployments
 
-Axiom SDKs will support edge deployments through environment variables. These SDKs will default to `US East 1 (AWS)`. Until SDK updates are made, please manually configure ingest endpoints.
+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.
 
 ## Legacy EU instance
 
 Axiom had previously operated two completely separate infrastructures to support an EU region:
 
-| Instance | Console | API endpoint | 
+| Instance | Console base domain | API endpoint base domain | 
 | :--- | :--- | :--- | 
 | US | `https://app.axiom.co` | `https://api.axiom.co` | 
 | EU | `https://app.eu.axiom.co` | `https://api.eu.axiom.co` | 
@@ -87,6 +89,6 @@ These instances had independent user accounts, billing systems, and API endpoint
 
 ### Migration to edge deployments
 
-If your organization currently uses `app.eu.axiom.co`, Axiom will contact you directly about migration once within-region query execution becomes available. The migration will move your data to the new unified model while preserving your dataset contents.
+If your organization currently uses the legacy EU instance, Axiom will contact you directly about migration after within-region query execution becomes available. 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 `api.axiom.co` by default. If you’re on the legacy EU instance, substitute `api.eu.axiom.co` in all API calls.
+Until migration, continue using your current EU instance endpoints. All API examples in Axiom’s documentation use the `https://api.axiom.co` base domain by default. If you’re on the legacy EU instance, replace this with the `https://api.eu.axiom.co` base domain in all API calls.
diff --git a/reference/organization-settings.mdx b/reference/organization-settings.mdx
@@ -17,7 +17,7 @@ import AiSetting from "/snippets/ai-setting.mdx"
 1. Click <img src="/doc-assets/icons/settings.svg" className="inline-icon" alt="Settings icon" /> **Settings > General**.
 1. Find organization region in the **Region** section.
 
-For more information, see [Regions](/reference/regions).
+For more information, see [Edge deployments](/reference/edge-deployments).
 
 ## Turn Axiom AI on or off
 

diff --git a/reference/regions-archiveme.mdx b/reference/regions-archiveme.mdx
diff --git a/restapi/introduction.mdx b/restapi/introduction.mdx
@@ -51,7 +51,7 @@ The base domain of an API request depends on the following:
 
     <BaseDomains />
 
-    For more information on regions, see [Regions](/reference/regions).
+    For more information on regions, see [Edge deployments](/reference/edge-deployments).
 
 - For all other API endpoints, use the base domain `https://api.axiom.co`.
 

diff --git a/send-data/syslog-proxy.mdx b/send-data/syslog-proxy.mdx
@@ -88,7 +88,7 @@ Set the following environment variables to connect to Axiom:
 
 - `AXIOM_TOKEN` is the Axiom API token you have generated.
 - `AXIOM_DATASET` is the name of the Axiom dataset where you want to send data.
-- Optional: `AXIOM_URL` is the URL of the Axiom API. By default, it uses the US region. Change the default value if your organization uses another region. For more information, see [Regions](/reference/regions).
+- Optional: `AXIOM_URL` is the URL of the Axiom API. By default, it uses the US region. Change the default value if your organization uses another region. For more information, see [Edge deployments](/reference/edge-deployments).
 
 ## Run Axiom Syslog Proxy
 

diff --git a/snippets/base-domains.mdx b/snippets/base-domains.mdx
@@ -1,4 +1,4 @@
-| Edge deployment | Base domain |
+| Edge deployment | Base domain of ingest API endpoint |
 | :--- | :--- |
 | `US East 1 (AWS)` | `https://us-east-1.aws.edge.axiom.co` |
 | `EU Central 1 (AWS)` | `https://eu-central-1.aws.edge.axiom.co` |
diff --git a/snippets/replace-domain.mdx b/snippets/replace-domain.mdx
@@ -1 +1 @@
-Replace `AXIOM_DOMAIN` with `api.axiom.co` if your organization uses the US region. For more information, see [Regions](/reference/regions).
+Replace `AXIOM_DOMAIN` with `api.axiom.co` if your organization uses the US region. For more information, see [Edge deployments](/reference/edge-deployments).
diff --git a/snippets/replace-edge-domain.mdx b/snippets/replace-edge-domain.mdx
@@ -1 +1 @@
-Replace `AXIOM_EDGE_DOMAIN` with `https://us-east-1.aws.edge.axiom.co` if your organization uses the US region, and with `https://eu-central-1.aws.edge.axiom.co` if your organization uses the EU region. For more information, see [Regions](/reference/regions).
+Replace `AXIOM_EDGE_DOMAIN` with `https://us-east-1.aws.edge.axiom.co` if your organization uses the US region, and with `https://eu-central-1.aws.edge.axiom.co` if your organization uses the EU region. For more information, see [Edge deployments](/reference/edge-deployments).
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		Replace `AXIOM_DOMAIN` with `api.axiom.co` if your organization uses the US region. For more information, see [Regions](/reference/regions).
		Replace `AXIOM_DOMAIN` with `api.axiom.co` if your organization uses the US region. For more information, see [Edge deployments](/reference/edge-deployments).
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		Replace `AXIOM_EDGE_DOMAIN` with `https://us-east-1.aws.edge.axiom.co` if your organization uses the US region, and with `https://eu-central-1.aws.edge.axiom.co` if your organization uses the EU region. For more information, see [Regions](/reference/regions).
		Replace `AXIOM_EDGE_DOMAIN` with `https://us-east-1.aws.edge.axiom.co` if your organization uses the US region, and with `https://eu-central-1.aws.edge.axiom.co` if your organization uses the EU region. For more information, see [Edge deployments](/reference/edge-deployments).