From df8d39191da70d5f0950b102d0e5718ebe73745a Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Mon, 24 Nov 2025 14:54:53 +0100 Subject: [PATCH 1/9] Fix links --- docs.json | 2 +- reference/cli.mdx | 2 +- reference/edge-deployments.mdx | 4 ++-- reference/organization-settings.mdx | 2 +- restapi/introduction.mdx | 2 +- send-data/syslog-proxy.mdx | 2 +- snippets/replace-domain.mdx | 2 +- snippets/replace-edge-domain.mdx | 2 +- 8 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs.json b/docs.json index 7aa7a90bc..eaab37ba2 100644 --- 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 index ff5e5a38f..ecc105e92 100644 --- 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 index e147ffb27..f8fd8bf33 100644 --- a/reference/edge-deployments.mdx +++ b/reference/edge-deployments.mdx @@ -23,7 +23,7 @@ Axiom currently supports the following edge deployments for data ingest: All other API operations use `https://api.axiom.co` as the base domain. -New edge deployments are prioritized based on interest. [Contact us](https://www.axiom.co/contact) to discuss your requirements. +New edge deployments are prioritized based on interest. [Contact Axiom](https://www.axiom.co/contact) to discuss your requirements. ## Current capabilities @@ -89,4 +89,4 @@ These instances had independent user accounts, billing systems, and API endpoint 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. -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. \ No newline at end of file +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. diff --git a/reference/organization-settings.mdx b/reference/organization-settings.mdx index e8da31115..e2e68805a 100644 --- a/reference/organization-settings.mdx +++ b/reference/organization-settings.mdx @@ -17,7 +17,7 @@ import AiSetting from "/snippets/ai-setting.mdx" 1. Click 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/restapi/introduction.mdx b/restapi/introduction.mdx index a707d8b63..4b8ae4abe 100644 --- a/restapi/introduction.mdx +++ b/restapi/introduction.mdx @@ -51,7 +51,7 @@ The base domain of an API request depends on the following: - 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 index 783c08464..b5b14b227 100644 --- 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/replace-domain.mdx b/snippets/replace-domain.mdx index 3f138f339..3c6b19cb5 100644 --- 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). \ No newline at end of file +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 index cc11523df..ca13202db 100644 --- 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). From 04838183cbc3d0bc5469cac9cc43b720959b218b Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Mon, 24 Nov 2025 15:30:47 +0100 Subject: [PATCH 2/9] Review edge deployments --- reference/edge-deployments.mdx | 54 ++++++++++++++++++---------------- 1 file changed, 28 insertions(+), 26 deletions(-) diff --git a/reference/edge-deployments.mdx b/reference/edge-deployments.mdx index f8fd8bf33..f1f4a452c 100644 --- 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'] --- @@ -20,49 +20,51 @@ Axiom currently supports the following edge deployments for data ingest: -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`. -New edge deployments are prioritized based on interest. [Contact Axiom](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** | Your selected edge deployment | Same edge deployment where data is stored | +| **Data storage** | Your selected edge deployment | Same edge deployment where data is stored | +| **Query execution** | Your selected edge deployment | Same edge deployment where data is stored | +| **Query results** | US infrastructure | Same edge deployment where data is stored | | **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. +This means that 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). +Some data-sovereignty frameworks 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 don’t 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 data locality. -### 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 Settings icon **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 -Jan 2026 [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. +Jan 2026 [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 +### Within-edge query execution Jan 2026 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. @@ -70,15 +72,15 @@ Axiom is evolving its edge deployment architecture to provide more flexibility a 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. -## 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. From 52ca25461203a75c507365f895c5aca45d0f1ef9 Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Tue, 25 Nov 2025 12:10:48 +0100 Subject: [PATCH 3/9] Update edge-deployments.mdx --- reference/edge-deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/edge-deployments.mdx b/reference/edge-deployments.mdx index f1f4a452c..5940bb111 100644 --- a/reference/edge-deployments.mdx +++ b/reference/edge-deployments.mdx @@ -39,7 +39,7 @@ See the table below for current and planned behavior: | **Query results** | US infrastructure | Same edge deployment where data is stored | | **Account data** | US infrastructure | - | -This means that 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. +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 From d1e77eb18e06423f0776c3c05c5715b50d7e22ec Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Tue, 25 Nov 2025 12:29:07 +0100 Subject: [PATCH 4/9] Fix table --- reference/edge-deployments.mdx | 2 +- snippets/base-domains.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/reference/edge-deployments.mdx b/reference/edge-deployments.mdx index 5940bb111..fcda15048 100644 --- a/reference/edge-deployments.mdx +++ b/reference/edge-deployments.mdx @@ -15,7 +15,7 @@ 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: diff --git a/snippets/base-domains.mdx b/snippets/base-domains.mdx index 345aec59f..bacfd4fd4 100644 --- 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` | \ No newline at end of file From 1c830bdd0f31d7fac9f84c046460577df826c4a1 Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Wed, 26 Nov 2025 09:06:05 +0100 Subject: [PATCH 5/9] Fix icon --- reference/edge-deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/edge-deployments.mdx b/reference/edge-deployments.mdx index fcda15048..3dc6ed735 100644 --- a/reference/edge-deployments.mdx +++ b/reference/edge-deployments.mdx @@ -53,7 +53,7 @@ The default edge deployment of your organization determines where Axiom stores y To determine your organization’s default edge deployment: -1. Click Settings icon **Settings > General**. +1. Click **Settings > General**. 1. Find your organization’s default edge deployment in the **Edge deployment** section. ## Roadmap for edge deployments From 915f40f64fbd2d8e7dd616a20b1ccb1d96886bff Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Wed, 26 Nov 2025 10:54:47 +0100 Subject: [PATCH 6/9] Implement review --- reference/edge-deployments.mdx | 8 +-- reference/regions-archiveme.mdx | 98 --------------------------------- 2 files changed, 4 insertions(+), 102 deletions(-) delete mode 100644 reference/regions-archiveme.mdx diff --git a/reference/edge-deployments.mdx b/reference/edge-deployments.mdx index 3dc6ed735..a30f64e31 100644 --- a/reference/edge-deployments.mdx +++ b/reference/edge-deployments.mdx @@ -33,9 +33,9 @@ See the table below for current and planned behavior: | Operation | Current behavior | Planned behavior | | :--- | :--- | :--- | -| **Data ingest** | Your selected edge deployment | Same edge deployment where data is stored | -| **Data storage** | Your selected edge deployment | Same edge deployment where data is stored | -| **Query execution** | Your selected edge deployment | Same edge deployment where data is stored | +| **Data ingest** | Your default edge deployment | Same edge deployment where data is stored | +| **Data storage** | Your default edge deployment | Same edge deployment where data is stored | +| **Query execution** | Your default edge deployment | Same edge deployment where data is stored | | **Query results** | US infrastructure | Same edge deployment where data is stored | | **Account data** | US infrastructure | - | @@ -45,7 +45,7 @@ Currently, if you select a non-US edge deployment, event data is ingested and st Some data-sovereignty frameworks accommodate this architecture when supported by appropriate transfer mechanisms (for example, SCCs). -Strict public-sector or regulated-industry frameworks don’t 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 data locality. +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 results. ### Determine your organization’s edge deployment diff --git a/reference/regions-archiveme.mdx b/reference/regions-archiveme.mdx deleted file mode 100644 index d6caa0e9d..000000000 --- a/reference/regions-archiveme.mdx +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: 'Regions' -description: 'This page explains how to work with Axiom’s unified multi-region platform.' ---- - -import BaseDomains from "/snippets/base-domains.mdx" - -Axiom is available in multiple regions to help you comply with data residency requirements and optimize performance. - -## Towards a unified multi-region platform - -Axiom is rolling out support for a unified platform where a single organization can manage datasets across multiple regions. This will give you complete control to decide where your data is stored and processed. - -### Current capabilities - -- You choose the default region when you create a new organization. -- You can choose from two available regions: US and EU. Support additional regions is coming soon. -- You can’t change the default region after creating the organization. -- Axiom stores the data you ingest in the default region of your organization. -- When you run a query, the query executes in your region, but Axiom routes the query results through the US region. This means that when you query data stored the EU region, the query results leave the EU region. - -The current implementation is useful if you want to ingest data to the EU region, but your query results can leave the EU region. If your organization has data sovereignty requirements that are stricter than the current implementation, Axiom recommends waiting for the next phase of the rollout before migrating. - -### Roadmap - -Axiom rolls out its unified multi-region platform in phases. This approach ensures you can migrate when the capabilities align with your specific data residency requirements. - -1. Complete data locality (coming soon) - - - Axiom routes query results through the same region where data is stored. - - Monitor and dashboard operations respect organization region boundaries. - - Full compliance with regional data protection requirements (for example, GDPR). - - In this phase, if your organization requires EU data sovereignty, you’ll be able to migrate with confidence. - -1. Unified multi-region platform (in development) - - - One organization managing datasets across multiple geographic regions. - - Choose a default region for your organization, add regions to your organization, and configure individual datasets to store data in one of your regions. - - Unified billing covering all your regions. - - In this phase, regions function as self-contained units that coexist within one organization while preserving data sovereignty guarantees. - -Axiom routes some of your personal data (for example, email and name when you log in) through US servers, and this won’t change in the rollout of the multi-region platform. - -Your view can help shape this roadmap. [Contact Axiom](https://www.axiom.co/contact) if you need a region that’s not currently supported or if you have any other suggestions. - -## Available regions - -Axiom currently supports the following cloud regions for data ingest: - - - - -The base domain of all other API endpoints is `https://api.axiom.co`. - - -## Determine default region - -The default region of your organization determines where Axiom stores your data. - -To determine your organization’s default region: - -1. Click Settings icon **Settings > General**. -1. Find your organization’s default region in the **Region** section. - -## Choose region - -When you create a new organization, choose the region that best meets your data residency requirements and where your infrastructure is located for optimal performance. - -When choosing a region, consider the following factors: - -- **Data residency requirements**: If you need to comply with regulations like GDPR that require data to be stored in specific regions, choose the appropriate region. -- **Performance**: Choose the region closest to your infrastructure for lower latency. -- **Team location**: Choose the region that your team is primarily located in for better performance. - -## Legacy infrastructure - -Until November 2025, Axiom operated separate infrastructures for two dedicated regional instances: - -| Instance | Base domain of Axiom Console | Base domain of API endpoints | -| ---------- | ------------------------------ | ----------------------- | -| US | `https://app.axiom.co` | `https://api.axiom.co` | -| EU | `https://app.eu.axiom.co` | `https://api.eu.axiom.co` | - -Each instance was entirely independent with separate: -- Organizations and user accounts -- Billing and subscription plans -- API endpoints and ingestion URLs -- Data storage and query infrastructure - -### Migration from legacy EU instance - -The unified multi-region model is rolling out progressively. If your organization currently uses the legacy EU instance, Axiom will contact you about the opportunity to migrate to the unified platform. - - -All examples in the Axiom API reference use the base domain `https://api.axiom.co`, which is the default for the legacy US instance. If your organization uses the legacy EU instance, use the base domain `https://api.eu.axiom.co` until Axiom migrates your organization to the unified platform. - From 41986498c50e01e03f7f1c5859c8cf5f24553953 Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Wed, 26 Nov 2025 11:12:40 +0100 Subject: [PATCH 7/9] Update edge-deployments.mdx --- reference/edge-deployments.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/reference/edge-deployments.mdx b/reference/edge-deployments.mdx index a30f64e31..674203e64 100644 --- a/reference/edge-deployments.mdx +++ b/reference/edge-deployments.mdx @@ -45,7 +45,7 @@ Currently, if you select a non-US edge deployment, event data is ingested and st Some data-sovereignty frameworks 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 results. +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. ### Determine your organization’s edge deployment @@ -64,7 +64,7 @@ Axiom is evolving its edge deployment architecture to provide more flexibility a Jan 2026 [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 Jan 2026 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. From 4d2c60f11aa2e281ae4be0384e2678d720fc180e Mon Sep 17 00:00:00 2001 From: Mano Toth Date: Wed, 26 Nov 2025 11:19:06 +0100 Subject: [PATCH 8/9] Revert to simpler table --- reference/edge-deployments.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/reference/edge-deployments.mdx b/reference/edge-deployments.mdx index 674203e64..f43db7c78 100644 --- a/reference/edge-deployments.mdx +++ b/reference/edge-deployments.mdx @@ -33,10 +33,10 @@ See the table below for current and planned behavior: | Operation | Current behavior | Planned behavior | | :--- | :--- | :--- | -| **Data ingest** | Your default edge deployment | Same edge deployment where data is stored | -| **Data storage** | Your default edge deployment | Same edge deployment where data is stored | -| **Query execution** | Your default edge deployment | Same edge deployment where data is stored | -| **Query results** | US infrastructure | Same edge deployment where data is stored | +| **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 | - | 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. From 6f95857e5cbd2432251e325a2c4bee6eb5b61010 Mon Sep 17 00:00:00 2001 From: Mano Toth <71388581+manototh@users.noreply.github.com> Date: Wed, 26 Nov 2025 11:26:28 +0100 Subject: [PATCH 9/9] Update reference/edge-deployments.mdx --- reference/edge-deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/edge-deployments.mdx b/reference/edge-deployments.mdx index f43db7c78..1d5526bf9 100644 --- a/reference/edge-deployments.mdx +++ b/reference/edge-deployments.mdx @@ -43,7 +43,7 @@ Currently, if you select a non-US edge deployment, event data is ingested and st ### Compliance considerations -Some data-sovereignty frameworks accommodate this architecture when supported by appropriate transfer mechanisms (for example, SCCs). +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 complete within-edge query processing.