"Snowflake powers AI, data engineering, applications, and analytics on a trusted, scalable AI Data Cloud — eliminating silos and accelerating innovation."
Snowflake Cortex Analyst is a text-to-SQL/conversational analytics service for structured data in Snowflake.
Business users can ask questions in natural language; Cortex Analyst generates SQL and provides answers without requiring end users to write SQL themselves. The feature can be integrated via REST API and relies on Semantic Views / Semantic Models, custom instructions, and verified queries for high accuracy.
Snowflake Cortex Analyst
Snowflake powers AI, data engineering, applications, and analytics on a trusted, scalable AI Data Cloud — eliminating silos and accelerating innovation
Location: USA ⓘ Snowflake, Inc., 135 Constitution Drive, Menlo Park, CA 94025, USA
Cortex Analyst API Usage Cortex Analyst can be used via REST API and is suitable for apps, dashboards, chatbots, or Streamlit applications.
Cortex AI / Cortex Search / Cortex Agents Additional Cortex features for LLM functions, search, agents, and other AI workloads; costs depend on the function, model, region, and usage.
Target audience
Snowflake Cortex Analyst is primarily aimed at companies, data platform teams, BI/analytics teams, data engineers, analytics engineers, and developers who already manage structured data in Snowflake and want to make it accessible to business units in natural language. Typical users are organizations that want to build self-service analytics, embedded analytics, or internal data assistants without unleashing a generic LLM directly on raw schemas. The product is not designed for classic consumer use.
Outstanding features
Cortex Analyst is particularly strong because of the combination of natural language with Semantic Views / Semantic Models, which cleanly define business logic, terms, metrics, and relationships. In addition, there are Custom Instructions for SQL rules and question classification, Verified Queries for improving quality, multi-turn dialogues for follow-up questions, and evaluations that allow the quality of a Semantic View to be systematically tested and improved. This makes Cortex Analyst much closer to production-ready conversational analytics than simple prompt-to-SQL approaches.
Main use cases
Cortex Analyst is especially suitable for self-service reporting, business unit analyses, revenue/sales analyses, finance and KPI queries, embedded chat interfaces in data apps, and generally for any application in which users should be able to ask questions about structured enterprise data. Via the REST API and examples with Streamlit, the function can be integrated into internal portals, dashboards, assistants, or other business applications. Cortex Search, on the other hand, is more intended for unstructured documents or knowledge search.
Usage & notes
In practice, Cortex Analyst should not be understood as a “chat on arbitrary tables,” but rather as a controlled analytics layer over well-modeled Snowflake data. For production-grade results, Semantic Views / Models, appropriate roles, stage/table permissions, and clear governance are important. Costs arise not only from Cortex Analyst itself, but additionally from SQL execution on warehouses. From a data protection perspective, it is important to deliberately choose the target region and to activate Cross-Region Inference only if this fits organizationally and legally.
| Target audience | Assessment |
|---|---|
| Data teams / BI teams | Very suitable – for natural-language questions on structured Snowflake data. |
| Business departments | Very suitable – business users can ask data questions without having to write SQL. |
| Companies with Snowflake | Very suitable – Cortex Analyst runs within the Snowflake environment and uses Snowflake governance. |
| Developers / product teams | Suitable – the REST API allows integration into custom apps, dashboards, chatbots, or Streamlit applications. |
| Private individuals / small teams without Snowflake | Not suitable – Cortex Analyst requires the Snowflake data platform and data modeling. |
| Regulated companies | Suitable to very suitable – if the Snowflake region, RBAC, governance, masking, and Cross-Region Inference are configured properly. |
Hosting & Data
1) On-prem / local hosting
Meaning: The company operates the solution on its own hardware or within its own infrastructure. In the strictest sense, not only the application runs locally, but ideally the model as well.
2) Private cloud / data center
Meaning: The solution runs in a dedicated or more clearly separated cloud environment, often with a hosting provider or hyperscaler, but in a German data center or in a particularly controlled environment.
3) EU SaaS / managed
Meaning: The provider operates the solution itself as a service. The company uses the tool as a ready-made cloud service, ideally with EU data residency.
4) Hybrid
Meaning: One part of the processing remains internal / local / in a private cloud, while another part runs in an external cloud or EU SaaS.
5) AVV / DPA
Meaning: This is the data processing agreement or Data Processing Addendum. It governs that the provider processes personal data on behalf of the customer and is bound by the customer's instructions.
6) No training
Meaning: The provider does not use your prompts, uploads, attachments, chat histories, or outputs for training or improving the general model — ideally excluded by contract.
7) Open-source / transparency path
Meaning: There is a path toward greater technical transparency and sovereignty, for example through:
- open models
- documented components
- self-hostable parts
- traceable architecture
- export / switching options
| On-prem / local hosting | ❓ |
| Private cloud / data center | ⚠️ |
| EU SaaS / Managed | ✅ |
| Hybrid | ❓ |
| DPA / AVV | ✅ |
| No training on customer data | ❓ |
| Open source / transparency path | ❓ |
On-Prem / local hosting: indirect / not available
For Cortex Analyst or Snowflake as a product, no on-premise or local self-hosting on customer-owned hardware is indicated on the website.
Private cloud / data center: partial
Snowflake describes customer-selected regions, single-region accounts, and a data residency commitment for stored data in the selected region. This suggests a segmented cloud deployment with regional control, but not classic dedicated private cloud hosting specifically for Cortex Analyst.
EU SaaS / managed: covered
Cortex Analyst is described as a fully managed service and is natively available in European regions, including AWS Frankfurt, AWS Ireland, and Azure West Europe (Netherlands). In addition, Snowflake documents EU boundaries for cross-region inference.
Hybrid: unclear
A hybrid model in the sense of partially internal/local processing and partially external processing is not specifically indicated for Cortex Analyst on the website.
DPA / Data Processing Agreement: covered
A Data Processing Addendum is available on the website. In it, Snowflake processes Customer Personal Data as a processor only for the agreed purposes and documented instructions; in addition, subprocessors rules and audit/evidence rights are described.
No training: unclear
An explicit statement on the website that prompts, uploads, chat histories, or outputs from Cortex Analyst are not used to train general models was not found. However, the privacy policy does state that usage data is used for the analysis, development, and improvement of products and services.
Open source / transparency path: indirect / not available
An open-source, self-host, or open components path for Cortex Analyst is not indicated on the website. Snowflake does mention open standards in general, but no openly self-hostable core components of Cortex Analyst.
Data processing
Snowflake operates Cortex Analyst as a managed cloud service within the Snowflake platform. Customers choose a region for their account; Snowflake documents that data is stored geographically in the selected region and lists numerous European regions. However, for Cortex Analyst and other Cortex AI features, cross-region inference is relevant: this can route requests within defined boundaries to other regions, and therefore must be deliberately configured or disabled for EU/EEA requirements. As subprocessors for hosting and infrastructure, Snowflake specifically names Amazon Web Services, Microsoft Azure, and Google Cloud Platform with customer-dependent region selection.
Conclusion
For the EU/EEA area, Snowflake Cortex Analyst is not universally, but conditionally usable. Positive aspects include EU regions, an available DPA/Data Processing Agreement, documented subprocessors, DPIA materials, and relevant certifications. Limiting factors are the documented cross-region inference as well as the lack of a clear website statement regarding a general AI training opt-out for content from Cortex Analyst. Therefore, the best justifiable classification for the European area is 'conditional'.
Sources
- https://www.snowflake.com/en/legal/privacy/privacy-policy/
- https://www.snowflake.com/en/legal/
- https://www.snowflake.com/en/legal/addenda/data-processing-addendum/
- https://www.snowflake.com/en/legal/privacy/snowflake-sub-processors/
- https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst
- https://docs.snowflake.com/en/en/user-guide/snowflake-cortex/cross-region-inference
- https://docs.snowflake.com/en/sql-reference/parameters
- https://docs.snowflake.com/en/en/user-guide/intro-regions
- https://www.snowflake.com/en/company/overview/data-boundary-roadmap-europe/
- https://docs.snowflake.com/en/user-guide/cert-iso-27001
- https://docs.snowflake.com/en/user-guide/cert-soc-2
- https://www.snowflake.com/legal-files/Snowflake-Data-Protection-Impact-Assessment-DPIA-Fact-Sheet.pdf
| On-prem / local hosting | ❓ |
| Private cloud / data center | ⚠️ |
| EU SaaS / Managed | ✅ |
| Hybrid | ❓ |
| DPA / AVV | ✅ |
| No training on customer data | ❓ |
| Open source / transparency path | ❓ |
On-Prem / local hosting: indirect / not available
For Cortex Analyst or Snowflake as a product, no on-premise or local self-hosting on customer-owned hardware is indicated on the website.
Private cloud / data center: partial
Snowflake describes customer-selected regions, single-region accounts, and a data residency commitment for stored data in the selected region. This suggests a segmented cloud deployment with regional control, but not classic dedicated private cloud hosting specifically for Cortex Analyst.
EU SaaS / managed: covered
Cortex Analyst is described as a fully managed service and is natively available in European regions, including AWS Frankfurt, AWS Ireland, and Azure West Europe (Netherlands). In addition, Snowflake documents EU boundaries for cross-region inference.
Hybrid: unclear
A hybrid model in the sense of partially internal/local processing and partially external processing is not specifically indicated for Cortex Analyst on the website.
DPA / Data Processing Agreement: covered
A Data Processing Addendum is available on the website. In it, Snowflake processes Customer Personal Data as a processor only for the agreed purposes and documented instructions; in addition, subprocessors rules and audit/evidence rights are described.
No training: unclear
An explicit statement on the website that prompts, uploads, chat histories, or outputs from Cortex Analyst are not used to train general models was not found. However, the privacy policy does state that usage data is used for the analysis, development, and improvement of products and services.
Open source / transparency path: indirect / not available
An open-source, self-host, or open components path for Cortex Analyst is not indicated on the website. Snowflake does mention open standards in general, but no openly self-hostable core components of Cortex Analyst.
Data processing
Snowflake operates Cortex Analyst as a managed cloud service within the Snowflake platform. Customers choose a region for their account; Snowflake documents that data is stored geographically in the selected region and lists numerous European regions. However, for Cortex Analyst and other Cortex AI features, cross-region inference is relevant: this can route requests within defined boundaries to other regions, and therefore must be deliberately configured or disabled for EU/EEA requirements. As subprocessors for hosting and infrastructure, Snowflake specifically names Amazon Web Services, Microsoft Azure, and Google Cloud Platform with customer-dependent region selection.
Conclusion
For the EU/EEA area, Snowflake Cortex Analyst is not universally, but conditionally usable. Positive aspects include EU regions, an available DPA/Data Processing Agreement, documented subprocessors, DPIA materials, and relevant certifications. Limiting factors are the documented cross-region inference as well as the lack of a clear website statement regarding a general AI training opt-out for content from Cortex Analyst. Therefore, the best justifiable classification for the European area is 'conditional'.
Sources
- https://www.snowflake.com/en/legal/privacy/privacy-policy/
- https://www.snowflake.com/en/legal/
- https://www.snowflake.com/en/legal/addenda/data-processing-addendum/
- https://www.snowflake.com/en/legal/privacy/snowflake-sub-processors/
- https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-analyst
- https://docs.snowflake.com/en/en/user-guide/snowflake-cortex/cross-region-inference
- https://docs.snowflake.com/en/sql-reference/parameters
- https://docs.snowflake.com/en/en/user-guide/intro-regions
- https://www.snowflake.com/en/company/overview/data-boundary-roadmap-europe/
- https://docs.snowflake.com/en/user-guide/cert-iso-27001
- https://docs.snowflake.com/en/user-guide/cert-soc-2
- https://www.snowflake.com/legal-files/Snowflake-Data-Protection-Impact-Assessment-DPIA-Fact-Sheet.pdf
Strengths & weaknesses at a glance
| Strengths | Weaknesses |
|---|---|
| • Very strong fit for self-service analytics on structured Snowflake data. | • Only suitable for structured data in Snowflake; Cortex Search is more intended for unstructured knowledge sources. |
| • API-first and therefore easy to integrate into your own apps, Streamlit, Slack, or Teams. | • A Semantic View / Semantic Model is required for good results; this demands data modeling and governance work. |
| • More precise results than generic text-to-SQL approaches thanks to Semantic Views, Verified Queries, and Custom Instructions. | • In addition to analyst usage, warehouse costs are incurred for the executed SQL queries. |
| • Clean role and access control with its own SNOWFLAKE.CORTEX_ANALYST_USER role model. | • No on-prem / local hosting; Snowflake runs entirely cloud-based. |
| • Broad edition support: Standard to VPS. | • When using Cross-Region Inference, processing may shift to other regions, which should be reviewed from a data protection perspective. |
Reviews
0 reviews in total
There are no confirmed reviews for this tool yet.
Submit review
Your review will only become visible after email confirmation. This protects the portal against abuse.
Report review
Please select the reason why this review should be checked.
GDPR-compliant usage possible?
For users in the EU/EEA, GDPR-compliant use of Snowflake Cortex Analyst is only plausibly documented under certain conditions. Positive aspects include a current AVV/DPA, documented subprocessors, EU/EEA-adjacent regions for hosting, and controllable limits for cross-region inference. At the same time, the website shows that Cortex Analyst partly uses cross-region inference and that Snowflake processes usage data for the analysis, development, and improvement of its products. Comprehensive, simple, standard GDPR compliance for every usage scenario is therefore not clearly demonstrated; it depends on the selected region, the account settings, and the contractual arrangement.
Positive
The website includes a privacy policy, a current Data Processing Addendum dated January 11, 2026, a subprocessor list, a DPIA factsheet, information on EU/EEA-suitable regions, and notes that customers can choose their data region. Snowflake also describes a data residency commitment for stored data in the selected region and mentions certifications such as ISO 27001 and SOC 2 Type II.
Negative
The website does not indicate any straightforward on-premise or self-hosting option for Cortex Analyst. For Cortex AI, cross-region inference is described; depending on the configuration, processing may therefore be routed to other regions. In addition, the privacy policy states that usage data is used for the analysis, development, and improvement of products and services. An explicit, product-specific statement on the website that prompts, uploads, chat histories, or outputs from Cortex Analyst are generally not used for model training is not provided on the website.
Server location
For Snowflake in general and for Cortex Analyst, EU/EEA-relevant regions are listed on the website, including among others AWS EU (Frankfurt) and EU (Ireland) as well as Azure West Europe (Netherlands). Snowflake also documents additional European regions for accounts and inference boundaries, such as Ireland, France, the Netherlands, Sweden, and Zurich. At the same time, it is documented that cross-region inference for Cortex AI is possible and must be separately limited or disabled.