Data handling & AI governance · Reliability and controls
Which BI tools let you control where AI inference runs?
3 of 15 tools do, according to their public docs, and 10 partly.
Yes: Omni, Sigma, Metabase. Partly: Databricks, Snowflake, Hex, BigQuery, Looker, Tableau, Power BI, Alteryx, MotherDuck, Redshift.
The question we asked: Can the customer control where model inference occurs?
The customer controls where inference occurs. A model running in the customer's cloud, warehouse or tenant earns yes; a documented choice of region or provider endpoint, or a bring-your-own-key path where the documentation says where the provider processes the request, earns partly. Vendor-hosted inference that the documentation says the customer cannot choose or move earns no. Supplying a key does not by itself say where inference runs, and documentation that only states where processing happens, with no customer choice, belongs to the residency row. A choice that applies to only some of the product's AI features is partly.
Databricks
Quoted from Databricks’s docsAdmins can choose to disable the partner-powered AI features setting. When the setting is disabled, Databricks AI assistive features use Databricks-hosted models where available, or are disabled entirely.
Snowflake
Quoted from Snowflake’s docsYou control the routing behavior through a single account-level parameter, CORTEX_ENABLED_CROSS_REGION, choosing the option that best fits your performance, compliance, and data residency requirements.
Omni
Quoted from Omni’s docsSnowflake Cortex provides access to industry-leading large language models (LLMs) hosted directly within your Snowflake infrastructure.
Hex
Quoted from Hex’s docsWith BYOK, Admins can supply their own credentials so that inference runs through your organization's provider account instead.
Sigma
Quoted from Sigma’s docs To connect to an AI model hosted by your data platform, see Configure a warehouse-hosted model as AI provider. When you choose the option to configure a warehouse-hosted model, your data is managed fully in your data platform.
BigQuery
Quoted from BigQuery’s docsFor most Gemini in BigQuery features, the Gemini processing location can be controlled by an administrator by using the Global Default Location setting at the project or organization level.
Looker
Quoted from Looker’s docsThis option enables data processing within the EU jurisdiction and allows Looker's Conversational Analytics traffic to be routed through an EU multi-regional endpoint, which ensures EU customer data is processed within the EU.
Tableau
Quoted from Tableau’s docsUnlike Tableau Cloud, in Tableau Server AI in Tableau connects directly from your Tableau Server deployment to the selected LLM provider or via a custom gateway (version 2026.3 and later).
Power BI
Quoted from Power BI’s docsIf you're okay with your data being handled outside of your area, switch on the setting Data sent to Azure OpenAI can be processed outside your capacity's geographic region, compliance boundary, or national cloud instance, and select Apply.
Metabase
Quoted from Metabase’s docsSet this when a self-hosted vLLM server is on your private network (allow-private) or on this machine (allow-all).
Alteryx
Quoted from Alteryx’s docsThese features connect to a large language model (LLM) – by default, this LLM is accessed via an Alteryx instance within Microsoft Azure Cognitive Services; however, you can instead use an LLM in your own Microsoft Azure Cognitive Services tenant.
MotherDuck
Quoted from MotherDuck’s docsWhere model inference runs depends on your organization's cloud region.
Redshift
Quoted from Redshift’s docsWith bring your own model (BYOM), you can use a model trained outside of Amazon Redshift with Amazon SageMaker AI for in-database inference locally in Amazon Redshift.
Mode
Streamlit