Snowflake vs Databricks

Agent ops

1. ai-native userMy agent can run governed SQL end to end — authenticate, discover schemas, query, and read results back through a CLI or API with no dashboard in the loop

   weight 3 · round drawn
   Snowflake✓fullprobed8/10

   Snowflake provides multiple governed, non-dashboard paths for an agent to run SQL end-to-end: the SQL API (REST) for authenticating and executing queries/managing objects, the Snowflake CLI for programmatic access, RBAC/access history for governance, and a Snowflake-managed MCP server that lets agents securely retrieve data and execute SQL as tools without deploying infrastructure. missing for 10: independent/hands-on third-party validation of the full agent workflow (auth→discover→query→read-results) via CLI/API/MCP, and explicit documentation of schema-discovery APIs (e.g., information_schema access) tied directly to the MCP/SQL API flow.

   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access History in Snowflake refers to when the user query reads data and when the SQL statement performs a data write operation... The user …”
   • [probe] “official MCP server documented at https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp”
   • [probe] “official CLI documented at https://docs.snowflake.com/en/developer-guide/snowflake-cli/index”

   proof ↗⚑ flag

   Databricks✓fullprobed8/10

   Databricks documents a full non-UI path: CLI/API authentication (databricks-docs-2/48/64), schema and object discovery governed by Unity Catalog accessible via CLI/SQL/REST (databricks-docs-56, 19, 38, 70, 75), SQL execution via the Databricks SQL API/CLI (databricks-supp-api-versioning, databricks-docs-32), and reading results back programmatically (workspace REST API reference, databricks-docs-65), with runtime evidence that the CLI actually installs and exposes a raw `databricks api` wrapper keylessly (databricks-probe-rt-1). Missing for 10: an end-to-end documented/hands-on example chaining auth→discover→query→result specifically for an agent (no single walkthrough), and no independent corroboration of the full flow outside vendor docs.

   • [claimed-docs] “The Databricks CLI (command-line interface) allows you to interact with the Databricks platform from your local terminal or automation scrip…”
   • [claimed-docs] “allows you to interact with the Databricks platform from your local terminal or automation scripts”
   • [claimed-docs] “You work with the objects Unity Catalog governs through Catalog Explorer, SQL, the Databricks CLI, and REST APIs.”
   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [claimed-docs] “Data and AI assets such as tables, views, volumes, functions, models, and services (model services and MCP services) follow a three-level na…”
   • [claimed-docs] “It runs directly on your data lake, supports ANSI SQL with Delta Lake extensions, and provides the tools to build highly performant, cost-ef…”
   • [claimed-docs] “Docs, "Update to the latest Databricks SQL API version": "The legacy API is deprecated and support will end soon. Use this page to migrate y…”
   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI installed via the vendor's brew tap and printed `Databricks CLI v1.15.0` keylessly; …”

   proof ↗⚑ flag

2. ai-native userA built-in AI assistant writes, fixes, and explains SQL against my schemas from natural language, inside the product

   weight 2 · round to Databricks
   Snowflake~partialclaimed7/10

   Cortex Analyst is a built-in, documented Snowflake feature that lets users ask questions in natural language and get answers 'without writing SQL,' implying it generates and runs SQL against the user's schema inside Snowsight; Cortex AI Functions and Notebooks further support SQL/Python assistance in-product. However, the evidence never explicitly shows the assistant 'fixing' or 'explaining' existing SQL (vs. generating it from scratch), and there's no independent/hands-on corroboration of accuracy or workflow beyond first-party docs. Missing for 10: explicit fix/explain-SQL capability documentation, and independent/community validation of the NL-to-SQL experience.

   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs from OpenAI, Anthropic, Met…”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs”
   • [claimed-docs] “Write SQL or Python code and quickly compare results with cell-by-cell development and execution.”
   • [claimed-docs] “Snowflake Notebooks is a unified development interface in Snowsight that offers an interactive, cell-based programming environment for Pytho…”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Databricks documents a built-in AI assistant (Genie/Genie Code) that writes, debugs, and explains code and queries directly inside notebooks/SQL editor against Unity Catalog tables, columns, and lineage, plus a separate Genie conversational analytics surface for asking natural-language data questions grounded in org data. This is native, in-product functionality (not a bolt-on), covering SQL generation, fixing errors, and natural-language explanation/answers over schemas. Missing for 10: independent/hands-on third-party verification of SQL-writing accuracy and no explicit example transcript showing it explaining SQL syntax step-by-step.

   • [claimed-docs] “Genie Code is the AI coding and data assistant for developers and technical practitioners in the Databricks workspace.”
   • [claimed-docs] “Write and run SQL queries with integrated AI assistance, code comments, and version history.”
   • [claimed-docs] “Ask data questions in natural language and get answers grounded in your organization's data.”
   • [claimed-docs] “It generates and runs code, builds pipelines and AI/BI dashboards, debugs errors, and works directly with Unity Catalog tables, columns, and…”
   • [claimed-docs] “Chat with Genie Code, get inline suggestions, and run agentic tasks in your workspace.”
   • [claimed-docs] “Run Genie Code as an autonomous agent that plans, runs code, fixes errors, and asks for approval before it uses tools.”
   • [claimed-docs] “It generates and runs code, builds pipelines and AI/BI dashboards, debugs errors, and works directly with Unity Catalog tables, columns, and…”
   • [claimed-docs] “From natural language dashboard creation to deep conversational analytics with Genie, this is BI built on AI from the start.”

   proof ↗⚑ flag

3. ai-native userBusiness users can ask questions in natural language and get governed, semantically-grounded answers rather than hallucinated joins

   weight 1 · round to Databricks
   Snowflake✓fullclaimed7/10

   Snowflake's Cortex Analyst is documented to let business users ask natural-language questions and get direct answers without writing SQL, and Snowflake Semantic Views let teams define business metrics/entities as governed semantic layer objects that Cortex Analyst can ground against, with RBAC controlling access to underlying data. This directly matches the story's ask for governed, semantically-grounded NL answers rather than raw hallucinated joins. missing for 10: independent/hands-on evidence validating accuracy or hallucination-reduction claims, and no detail on how Cortex Analyst explicitly enforces the semantic model to prevent bad joins (only first-party docs, no third-party corroboration).

   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object. You can define busines…”
   • [claimed-docs] “You can define business metrics and model business entities and their relationships.”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View ... define business metrics and model business entities…”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Genie provides natural language Q&A grounded in organizational data (docs-8, docs-22, docs-57), backed by Unity Catalog governance enforcing access control and lineage (docs-19, docs-38) and metric views providing a semantic layer so metrics are defined once and computed consistently rather than via ad-hoc joins (docs-7, docs-16, docs-42, docs-72). Business-user-focused Genie One interface is explicitly documented for non-technical users (docs-57). missing for 10: independent/hands-on evidence of Genie's accuracy avoiding hallucinated joins in practice, and no community corroboration of semantic grounding quality specifically (community evidence pack is generic platform commentary, not about Genie/semantic layer).

   • [claimed-docs] “Ask data questions in natural language and get answers grounded in your organization's data.”
   • [claimed-docs] “From natural language dashboard creation to deep conversational analytics with Genie, this is BI built on AI from the start.”
   • [claimed-docs] “Navigate the Genie One interface designed for business users. View dashboards, ask natural language data questions, and discover assets shar…”
   • [claimed-docs] “you define the metric once, for example _sum of revenue divided by distinct customer count_, and users can group by any available field.”
   • [claimed-docs] “you define the metric once, for example sum of revenue divided by distinct customer count, and users can group by any available field”
   • [claimed-docs] “Define business metrics with consistent calculations using a semantic layer. Reuse metrics across queries and dashboards.”
   • [claimed-docs] “you define the metric once, for example sum of revenue divided by distinct customer count, and users can group by any available field. The q…”
   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Snowflake
   Snowflake✓fullprobed9/10

   Snowflake publishes a root llms.txt (confirmed via live probe, HTTP 200) summarizing the platform, plus dedicated llms.txt files for individual products like Snowpark, Streamlit, and Snowflake Postgres, giving agents a structured, agent-oriented entry point into the docs. missing for 10: independent/third-party confirmation that agents successfully consume these llms.txt files in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.snowflake.com/llms.txt # Snowflake Documentation > Snowflake is a cloud data platform providing da…”
   • [claimed-docs] “Snowpark API for Python, Java, and Scala — process data at scale inside Snowflake.”
   • [claimed-docs] “Build and deploy interactive Streamlit apps directly inside Snowflake.”
   • [claimed-docs] “Managed Postgres instances running directly inside Snowflake.”

   proof ↗⚑ flag

   Databricks✓fullprobed8/10

   Databricks hosts an llms.txt file (probe confirms HTTP 200 with a structured documentation index) and also ships agent-oriented skill docs (SKILL.md files installable via `databricks aitools install`) that agents can be pointed at, going beyond a bare llms.txt. missing for 10: no independent third-party report of an agent successfully consuming llms.txt or the skills in practice, and no evidence of an /llms-full.txt or deeper machine-readable agent doc index.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.databricks.com/llms.txt # Databricks Documentation > Comprehensive documentation for the Databricks…”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI SHIPS vendor agent skills — `databricks aitools install --path /tmp/pa-dbx-skills` k…”
   • [claimed-docs] “Genie Code is the AI coding and data assistant for developers and technical practitioners in the Databricks workspace.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Snowflake✓fullprobed8/10

   Snowflake ships an official CLI for managing apps/workloads and REST APIs (SQL API and Resource Management API) explicitly designed for programmatic, non-interactive integration and automation, which are the standard mechanisms for running Snowflake operations headlessly in CI pipelines. missing for 10: explicit CI/CD pipeline examples (e.g., GitHub Actions integration) and documentation of non-interactive auth flows (key-pair/OAuth) tailored for headless automation.

   • [claimed-docs] “With Snowflake CLI, developers can create, manage, update, and view apps running on Snowflake across workloads such as Streamlit in Snowflak…”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [probe] “official CLI documented at https://docs.snowflake.com/en/developer-guide/snowflake-cli/index”

   proof ↗⚑ flag

   Databricks✓fullprobed8/10

   Databricks provides a documented, keylessly-installable CLI supporting scripting/automation of workspace, jobs, and Lakeflow pipelines (databricks-docs-2, databricks-docs-48, databricks-probe-rt-1), plus REST APIs and Python SDK explicitly for automating operations (databricks-docs-49, databricks-docs-65), enabling headless/CI use for orchestrating pipelines, jobs, and ML training. Jobs/pipelines can be triggered/orchestrated without UI interaction, matching CI automation needs. Missing for 10: no explicit CI/CD pipeline integration guide (e.g., GitHub Actions) or independent case study confirming CI usage beyond docs and CLI probes.

   • [claimed-docs] “The Databricks CLI (command-line interface) allows you to interact with the Databricks platform from your local terminal or automation scrip…”
   • [claimed-docs] “allows you to interact with the Databricks platform from your local terminal or automation scripts”
   • [claimed-docs] “you learn how to automate Databricks operations and accelerate development with the Databricks SDK for Python”
   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI installed via the vendor's brew tap and printed `Databricks CLI v1.15.0` keylessly; …”
   • [claimed-docs] “Develop and deploy your first ETL (extract, transform, and load) pipeline for data orchestration with Apache Spark™.”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Databricks
   Snowflake—none0/10

   Evidence documents Snowflake's own MCP server that exposes Snowflake's Cortex tools to external AI agents (server-side), but there is no evidence Snowflake can act as an MCP client consuming external MCP servers' tools to extend Cortex Agents or CoWork/CoCo's capabilities.

   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to”
   • [probe] “official MCP server documented at https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp”

   proof ↗⚑ flag

   Databricks✓fullprobed8/10

   Databricks documents connecting agents to external, managed, and custom MCP servers (docs-45, docs-50, docs-71) and using their tools/third-party SaaS integrations (docs-31, docs-43), plus a Marketplace listing MCP servers for discovery (docs-34/69). This directly matches the story of plugging in MCP servers to gain tool access. Missing for 10: independent/hands-on community confirmation of the MCP-client integration working end-to-end (only vendor docs, no third-party validation).

   • [claimed-docs] “Wire up Claude, Cursor, MCP Inspector, and other external clients to MCP servers hosted on Databricks.”
   • [claimed-docs] “Discover, authenticate to, and call managed, MCP Service, and custom MCP servers from your agent code, then deploy the agent on Databricks A…”
   • [claimed-docs] “Give your agent governed access to third-party and SaaS tools such as Slack, GitHub, Google Drive, Google Calendar, and Gmail — through buil…”
   • [claimed-docs] “Create AI agent tools using Unity Catalog functions, including third-party integrations and code interpreter tools.”
   • [claimed-docs] “Listings include datasets, AI models, notebooks, apps, and Model Context Protocol (MCP) servers.”
   • [probe] “official MCP server documented at https://docs.databricks.com/aws/en/agents/mcp-tools”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Snowflake
   Snowflake✓fullprobed9/10

   Snowflake documents an official, Snowflake-managed MCP server (Cortex Agents MCP) that lets AI agents securely retrieve data without deploying separate infrastructure, and it can be configured to serve Cortex Analyst, Cortex Search, Cortex Agents, custom tools, and SQL execution as MCP tools. This is a first-party, GA-documented feature confirmed by a direct probe of the docs URL. Missing for 10: independent/hands-on third-party corroboration of real-world agent connections beyond vendor docs.

   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to”
   • [probe] “official MCP server documented at https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp”

   proof ↗⚑ flag

   Databricks✓fullprobed8/10

   Databricks documents official MCP server support extensively: it hosts managed/custom MCP servers as Databricks Apps, exposes Unity Catalog functions as MCP tools, provides built-in system.ai MCP Services for third-party SaaS tools, and explicitly supports wiring external clients (Claude, Cursor, MCP Inspector) to MCP servers hosted on Databricks; Marketplace also lists MCP servers as discoverable assets. Missing for 10: independent/hands-on third-party verification of the MCP connection flow (only first-party docs available).

   • [claimed-docs] “Host a custom MCP server as a Databricks app to expose your own tools.”
   • [claimed-docs] “Give your agent governed access to third-party and SaaS tools such as Slack, GitHub, Google Drive, Google Calendar, and Gmail”
   • [claimed-docs] “Create AI agent tools using Unity Catalog functions, including third-party integrations and code interpreter tools.”
   • [claimed-docs] “Wire up Claude, Cursor, MCP Inspector, and other external clients to MCP servers hosted on Databricks.”
   • [claimed-docs] “Discover, authenticate to, and call managed, MCP Service, and custom MCP servers from your agent code, then deploy the agent on Databricks A…”
   • [claimed-docs] “Listings include datasets, AI models, notebooks, apps, and Model Context Protocol (MCP) servers. This gives customers a single catalog for f…”
   • [claimed-docs] “Give your agent governed access to third-party and SaaS tools such as Slack, GitHub, Google Drive, Google Calendar, and Gmail — through buil…”
   • [probe] “official MCP server documented at https://docs.databricks.com/aws/en/agents/mcp-tools”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Databricks
   Snowflake✓fullprobed8/10

   Snowflake ships an official Snowflake CLI documented for creating, managing, updating, and viewing apps across Streamlit, Native Apps, Snowpark Container Services, and Snowpark, confirmed by a dedicated docs probe. It's a general developer CLI rather than one purpose-built for AI-native/agentic workflows specifically. Missing for 10: independent/hands-on corroboration of CLI usage, and explicit agentic-workflow-specific CLI features (vs. general app management).

   • [claimed-docs] “With Snowflake CLI, developers can create, manage, update, and view apps running on Snowflake across workloads such as Streamlit in Snowflak…”
   • [claimed-docs] “developers can create, manage, update, and view apps running on Snowflake across workloads”
   • [claimed-docs] “developers can create, manage, update, and view apps running on Snowflake across workloads such as Streamlit in Snowflake, the Snowflake Nat…”
   • [probe] “official CLI documented at https://docs.snowflake.com/en/developer-guide/snowflake-cli/index”

   proof ↗⚑ flag

   Databricks✓fullprobed9/10

   Databricks ships an official CLI (docs, migration guides, REST wrapper) confirmed by hands-on runtime probe (v1.15.0), and it is explicitly AI-native: the CLI ships an `aitools install` subcommand that installs vendor agent skills (SKILL.md files) for Claude Code, Codex, Cursor, Copilot, etc. missing for 10: independent/community corroboration beyond the vendor docs and runtime probe.

   • [claimed-docs] “The Databricks CLI (command-line interface) allows you to interact with the Databricks platform from your local terminal or automation scrip…”
   • [claimed-docs] “allows you to interact with the Databricks platform from your local terminal or automation scripts”
   • [claimed-docs] “To migrate from Databricks CLI version 0.18 or below to Databricks CLI version 0.205 or above, see Databricks CLI migration.”
   • [probe] “official CLI documented at https://docs.databricks.com/aws/en/dev-tools/cli/”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI installed via the vendor's brew tap and printed `Databricks CLI v1.15.0` keylessly; …”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI SHIPS vendor agent skills — `databricks aitools install --path /tmp/pa-dbx-skills` k…”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Databricks
   Snowflake✓fullprobed8/10

   Snowflake documents a public REST API for resource management and a SQL API (both OpenAPI-compliant with an official spec repo and Postman collections) allowing programmatic querying, deployment management, and integration building, plus Snowpark APIs for Python/Java/Scala. This is well-documented first-party evidence of a documented public API surface usable by AI-native/automated clients. Missing for 10: independent hands-on developer corroboration of API robustness/limits, and a discoverable machine-readable openapi.json at the probed standard paths (probe returned 404s despite claims of OpenAPI compliance).

   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.snowflake.com/openapi.json, https://docs.snowflake.com/swagger.json, https://docs.snowf…”

   proof ↗⚑ flag

   Databricks✓fullprobed9/10

   Databricks publishes a documented REST API reference (workspace-level APIs, versioned Jobs/SQL APIs with request/response examples), plus CLI, SDKs (Python), and Databricks Connect that all wrap this public API for automation and agentic use, and this is corroborated by a runtime probe confirming a working CLI with a raw `databricks api` REST wrapper. Missing for 10: a live interactive API try-it console or independent third-party API-quality corroboration beyond vendor docs.

   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”
   • [claimed-docs] “API reference hub lists versioned REST APIs side by side, e.g. "Jobs v2.0 API — REST API reference for version 2.0 version of the Jobs REST …”
   • [claimed-docs] “API reference (docs.databricks.com/api): "This reference describes the types, paths, and any request payload or query parameters, for each s…”
   • [claimed-docs] “allows you to interact with the Databricks platform from your local terminal or automation scripts”
   • [claimed-docs] “you learn how to automate Databricks operations and accelerate development with the Databricks SDK for Python”
   • [claimed-docs] “Just like a JDBC driver, the Databricks Connect library can be embedded in any application to interact with Databricks.”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI installed via the vendor's brew tap and printed `Databricks CLI v1.15.0` keylessly; …”
   • [probe] “official CLI documented at https://docs.databricks.com/aws/en/dev-tools/cli/”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Snowflake
   Snowflake~partialclaimed5/10

   Snowflake's RBAC system lets admins scope privileges to specific roles that can then be attached to service/API credentials, and its REST APIs plus the Cortex Agents MCP server explicitly support secure, credential-based programmatic access for AI agents. However, no evidence directly documents an agent-specific credential-issuance workflow (e.g., short-lived scoped tokens purpose-built for agent identities) — the story is inferred from general RBAC/API docs rather than an agent-specific credentialing feature. Missing for 10: explicit documentation of issuing least-privilege, agent-scoped API keys/tokens (vs. general RBAC/roles), and any hands-on/independent confirmation of this workflow.

   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to”

   proof ↗⚑ flag

   Databricks~partialclaimed4/10

   Databricks documents Unity Catalog governance that enforces access control on data/AI assets and lets agents get 'governed access' to third-party tools via Unity Catalog functions and MCP services (docs-19, 38, 70, 71, 43), implying a permissions model that could scope agent access. However, there is no explicit documentation of an API/credential-issuance mechanism (e.g., scoped service-principal tokens or OAuth scopes specifically for agents) described as 'least-privilege API credentials for an agent.' Missing for 10: explicit credential/token issuance workflow scoped to an agent identity, documentation of OAuth/service-principal scoping granularity, and any hands-on or independent confirmation that credentials can be narrowly scoped per-agent.

   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [claimed-docs] “Give your agent governed access to third-party and SaaS tools such as Slack, GitHub, Google Drive, Google Calendar, and Gmail — through buil…”
   • [claimed-docs] “Create AI agent tools using Unity Catalog functions, including third-party integrations and code interpreter tools.”
   • [claimed-docs] “Data and AI assets such as tables, views, volumes, functions, models, and services (model services and MCP services) follow a three-level na…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Databricks
   Snowflake✓fullprobed7/10

   Snowflake documents multiple official SDKs/APIs for developers—Snowpark API for Python, Java, and Scala, the Snowflake SQL API, and REST APIs for resource management with OpenAPI specifications hosted in an official GitHub repo—plus a managed MCP server letting AI agents interact with Snowflake without custom infrastructure, directly supporting AI-native build patterns. Missing for 10: independent/hands-on developer corroboration of SDK quality/ergonomics and more explicit agent-framework integration examples beyond MCP.

   • [claimed-docs] “Snowpark API for Python, Java, and Scala — process data at scale inside Snowflake.”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”
   • [probe] “official MCP server documented at https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp”

   proof ↗⚑ flag

   Databricks✓fullprobed9/10

   Databricks publishes official SDKs (e.g., Databricks SDK for Python), a Databricks Connect library embeddable in any IDE, official CLI, and REST API reference with SDK-based examples, all first-party documented and independently verified via CLI runtime probes. This directly supports AI-native developers building against official SDKs/tools, further reinforced by agent-skill installs and MCP tool integration docs. missing for 10: no independent third-party benchmark of SDK reliability/coverage across languages beyond Python.

   • [claimed-docs] “you learn how to automate Databricks operations and accelerate development with the Databricks SDK for Python”
   • [claimed-docs] “Databricks Connect enables developers to develop and debug their code on Databricks compute using any IDE's native running and debugging fun…”
   • [claimed-docs] “Just like a JDBC driver, the Databricks Connect library can be embedded in any application to interact with Databricks.”
   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI installed via the vendor's brew tap and printed `Databricks CLI v1.15.0` keylessly; …”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI SHIPS vendor agent skills — `databricks aitools install --path /tmp/pa-dbx-skills` k…”
   • [claimed-docs] “API reference hub lists versioned REST APIs side by side, e.g. "Jobs v2.0 API — REST API reference for version 2.0 version of the Jobs REST …”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Snowflake—none0/10

   Evidence shows Snowflake supports streams for CDC (polled) and notification integrations for cost alerts, but there is no documentation of a general-purpose webhook subscription mechanism that lets an AI-native user subscribe to events pushed via webhooks. Absence of evidence for this applicable capability yields 'none'.

   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “Notification integrations for cost anomaly alerts (General availability)”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables... so that actions can be taken using the changed data”

   proof ↗⚑ flag

   Databricks—none0/10

   No evidence in the pack describes any webhook subscription mechanism (e.g., event notifications pushed to external endpoints); Databricks docs reference REST APIs, SQL alerts, and MCP tools but nothing about webhooks for event subscription.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Snowflake✓fullclaimed8/10

   Snowflake ships Cortex AI Functions for LLM-powered unstructured analytics on data in-place, and Cortex Analyst lets business users ask natural-language questions and get direct answers without SQL, plus semantic views to ground these insights in business context — all inside the product. missing for 10: independent/hands-on validation of insight quality and no evidence of proactive/automated suggestion surfacing (e.g., anomaly-based recommendations) beyond query-driven Q&A.

   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs from OpenAI, Anthropic, Met…”
   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object. You can define busines…”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View ... define business metrics and model business entities…”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Databricks ships multiple first-party AI-insight surfaces: Genie for natural-language Q&A grounded in org data, AI/BI dashboards with AI-assisted authoring, automatic query performance insights/recommendations, and a semantic layer (metric views) that standardizes metrics for consistent AI-driven analysis. This directly satisfies the story of getting AI-generated insights/suggestions inside the product. Missing for 10: independent/hands-on user corroboration specifically validating insight quality (community evidence is generic platform sentiment, not about Genie/AI-BI insight accuracy), and no benchmark of suggestion usefulness.

   • [claimed-docs] “Ask data questions in natural language and get answers grounded in your organization's data.”
   • [claimed-docs] “Create interactive AI/BI dashboards with AI-assisted authoring to share insights across your organization.”
   • [claimed-docs] “Get automatic insights and recommendations when queries run inefficiently.”
   • [claimed-docs] “From natural language dashboard creation to deep conversational analytics with Genie, this is BI built on AI from the start.”
   • [claimed-docs] “Define business metrics with consistent calculations using a semantic layer. Reuse metrics across queries and dashboards.”
   • [claimed-docs] “you define the metric once, for example sum of revenue divided by distinct customer count, and users can group by any available field. The q…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Databricks
   Snowflake~partialclaimed5/10

   Snowflake documents several building blocks for background automation — Snowpipe auto-ingests files without manual scheduling, Dynamic Tables (GA) auto-refresh on a target lag, Streams capture DML changes to trigger downstream actions, and dbt Projects on Snowflake supports full orchestration of pipelines inside the platform. Cortex Agents plus the managed MCP server let AI agents query Snowflake data, but the evidence shows MCP as a request/response tool-serving interface rather than a documented mechanism for an AI-native user to schedule agents that run continuously and autonomously in the background. Missing for 10: explicit documentation of a Tasks/scheduler feature for autonomous job execution, evidence of agent-triggered/looping automations (not just query-based interactions), and independent/hands-on confirmation that these pieces compose into unattended AI-driven automation.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “CREATE OR ALTER DYNAMIC TABLE (General availability)”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations”
   • [claimed-docs] “No infrastructure to manage: Snowflake provides managed dbt Core and dbt Fusion runtimes.”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”

   proof ↗⚑ flag

   Databricks✓fullclaimed7/10

   Databricks supports autonomous background automation via Lakeflow pipelines/jobs scheduling, Genie Code running as an autonomous agent that plans, runs code, fixes errors and asks approval before tool use, and CLI/SDK scripting for automation, plus MCP-based agent tooling for background agent workflows. missing for 10: independent/hands-on verification of fully unattended (no-human-in-loop) agent runs, and clearer documentation of scheduling/triggers specifically for autonomous agent tasks rather than just pipelines.

   • [claimed-docs] “Run Genie Code as an autonomous agent that plans, runs code, fixes errors, and asks for approval before it uses tools.”
   • [claimed-docs] “Create and deploy an ETL (extract, transform, and load) pipeline for data orchestration using Lakeflow pipelines and Auto Loader.”
   • [claimed-docs] “The Databricks CLI (command-line interface) allows you to interact with the Databricks platform from your local terminal or automation scrip…”
   • [claimed-docs] “you learn how to automate Databricks operations and accelerate development with the Databricks SDK for Python”
   • [claimed-docs] “Create AI agent tools using Unity Catalog functions, including third-party integrations and code interpreter tools.”
   • [claimed-docs] “Discover, authenticate to, and call managed, MCP Service, and custom MCP servers from your agent code, then deploy the agent on Databricks A…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Databricks
   Snowflake~partialclaimed4/10

   Snowflake's homepage advertises 'Snowflake CoWork' ('Ask anything') and 'Snowflake CoCo' ('Build anything') as built-in enterprise AI assistants, and Cortex Analyst lets business users get natural-language answers without SQL — both suggest task delegation to an in-product assistant. However, the evidence pack has no dedicated docs page, feature list, or independent/hands-on account of CoWork/CoCo's actual task-delegation capabilities, so the claim rests on thin marketing taglines rather than substantiated documentation. Missing for 10: dedicated CoWork/CoCo documentation detailing task-delegation scope, hands-on or independent corroboration of the assistant performing multi-step tasks, and clarity on how it differs from Cortex Analyst's NL query feature.

   • [claimed-docs] “Ask anything with Snowflake CoWork. Build anything with Snowflake CoCo. Welcome to your one-stop shop for everyone in the enterprise.”
   • [claimed-docs] “Build anything with Snowflake CoCo.”
   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Databricks ships Genie Code, a built-in AI assistant that generates/runs code, builds pipelines and dashboards, debugs errors, and can run as an autonomous agent that plans, executes code, fixes errors and asks approval before tool use — directly matching 'delegate tasks to a built-in AI assistant.' It also supports parallel chats and can be given governed tool access (Slack, GitHub, etc.) via MCP for agentic task execution. missing for 10: independent/hands-on user validation of agentic delegation quality is absent from community evidence.

   • [claimed-docs] “It generates and runs code, builds pipelines and AI/BI dashboards, debugs errors, and works directly with Unity Catalog tables, columns, and…”
   • [claimed-docs] “Chat with Genie Code, get inline suggestions, and run agentic tasks in your workspace.”
   • [claimed-docs] “Run Genie Code as an autonomous agent that plans, runs code, fixes errors, and asks for approval before it uses tools.”
   • [claimed-docs] “It generates and runs code, builds pipelines and AI/BI dashboards, debugs errors, and works directly with Unity Catalog tables, columns, and…”
   • [claimed-docs] “Start work directly from Genie Code rather than from an asset like a notebook, run multiple chats in parallel, and persona”
   • [claimed-docs] “Give your agent governed access to third-party and SaaS tools such as Slack, GitHub, Google Drive, Google Calendar, and Gmail”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Databricks
   Snowflake~partialclaimed7/10

   Snowflake documents genuine natural-language operation via Cortex Analyst (ask business questions in NL, get answers without writing SQL) and Cortex AI Functions for NL-driven analytics on text/images, plus a marketed 'CoWork'/'CoCo' NL agent interface and an MCP server exposing these NL/agent capabilities to external AI agents. This is solid support for AI-native NL interaction, but most of it is scoped to querying/analytics rather than full product administration (warehouses, security, pipelines) via natural language, and CoWork/CoCo are only marketing taglines with no detailed docs in the pack. Missing for 10: independent/hands-on validation of NL breadth, detailed CoWork/CoCo documentation, and evidence that operational/admin tasks (not just analytics) can be driven by natural language.

   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs from OpenAI, Anthropic, Met…”
   • [claimed-docs] “Use Cortex AI Functions in Snowflake to run unstructured analytics on text and images with industry-leading LLMs”
   • [claimed-docs] “Ask anything with Snowflake CoWork. Build anything with Snowflake CoCo. Welcome to your one-stop shop for everyone in the enterprise.”
   • [claimed-docs] “Build anything with Snowflake CoCo.”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”

   proof ↗⚑ flag

   Databricks✓fullclaimed7/10

   Databricks documents multiple natural-language interaction surfaces: Genie for asking data questions in plain English (docs-8), Genie Code as an autonomous coding/data agent that plans, runs code, fixes errors, and builds pipelines/dashboards from NL prompts (docs-15, docs-28, docs-29, docs-30), and NL-driven dashboard authoring (docs-22). This covers the core of 'operate via natural language' across both business and technical personas. Missing for 10: independent/hands-on validation of NL command reliability and no evidence of NL control over broader ops (e.g., cluster/job management) beyond data/coding tasks.

   • [claimed-docs] “Ask data questions in natural language and get answers grounded in your organization's data.”
   • [claimed-docs] “It generates and runs code, builds pipelines and AI/BI dashboards, debugs errors, and works directly with Unity Catalog tables, columns, and…”
   • [claimed-docs] “From natural language dashboard creation to deep conversational analytics with Genie, this is BI built on AI from the start.”
   • [claimed-docs] “Chat with Genie Code, get inline suggestions, and run agentic tasks in your workspace.”
   • [claimed-docs] “Run Genie Code as an autonomous agent that plans, runs code, fixes errors, and asks for approval before it uses tools.”
   • [claimed-docs] “It generates and runs code, builds pipelines and AI/BI dashboards, debugs errors, and works directly with Unity Catalog tables, columns, and…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Databricks
   Snowflake~partialprobed3/10

   Snowflake publishes OpenAPI-compliant spec files and importable Postman collections for its REST/SQL APIs, which gives developers a way to run example requests, but there is no evidence of an embedded, interactive 'try-it' API reference on the docs site itself — a direct probe for openapi.json/swagger endpoints returned 404s. Missing for 10: an in-browser interactive API explorer (e.g., Swagger/Redoc UI) hosted by Snowflake, and any independent confirmation that the Postman-based workflow is commonly used as a live API reference.

   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.snowflake.com/openapi.json, https://docs.snowflake.com/swagger.json, https://docs.snowf…”

   proof ↗⚑ flag

   Databricks~partialprobed4/10

   Databricks publishes a detailed REST API reference with request/response payload examples and code samples via CLI/Terraform/SDKs (databricks-docs-65, databricks-supp-api-reference-examples), but the same doc explicitly states 'No live try-it runner is documented,' and probes found no OpenAPI/Swagger endpoint to power an interactive explorer (databricks-probe-2). This gives static, copyable examples rather than a true in-browser runnable API reference. Missing for 10: an in-page 'try it now' execution console, OpenAPI-based interactive explorer, and confirmation of live request execution against a user's workspace from the docs site.

   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”
   • [claimed-docs] “API reference (docs.databricks.com/api): "This reference describes the types, paths, and any request payload or query parameters, for each s…”
   • [claimed-docs] “API reference hub lists versioned REST APIs side by side, e.g. "Jobs v2.0 API — REST API reference for version 2.0 version of the Jobs REST …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.databricks.com/openapi.json, https://docs.databricks.com/swagger.json, https://docs.dat…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Snowflake
   Snowflake✓fullprobed8/10

   Snowflake publishes an official, first-party GitHub repository (snowflakedb/snowflake-rest-api-specs) containing downloadable OpenAPI-compliant spec files plus Postman collections for its REST APIs, and its own docs explicitly state the REST APIs are 'compliant with the OpenAPI specification' and enable building integrations 'using the openAPI specifications.' Missing for 10: a directly hosted /openapi.json or /swagger.json endpoint on the docs site itself (probe found 404s there), so the machine-readable spec must be fetched from the separate GitHub repo rather than a single canonical URL.

   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.snowflake.com/openapi.json, https://docs.snowflake.com/swagger.json, https://docs.snowf…”

   proof ↗⚑ flag

   Databricks—none0/10

   Databricks publishes an extensive human-readable REST API reference (databricks-docs-65, databricks-supp-versioned-apis, databricks-supp-api-reference-examples) but there is no evidence of a downloadable machine-readable spec — the probe explicitly found openapi.json/swagger.json/api/openapi.json/.well-known/openapi.json all return 404 (databricks-probe-2), and the API reference page confirms 'No live try-it runner is documented.' This is an applicable axis for a platform with a large REST API surface, so absent evidence of an OpenAPI/Swagger artifact this is 'none' rather than 'na'.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.databricks.com/openapi.json, https://docs.databricks.com/swagger.json, https://docs.dat…”
   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”
   • [claimed-docs] “API reference (docs.databricks.com/api): "This reference describes the types, paths, and any request payload or query parameters, for each s…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Snowflake
   Snowflake~partialclaimed5/10

   Snowflake's zero-copy cloning (object-clone) lets users create full database/schema clones inheriting privileges without duplicating or altering production data, which supports building an isolated sandbox for testing, and RBAC plus resource monitors help isolate/limit that environment. However, the evidence never frames this explicitly as an 'AI-native sandbox' workflow or ties cloning to agentic/AI testing use cases. missing for 10: explicit sandbox/dev-test documentation framed for AI-native or agent workflows, guidance on isolating agent test runs from prod data, and independent corroboration of clone-based sandboxing in practice.

   • [claimed-docs] “the clone inherits all granted privileges on the clones of all child objects contained in the source object”
   • [claimed-docs] “If the source object is a database or schema, the clone inherits all granted privileges on the clones of all child objects contained in the …”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users”

   proof ↗⚑ flag

   Databricks—none0/10

   Evidence shows Unity Catalog governance, Free Edition for learning, and an AI Playground for prototyping agents, but nothing documents a dedicated sandbox/test environment that isolates AI-native testing from production data (e.g., dev/test catalog cloning, data masking for test runs, or a documented sandbox mode). Missing for 10: explicit sandbox/test-environment feature, data isolation guarantees for testing, and any customer/community confirmation of safe non-production testing workflows.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Snowflake~partialclaimed6/10

   Snowflake documents official REST APIs (SQL API, resource-management API) built on OpenAPI specs, and maintains a dedicated 'Behavior change announcements' page describing dated bundles of changes meant to minimize disruption — functioning as a de facto deprecation/change policy. However, there's no explicit documentation of API version numbers (v1/v2) or formal deprecation timelines/sunset dates for the APIs themselves. Missing for 10: explicit API versioning scheme documentation, formal deprecation timeline/sunset policy tied to specific API versions, independent corroboration of API stability guarantees.

   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “Docs, "Behavior change announcements": "To help you manage your operations and minimize disruption to your Snowflake service, we document be…”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”

   proof ↗⚑ flag

   Databricks~partialclaimed6/10

   Databricks documents versioned REST APIs (e.g., Jobs v2.0) with explicit recommendations to use the latest version, and shows a concrete deprecation/migration case (legacy SQL API path deprecated in favor of api/2.0/sql/queries with a migration guide). This shows real-world versioning and deprecation practice, but there's no single consolidated deprecation policy document, no stated support timelines/sunset dates, and no explicit versioning scheme description (e.g., semver, LTS windows) across the whole API surface. missing for 10: a unified deprecation-policy page with timelines/sunset commitments, explicit API versioning scheme documentation, and independent confirmation that deprecations are reliably telegraphed in advance across all APIs.

   • [claimed-docs] “Docs, "Update to the latest Databricks SQL API version": "The legacy API is deprecated and support will end soon. Use this page to migrate y…”
   • [claimed-docs] “API reference hub lists versioned REST APIs side by side, e.g. "Jobs v2.0 API — REST API reference for version 2.0 version of the Jobs REST …”
   • [claimed-docs] “API reference (docs.databricks.com/api): "This reference describes the types, paths, and any request payload or query parameters, for each s…”
   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Databricks
   Snowflake~partialclaimed6/10

   Snowflake supports bulk/batch operations via SQL (COPY INTO, Snowpipe micro-batches), Snowpark for programmatic bulk data processing, REST/SQL APIs for scripted batch operations, and CLI/dbt for orchestrating multi-object workflows, but these are general data-platform bulk operations rather than an AI-native agent-oriented bulk-action capability explicitly designed for AI agents to invoke across many items at once. The MCP server (Cortex Agents MCP) exposes tools for agents but evidence doesn't show explicit bulk/batch operation support through that interface. missing for 10: explicit documentation of AI-agent-initiated bulk operations (e.g., MCP server batch tool calls across many items), hands-on/independent evidence of AI-native bulk workflows succeeding at scale, and any agent-specific bulk-action API beyond generic SQL/REST batch capabilities.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowpark API for Python, Java, and Scala — process data at scale inside Snowflake.”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”

   proof ↗⚑ flag

   Databricks✓fullprobed7/10

   Databricks exposes bulk/automation capabilities via CLI, SDKs, REST APIs, and Lakeflow pipelines that let AI-native users script operations across many jobs, tables, or workspace objects at once (databricks-docs-2, databricks-docs-48, databricks-docs-49, databricks-docs-56, databricks-docs-65), and Unity Catalog governs bulk operations across catalogs/schemas with consistent access control. Runtime probes confirm the CLI actually works keylessly and covers workspace/compute/jobs/pipelines plus a raw REST wrapper (databricks-probe-rt-1). missing for 10: explicit documentation or example of a single bulk-operation command (e.g., batch update/delete across many items in one call) rather than iterating via scripts, and independent/hands-on evidence of bulk-operation reliability at scale.

   • [claimed-docs] “The Databricks CLI (command-line interface) allows you to interact with the Databricks platform from your local terminal or automation scrip…”
   • [claimed-docs] “allows you to interact with the Databricks platform from your local terminal or automation scripts”
   • [claimed-docs] “you learn how to automate Databricks operations and accelerate development with the Databricks SDK for Python”
   • [claimed-docs] “You work with the objects Unity Catalog governs through Catalog Explorer, SQL, the Databricks CLI, and REST APIs.”
   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI installed via the vendor's brew tap and printed `Databricks CLI v1.15.0` keylessly; …”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Snowflake~partialclaimed6/10

   Snowflake offers building blocks that support event-driven automation — Streams capture DML changes for downstream actions, Snowpipe auto-ingests new files, resource monitors can auto-suspend warehouses on cost thresholds, and anomaly monitors trigger notification alerts — but there is no single unified 'rules engine' or declarative trigger-action framework exposed as one product for AI-native users to define arbitrary event-condition-action automations. missing for 10: a first-class, general-purpose rules/trigger-action framework (e.g., 'if X event then do Y') rather than disparate feature-specific mechanisms (streams+tasks, Snowpipe, resource monitors), and independent/hands-on evidence of composing these into end-to-end automated workflows.

   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables... so that actions can be taken using the changed data”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage”
   • [claimed-docs] “You can use a resource monitor to monitor credit usage by virtual warehouses ... You can also set up a resource monitor to suspend a standar…”
   • [claimed-docs] “you can set up a resource monitor to suspend a standard virtual warehouse or disable an Adaptive Warehouse when it reaches a credit limit”
   • [claimed-docs] “Anomaly monitors for cost anomalies (Preview)”
   • [claimed-docs] “Notification integrations for cost anomaly alerts (General availability)”

   proof ↗⚑ flag

   Databricks~partialclaimed6/10

   Databricks supports rule-like automation via SQL Alerts (monitor query results, evaluate conditions, deliver notifications automatically) and event-driven Lakeflow/Auto Loader pipelines that trigger on new file arrival, plus job triggers and the CLI/SDK for scripting automated actions. However, there is no dedicated general-purpose 'if event then action' rules engine documented beyond these specific mechanisms (alerts, streaming triggers, job schedules). Missing for 10: a unified event-rule/trigger API spanning arbitrary events, independent hands-on validation of alert/trigger reliability, and more detail on custom action types beyond notifications.

   • [claimed-docs] “Monitor query results, evaluate conditions, and deliver notifications automatically.”
   • [claimed-docs] “Incrementally and efficiently process new data files as they arrive in cloud storage.”
   • [claimed-docs] “Process data for real-time workloads with end-to-end latency as low as five milliseconds.”
   • [claimed-docs] “Create and deploy an ETL (extract, transform, and load) pipeline for data orchestration using Lakeflow pipelines and Auto Loader.”
   • [claimed-docs] “allows you to interact with the Databricks platform from your local terminal or automation scripts”
   • [claimed-docs] “you learn how to automate Databricks operations and accelerate development with the Databricks SDK for Python”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Databricks
   Snowflake~partialclaimed4/10

   Evidence shows dbt Projects on Snowflake can 'orchestrate' transformations with a managed runtime, implying some recurring-job scheduling capability, but the pack contains no direct documentation of Snowflake's native TASK/scheduler object or agent-triggered recurring workflows for AI-native users. Missing for 10: explicit docs on Snowflake Tasks or a scheduler API, evidence of AI agents creating/managing recurring jobs via MCP or CLI, and independent/hands-on confirmation of scheduling reliability.

   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations in th…”
   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations”
   • [claimed-docs] “No infrastructure to manage: Snowflake provides managed dbt Core and dbt Fusion runtimes.”

   proof ↗⚑ flag

   Databricks✓fullprobed8/10

   Databricks Lakeflow Jobs (referenced via docs-1, docs-40, docs-4/45/50 MCP/agent orchestration context, and CLI docs-2/48/rt-1) natively supports scheduling recurring jobs/workflows, and the CLI/SDK (docs-49) allow programmatic/automated job management for AI-native workflows. Missing for 10: no explicit docs excerpt detailing cron/schedule syntax or trigger configuration, and no independent/hands-on confirmation of scheduling reliability beyond vendor docs.

   • [claimed-docs] “Create and deploy an ETL (extract, transform, and load) pipeline for data orchestration using Lakeflow pipelines and Auto Loader.”
   • [claimed-docs] “Develop and deploy your first ETL (extract, transform, and load) pipeline for data orchestration with Apache Spark™.”
   • [claimed-docs] “The Databricks CLI (command-line interface) allows you to interact with the Databricks platform from your local terminal or automation scrip…”
   • [claimed-docs] “allows you to interact with the Databricks platform from your local terminal or automation scripts”
   • [claimed-docs] “you learn how to automate Databricks operations and accelerate development with the Databricks SDK for Python”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI installed via the vendor's brew tap and printed `Databricks CLI v1.15.0` keylessly; …”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Databricks
   Snowflake~partialclaimed4/10

   Snowflake docs show building blocks that touch pieces of this story — dbt Projects on Snowflake covers the 'develop, deploy, orchestrate, observe' lifecycle (implying dbt's git-based versioning) [snowflake-docs-2][snowflake-docs-55], Time Travel lets you restore/rollback objects and query past states [snowflake-docs-5][snowflake-docs-24][snowflake-docs-35], and object cloning/behavior-change bundles give some notion of state snapshots and change tracking [snowflake-docs-67][snowflake-supp-behavior-changes]. However there is no dedicated, documented capability for versioning, reviewing, and rolling back 'automations' (e.g., Tasks, Dynamic Tables pipelines, agent workflows) as a first-class AI-native feature — the evidence is inferential rather than a direct product answer to this story. Missing for 10: explicit versioning/review/rollback tooling for Tasks/Dynamic Tables/agent pipelines, a documented approval/review workflow for automation changes, and independent/hands-on confirmation of rollback working for automations specifically.

   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations in th…”
   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations”
   • [claimed-docs] “Using Time Travel, you can perform the following actions within a defined period of time: Query data in the past that has since been updated…”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted.”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted. You can restore individual objects, such as tables, or restore…”
   • [claimed-docs] “the clone inherits all granted privileges on the clones of all child objects contained in the source object”
   • [claimed-docs] “Docs, "Behavior change announcements": "To help you manage your operations and minimize disruption to your Snowflake service, we document be…”

   proof ↗⚑ flag

   Databricks~partialclaimed5/10

   Databricks documents automatic versioning for notebooks, Delta table time-travel/rollback, and Unity Catalog lineage/audit logging, which together cover generic version/review/rollback capabilities, but none of this evidence explicitly ties into versioning or rolling back Lakeflow pipelines/Jobs (the actual 'automations') rather than notebooks/tables. Missing for 10: explicit job/pipeline version history and rollback workflow, CI/CD or git-based pipeline versioning evidence, and any hands-on confirmation of rolling back an automation run.

   • [claimed-docs] “Databricks notebooks provide real-time coauthoring in multiple languages, automatic versioning, and built-in data visualizations”
   • [claimed-docs] “Databricks notebooks provide real-time coauthoring in multiple languages, automatic versioning, and built-in data visualizations for develop…”
   • [claimed-docs] “Use history information to audit operations, roll back a table, or query a table at a specific point in time using time travel.”
   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”

   proof ↗⚑ flag

Pricing

1. platform-engineerThe pricing model is documented clearly enough that I can estimate a monthly bill for my workload before committing

   weight 3 · round to Databricks
   Snowflake!disputedcontradicted5/10

   Snowflake docs explain the underlying cost model (credit-consuming virtual warehouses, resizing, resource monitors, cost-anomaly alerts, and a general pricing-tier page) which gives a platform engineer the mechanics needed to model cost, but there is no concrete rate card or calculator evidenced. Community reports concretely contradict the 'estimate before committing' claim: users note costs 'balloon pretty fast', warehouse credit consumption 'doubles each size up', there is 'no query level attribution of costs and no in-built features for monitoring', and it's 'easy... to get to $100k/year bills without massive data' — indicating the documented model is hard to translate into an accurate upfront estimate in practice. missing for 10: a transparent unit-price/rate table, a first-party cost calculator, and independent confirmation that engineers can reliably forecast bills from the docs alone.

   • [claimed-docs] “Virtual warehouses consume credits as they execute queries, load data and perform other DML operations. Virtual Warehouses are user-managed,…”
   • [claimed-docs] “Virtual Warehouses are user-managed, which means you can directly control credit consumption of these resources.”
   • [claimed-docs] “You can use a resource monitor to monitor credit usage by virtual warehouses ... You can also set up a resource monitor to suspend a standar…”
   • [claimed-docs] “you can set up a resource monitor to suspend a standard virtual warehouse or disable an Adaptive Warehouse when it reaches a credit limit”
   • [claimed-docs] “An entry-level, introductory offering providing access to core functionality.”
   • [claimed-docs] “Standard: An entry-level, introductory offering providing access to core functionality. ... Security with automatic encryption of all data, …”
   • [community] “Since the beginning of my trial, I have used 9 credits and 40GB of storage... about $19.60 worth of resources. Snowflake costs could balloon…”
   • [community] “The problem with Snowflake is particularly worse due to its lack of query level attribution of costs and no in-built features for monitoring…”
   • [community] “I have no Snowflake experience, but some limited BigQuery experience. And it's very easy for a small company to get to $100k/year bills with…”

   proof ↗⚑ flag

   Databricks~partialcommunity5/10

   Databricks documents a pay-as-you-go, per-second-billing model (docs-21) and provides account/workspace-level budget tracking tools (docs-58, docs-61) that help monitor spend, but there is no evidence of a pricing calculator, DBU rate tables, or concrete per-workload cost examples that would let a platform engineer pre-estimate a monthly bill before committing. Community comments (databricks-comm-2, databricks-comm-4) describing the platform as 'crazy expensive' with 'surprise gotchas' around serverless pricing further suggest cost estimation in practice is harder than the high-level docs imply, though this falls short of a concrete documented failure of the pricing docs themselves. Missing for 10: a pricing/cost calculator, itemized DBU/unit rate tables, example workload cost breakdowns, and independent confirmation that pre-commitment estimates match actual bills.

   • [claimed-docs] “Databricks offers you a pay-as-you-go approach with no up-front costs. Only pay for the products you use at per second granularity.”
   • [claimed-docs] “You can set up budgets to either track account-wide spending, or apply filters to track the spending of specific teams, projects, or workspa…”
   • [claimed-docs] “Budgets enable you to monitor usage across your account. You can set up budgets to either track account-wide spending, or apply filters to t…”
   • [community] “Coming from hadoop, databricks is utopia. It's stable, fast, scales really well if you have massive datasets. The biggest gripe I have is ho…”
   • [community] “They push Serverless so hard but there are SO MANY limitations and surprise gotchas. It's driving me absolutely insane.”

   proof ↗⚑ flag

2. platform-engineerBudgets, resource monitors, or auto-suspend stop a runaway query or idle compute from burning money overnight

   weight 2 · round to Snowflake
   Snowflake✓fullcommunity8/10

   Snowflake ships resource monitors that track credit usage and can auto-suspend a virtual warehouse (or disable an Adaptive Warehouse) when a threshold is hit, plus GA cost-anomaly monitors, per-user quotas, and notification integrations for cost alerts, directly matching the platform-engineer need to stop runaway spend. Community commentary independently corroborates this as standard practice (setting up resource monitors and using small warehouses to control cost), and warehouses can also be manually started, stopped, and resized to control burn. Missing for 10: independent hands-on confirmation that resource monitors reliably kill an in-flight runaway query versus only suspending future warehouse starts, and detail on statement-level timeout controls.

   • [claimed-docs] “You can use a resource monitor to monitor credit usage by virtual warehouses ... You can also set up a resource monitor to suspend a standar…”
   • [claimed-docs] “you can set up a resource monitor to suspend a standard virtual warehouse or disable an Adaptive Warehouse when it reaches a credit limit”
   • [claimed-docs] “You can also set up a resource monitor to suspend a standard virtual warehouse or disable an Adaptive Warehouse when it reaches a credit lim…”
   • [claimed-docs] “Per-user quotas (General availability)”
   • [claimed-docs] “Anomaly monitors for cost anomalies (Preview)”
   • [claimed-docs] “Notification integrations for cost anomaly alerts (General availability)”
   • [claimed-docs] “Virtual warehouses consume credits as they execute queries, load data and perform other DML operations. Virtual Warehouses are user-managed,…”
   • [claimed-docs] “Warehouses can be started and stopped at any time. They can also be resized at any time, even while running, to accommodate the need for mor…”
   • [community] “Since the beginning of my trial, I have used 9 credits and 40GB of storage... about $19.60 worth of resources. Snowflake costs could balloon…”

   proof ↗⚑ flag

   Databricks~partialclaimed5/10

   Databricks docs show account-level budgets for tracking spend by team/project/workspace and query-level alerting when conditions are met (databricks-docs-58, -61, -26), which partially covers cost monitoring, but the evidence never documents an automatic enforcement mechanism (e.g., warehouse auto-stop for idle compute or query kill/timeout) that actually halts a runaway query or idle cluster overnight — budgets are described as tracking/notifying, not stopping. missing for 10: explicit auto-suspend/auto-stop behavior for idle compute, automatic termination of runaway queries, and independent confirmation that budgets can enforce hard spend caps rather than just alert.

   • [claimed-docs] “You can set up budgets to either track account-wide spending, or apply filters to track the spending of specific teams, projects, or workspa…”
   • [claimed-docs] “Budgets enable you to monitor usage across your account. You can set up budgets to either track account-wide spending, or apply filters to t…”
   • [claimed-docs] “Monitor query results, evaluate conditions, and deliver notifications automatically.”

   proof ↗⚑ flag

Trial

1. analystEvaluate with a free tier or trial — real queries on real data without a credit card or a sales call

   weight 1 · round to Databricks
   Snowflake~partialcommunity5/10

   Community evidence confirms a real, usable free trial exists (a user ran actual queries burning real credits and storage over the trial period), showing the trial supports real queries on real data — but there is no first-party documentation in the pack describing signup requirements (credit card, sales contact) for that trial, and pricing docs only describe a paid 'Standard' entry tier rather than a no-card free trial. missing for 10: official docs confirming no-credit-card signup, no sales-call requirement, and trial credit/duration terms.

   • [community] “Since the beginning of my trial, I have used 9 credits and 40GB of storage... about $19.60 worth of resources. Snowflake costs could balloon…”
   • [claimed-docs] “An entry-level, introductory offering providing access to core functionality.”
   • [claimed-docs] “Standard: An entry-level, introductory offering providing access to core functionality. ... Security with automatic encryption of all data, …”

   proof ↗⚑ flag

   Databricks✓fullclaimed7/10

   Databricks offers a genuinely free, self-serve 'Free Edition' (replacing Community Edition) plus a free trial, explicitly for exploring datasets and running real queries/ML without needing a workspace purchase or sales call (docs-66, docs-73, docs-74, docs-39). This directly matches the analyst story of self-serve evaluation on real data. Missing for 10: explicit confirmation that no credit card is required to sign up, and independent/hands-on user corroboration of the free-tier experience (community evidence only discusses paid usage/cost complaints, not the free tier).

   • [claimed-docs] “Free Edition gives you an easy-to-use Databricks workspace where you can explore datasets, build and share projects, and work with AI and ma…”
   • [claimed-docs] “Databricks Free Edition is a no-cost version of Databricks designed for students, educators, hobbyists, and anyone interested in learning or…”
   • [claimed-docs] “Free Edition replaced the legacy Databricks Community Edition, which was retired in 2025. If you previously used Community Edition, sign up …”
   • [claimed-docs] “Start your journey with Databricks by signing up for a free trial account.”

   proof ↗⚑ flag

Bi

1. analystStandard drivers (JDBC/ODBC) and documented BI-tool integrations connect my dashboards without custom glue

   weight 1 · round to Databricks
   Snowflake—none0/10

   The evidence pack contains no specific mention of JDBC/ODBC drivers or documented BI-tool integrations (e.g., Tableau, Power BI, Looker) for Snowflake; only a generic reference to 'applications and tools you can use to access Snowflake' (snowflake-docs-27) without detail on standard drivers or BI connectors. This is an axis that clearly applies to a data warehouse product, but no concrete evidence demonstrates the capability.

   ⚑ flag

   Databricks✓fullclaimed7/10

   Docs show that external BI tools (Power BI, Tableau, Sigma) can query Databricks metric views directly, and a JDBC-style connection library (Databricks Connect) is documented, indicating standard driver-based BI connectivity without custom glue. However, no dedicated JDBC/ODBC driver certification page or explicit ODBC integration guide is cited in the pack. missing for 10: a direct JDBC/ODBC driver download/certification doc, independent BI-tool hands-on validation.

   • [claimed-docs] “Query metric views from Power BI, Tableau, Sigma, and other external BI tools.”
   • [claimed-docs] “Just like a JDBC driver, the Databricks Connect library can be embedded in any application to interact with Databricks.”
   • [claimed-docs] “It runs directly on your data lake, supports ANSI SQL with Delta Lake extensions, and provides the tools to build highly performant, cost-ef…”
   • [claimed-docs] “Define business metrics with consistent calculations using a semantic layer. Reuse metrics across queries and dashboards.”

   proof ↗⚑ flag

Dev loop

1. data-engineerI get a fast local or free dev loop — a local engine, emulator, or sandbox — to develop transformations before touching production compute

   weight 2 · round to Databricks
   Snowflake—none0/10

   Snowflake's evidence pack covers cloud compute (warehouses, Snowpipe, notebooks, dbt-in-Snowflake, Snowpark) but nothing about a local engine, emulator, or free sandbox for developing transformations before touching production compute — everything described runs against live Snowflake compute/credits. Community evidence even notes trial credits get consumed quickly (~$19.60 in credits within days), reinforcing that there's no cost-free local dev loop. Missing for 10: any local engine/emulator, offline dev mode, or a genuinely free (non-credit-consuming) sandbox tier.

   • [community] “Since the beginning of my trial, I have used 9 credits and 40GB of storage... about $19.60 worth of resources. Snowflake costs could balloon…”
   • [claimed-docs] “An entry-level, introductory offering providing access to core functionality.”
   • [claimed-docs] “Standard: An entry-level, introductory offering providing access to core functionality. ... Security with automatic encryption of all data, …”
   • [claimed-docs] “Virtual warehouses consume credits as they execute queries, load data and perform other DML operations. Virtual Warehouses are user-managed,…”

   proof ↗⚑ flag

   Databricks~partialcommunity5/10

   Databricks offers a free-tier workspace (Free Edition) and local-IDE tooling (Databricks Connect, dbt Core, CLI/SDK) that let a data-engineer author and test transformations from their laptop, but Databricks Connect still executes against real remote (Databricks) compute rather than a true local engine/emulator, and Free Edition is a hosted cloud workspace, not an offline sandbox. Community commentary even notes some engineers prefer spinning up their own local notebook/storage instead, underscoring the lack of a genuine local execution engine. missing for 10: a true local/offline execution engine or emulator that fully mimics production compute without any cloud dependency, and evidence of hands-on validation of that local dev loop.

   • [claimed-docs] “Databricks Connect enables developers to develop and debug their code on Databricks compute using any IDE's native running and debugging fun…”
   • [claimed-docs] “Just like a JDBC driver, the Databricks Connect library can be embedded in any application to interact with Databricks.”
   • [claimed-docs] “Free Edition gives you an easy-to-use Databricks workspace where you can explore datasets, build and share projects, and work with AI and ma…”
   • [claimed-docs] “Databricks Free Edition is a no-cost version of Databricks designed for students, educators, hobbyists, and anyone interested in learning or…”
   • [claimed-docs] “dbt Core enables you to write dbt code in the IDE of your choice on your local development machine and then run dbt from the command line.”
   • [claimed-docs] “dbt (data build tool) is a development environment for transforming data by writing select statements.”
   • [community] “Not only is Databricks a deplorable company when it comes to HR, but their product is terrible. I really don't get what it's all about. Much…”

   proof ↗⚑ flag

Transformation

1. data-engineerDbt is a first-class citizen — a documented adapter or native dbt project support with vendor docs to match

   weight 2 · round drawn
   Snowflake✓fullcommunity8/10

   Snowflake has a dedicated first-party feature, 'dbt Projects on Snowflake,' with vendor docs describing native support for the full dbt lifecycle (develop, deploy, orchestrate, observe), managed dbt Core/Fusion runtimes, and a documented migration path from dbt Core. This goes beyond a community adapter — it's native, vendor-documented dbt support. missing for 10: independent/hands-on validation of dbt Projects on Snowflake in production, and more detail on parity/limitations vs dbt Core for advanced use cases.

   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations in th…”
   • [claimed-docs] “Migrating an existing dbt Core project? See the Migrate from dbt Core to dbt Projects on Snowflake.”
   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations”
   • [claimed-docs] “No infrastructure to manage: Snowflake provides managed dbt Core and dbt Fusion runtimes.”
   • [community] “The issue with dbt models in Snowflake is that if you perform a full-refresh and don't sort it, you ruin any natural clustering from an incr…”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Databricks has a dedicated vendor docs page for dbt covering installation, connection, and dbt Core usage (databricks-docs-10, -14, -35), making dbt a documented first-class integration path for data engineers. missing for 10: no evidence of a native dbt-databricks adapter maintenance page, independent community corroboration of dbt workflow quality, or dbt Cloud-specific integration details.

   • [claimed-docs] “This page explains what dbt is, how to install dbt Core, and how to connect.”
   • [claimed-docs] “dbt Core enables you to write dbt code in the IDE of your choice on your local development machine and then run dbt from the command line.”
   • [claimed-docs] “dbt (data build tool) is a development environment for transforming data by writing select statements.”

   proof ↗⚑ flag

Access

1. platform-engineerAccess control reaches tables, columns, and rows — roles plus masking policies — so one warehouse can serve many teams safely

   weight 3 · round to Snowflake
   Snowflake~partialclaimed5/10

   Docs confirm Snowflake's core RBAC model (privileges assigned to roles, roles to users) and Access History views tracking table/column-level query and write activity, which supports auditing at the object level. However, the evidence pack contains no mention of dynamic data masking policies or row access policies (row-level security), which are the specific mechanisms the story calls out for column- and row-level control — missing for 10: masking policy documentation, row access policy documentation, and any independent/hands-on confirmation these work as described.

   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users”
   • [claimed-docs] “Access History in Snowflake refers to when the user query reads data and when the SQL statement performs a data write operation... The user …”
   • [claimed-docs] “The records in these views facilitate regulatory compliance auditing and provide insights on popular and frequently accessed tables and colu…”
   • [claimed-docs] “facilitate regulatory compliance auditing and provide insights on popular and frequently accessed tables and columns”
   • [claimed-docs] “The user access history can be found by querying the ACCESS_HISTORY view in the ACCOUNT_USAGE and ORGANIZATION_USAGE schemas.”

   proof ↗⚑ flag

   Databricks!disputedcontradicted4/10

   Unity Catalog docs describe enforcing access control on tables and objects with grants (databricks-docs-19/38/46/56/70), which supports role-based table-level governance for many teams, but the evidence pack contains no first-party documentation of column-level masking policies or row-level filters. A community report explicitly contradicts the row/column-masking claim, stating Databricks security 'seems lacking - just table level, only in SQL and Spark, none in R' compared to competitors offering table/column/row-level security and dynamic masking (databricks-comm-9). Missing for 10: first-party docs on column masking policies, row-level security/filters, and independent confirmation these work as claimed to resolve the community-reported gap.

   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [claimed-docs] “Create a table and grant privileges in Databricks using the Unity Catalog data governance model.”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [community] “Snowflake has much more advanced data security - table, column, row level security, dynamic data masking, and zero-copy cloning. Databricks …”

   proof ↗⚑ flag

Governance

1. platform-engineerI get audit logs of who ran what and column-level lineage of where data came from

   weight 2 · round to Databricks
   Snowflake~partialclaimed6/10

   Snowflake provides strong audit-log coverage via Query History (who ran what queries) and Access History (ACCESS_HISTORY view tracking reads/writes for compliance auditing, including per-column access insights), which addresses the 'who ran what' half of the story well. However, the evidence pack does not document an explicit column-level lineage graph/feature (e.g., Snowflake's Horizon/lineage explorer) showing upstream data provenance — only that Access History surfaces 'popular and frequently accessed tables and columns,' which is usage insight, not full lineage tracing. Missing for 10: explicit column-level lineage/graph documentation, independent validation of lineage accuracy across transformations.

   • [claimed-docs] “With the Query History page in Snowsight, you can do the following: Monitor individual or grouped queries that are executed by users in your…”
   • [claimed-docs] “The Query History page lets you explore queries executed in your Snowflake account over the last 14 days.”
   • [claimed-docs] “Access History in Snowflake refers to when the user query reads data and when the SQL statement performs a data write operation... The user …”
   • [claimed-docs] “The records in these views facilitate regulatory compliance auditing and provide insights on popular and frequently accessed tables and colu…”
   • [claimed-docs] “The user access history can be found by querying the ACCESS_HISTORY view in the ACCOUNT_USAGE and ORGANIZATION_USAGE schemas.”
   • [claimed-docs] “facilitate regulatory compliance auditing and provide insights on popular and frequently accessed tables and columns”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Unity Catalog docs explicitly state it enforces access control, tracks lineage of data and AI assets, and logs activity for auditing automatically across the workspace, and Delta history supports auditing operations. missing for 10: no independent/hands-on corroboration of column-level lineage granularity or audit log query examples, and no explicit mention of 'who ran what' query-level attribution beyond general activity logging.

   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [claimed-docs] “Use history information to audit operations, roll back a table, or query a table at a specific point in time using time travel.”
   • [claimed-docs] “You work with the objects Unity Catalog governs through Catalog Explorer, SQL, the Databricks CLI, and REST APIs.”

   proof ↗⚑ flag

2. platform-engineerCompliance attestations (SOC 2, HIPAA, PCI) are documented so security review does not stall the rollout

   weight 1 · round drawn
   Snowflake✓fullclaimed8/10

   Snowflake's dedicated Regulatory Compliance documentation explicitly lists per-certification pages for SOC 1 Type II, SOC 2 Type II, PCI DSS, and FedRAMP (a HIPAA-relevant standard), directly addressing the security-review documentation need. This is supported by first-party docs with named certifications, giving platform-engineers concrete attestation references. Missing for 10: an explicit named HIPAA compliance page/BAA reference and independent third-party corroboration of audit currency.

   • [claimed-docs] “Docs, "Regulatory compliance": "Snowflake is committed to meeting industry-standard regulatory compliance requirements", with per-certificat…”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Databricks' Trust Center compliance page explicitly documents SOC 2 Type II reports and a broader certification portfolio, directly addressing platform-engineer compliance-review needs, and this is reinforced by Unity Catalog's built-in access control, lineage, and audit logging documentation which supports such attestations operationally. Missing for 10: explicit mention of HIPAA and PCI attestations/BAA details in the evidence pack, and no independent/third-party audit confirmation beyond the vendor's own trust page.

   • [claimed-docs] “Databricks Trust Center compliance page ("Ensuring Security, Privacy, & Compliance") documents attestations including a SOC 2 Type II report…”
   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”

   proof ↗⚑ flag

Connectors

1. data-engineerFirst-party and partner connectors cover my sources — SaaS apps, databases, and ETL/ELT tools — with documented setup

   weight 2 · round to Databricks
   Snowflake~partialclaimed4/10

   The pack shows Snowflake integrates with ETL/ELT tooling (dbt Projects on Snowflake, managed dbt runtimes) and general data-loading mechanisms (Snowpipe, COPY INTO, Iceberg tables for external lakes) with documented setup, but it never documents a first-party/partner connector catalog for specific SaaS apps (e.g., Salesforce, HubSpot) or databases (e.g., Postgres, MySQL) — no Partner Connect, native connectors gallery, or marketplace connector docs are cited. Missing for 10: documented SaaS-app connector catalog, database-source connector docs, partner ETL/ELT integration listings beyond dbt.

   • [claimed-docs] “dbt Projects on Snowflake brings the full dbt lifecycle into Snowflake: develop, deploy, orchestrate, and observe your transformations in th…”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Apache Iceberg™ tables for Snowflake combine the performance and query semantics of typical Snowflake tables with external cloud storage tha…”
   • [claimed-docs] “No infrastructure to manage: Snowflake provides managed dbt Core and dbt Fusion runtimes.”

   proof ↗⚑ flag

   Databricks~partialclaimed6/10

   Databricks documents an ingestion hub for choosing 'standard connectors by data source' (Lakeflow Connect/Auto Loader) and a documented partner integration for dbt, plus a Marketplace listing partner data/tool assets — showing first-party and partner connector coverage with setup docs. However, the evidence pack lacks an explicit named catalog of SaaS-app/database connectors (e.g., Salesforce, Workday, specific DB connectors) with individual setup guides beyond dbt and generic Auto Loader ingestion. Missing for 10: an exhaustive/documented list of named SaaS and database connectors with per-connector setup instructions, and independent confirmation that connector coverage meets diverse source needs.

   • [claimed-docs] “Use it to choose a standard connector by data source and level of pipeline customization.”
   • [claimed-docs] “This page explains what dbt is, how to install dbt Core, and how to connect.”
   • [claimed-docs] “dbt Core enables you to write dbt code in the IDE of your choice on your local development machine and then run dbt from the command line.”
   • [claimed-docs] “dbt (data build tool) is a development environment for transforming data by writing select statements.”
   • [claimed-docs] “Incrementally and efficiently process new data files as they arrive in cloud storage.”
   • [claimed-docs] “publish offerings that Databricks customers can discover, evaluate, and connect with directly from their workspace”
   • [claimed-docs] “Listings include datasets, AI models, notebooks, apps, and Model Context Protocol (MCP) servers. This gives customers a single catalog for f…”

   proof ↗⚑ flag

Loading

1. data-engineerBulk-load CSV, JSON, and Parquet from cloud object storage with a single documented command

   weight 3 · round to Databricks
   Snowflake~partialcommunity5/10

   Evidence confirms Snowflake's COPY INTO/Snowpipe ingestion path from cloud stages (referenced via stream and Snowpipe docs, plus a community mention of COPY skipping already-loaded files and JSON Lines usage) and separate support for semi-structured JSON data types, but the pack never explicitly documents a single COPY INTO command example covering CSV, JSON, and Parquet together. missing for 10: explicit doc snippet naming CSV/Parquet file format support in COPY INTO, and a concrete single-command example spanning all three formats.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “SQL reference, "Semi-structured data types" (VARIANT/OBJECT/ARRAY) with guides "Introduction to loading semi-structured data", "Querying Sem…”
   • [community] “Regarding combining to a single file for loading: not necessary... Just make them JSON Lines. The COPY command will even skip files it has a…”

   proof ↗⚑ flag

   Databricks~partialclaimed6/10

   Databricks documents ingestion tooling (a connector-selection page for cloud object storage sources) and Auto Loader for incrementally/bulk processing new files as they arrive in cloud storage, which covers CSV/JSON/Parquet ingestion, but no evidence names a single specific command (e.g., COPY INTO) or shows a concrete one-line bulk-load example spanning all three formats. Missing for 10: explicit single documented command syntax for bulk-loading CSV/JSON/Parquet, and independent/hands-on confirmation of ease-of-use.

   • [claimed-docs] “Use it to choose a standard connector by data source and level of pipeline customization.”
   • [claimed-docs] “Incrementally and efficiently process new data files as they arrive in cloud storage.”
   • [claimed-docs] “Create and deploy an ETL (extract, transform, and load) pipeline for data orchestration using Lakeflow pipelines and Auto Loader.”

   proof ↗⚑ flag

2. data-engineerA managed service continuously ingests new files or events as they arrive, without me running my own pipeline infrastructure

   weight 2 · round drawn
   Snowflake✓fullcommunity8/10

   Snowpipe is a first-party managed service that automatically loads files from a stage as soon as they arrive, in micro-batches within minutes, without manual COPY scheduling or customer-run pipeline infrastructure (snowflake-docs-6/20/29/34/44/76). Community evidence corroborates continuous file-based loading behavior (COPY skipping already-loaded files) consistent with this pattern (snowflake-comm-4). Missing for 10: explicit documentation of event-driven/streaming ingestion (e.g., Snowpipe Streaming API or Kafka connector) and independent hands-on validation of the 'no pipeline infra' claim beyond vendor docs.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage.”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage.”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches”
   • [community] “Regarding combining to a single file for loading: not necessary... Just make them JSON Lines. The COPY command will even skip files it has a…”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Databricks provides Auto Loader/Lakeflow pipelines to incrementally and efficiently ingest new files as they arrive in cloud storage, plus Structured Streaming for continuous event processing with low latency and exactly-once guarantees on Delta Lake, all as managed serverless/DLT-style pipelines rather than self-managed infra, and a broader ingestion connector catalog for various sources. Missing for 10: independent/hands-on evidence of production reliability at scale for continuous ingestion, and more detail on serverless auto-scaling/operational overhead reduction claims beyond docs.

   • [claimed-docs] “Incrementally and efficiently process new data files as they arrive in cloud storage.”
   • [claimed-docs] “Create and deploy an ETL (extract, transform, and load) pipeline for data orchestration using Lakeflow pipelines and Auto Loader.”
   • [claimed-docs] “Process data for real-time workloads with end-to-end latency as low as five milliseconds.”
   • [claimed-docs] “Structured Streaming lets you express computation on streaming data in the same way you express a batch computation on static data.”
   • [claimed-docs] “Use Delta Lake tables as streaming sources and sinks with exactly-once processing guarantees.”
   • [claimed-docs] “Use it to choose a standard connector by data source and level of pipeline customization.”

   proof ↗⚑ flag

Notebooks

1. analystFirst-party notebooks let me mix SQL and Python against warehouse data, with results and charts inline

   weight 2 · round drawn
   Snowflake✓fullcommunity8/10

   Snowflake Notebooks is a first-party, cell-based Snowsight interface supporting Python, SQL, and Markdown in the same notebook with cell-by-cell execution and result comparison, directly matching the story. Missing for 10: explicit documentation/screenshots of inline chart rendering within notebooks and independent/hands-on user corroboration beyond vendor docs.

   • [claimed-docs] “Write SQL or Python code and quickly compare results with cell-by-cell development and execution.”
   • [claimed-docs] “Snowflake Notebooks is a unified development interface in Snowsight that offers an interactive, cell-based programming environment for Pytho…”
   • [claimed-docs] “you can leverage your Snowflake data to perform exploratory data analysis, develop machine learning models, and perform other data science a…”
   • [community] “Snowflake's preview app called Snowsight provides a way to both query and visualize the data.”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Databricks notebooks docs explicitly describe multi-language coauthoring, automatic versioning, and built-in visualizations, and the getting-started guide shows querying Unity Catalog data and visualizing results inline in a notebook — directly matching the analyst story of mixing SQL/Python with inline charts. Missing for 10: explicit documentation of magic-command language switching within a single notebook cell (%sql/%python) and independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “Databricks notebooks provide real-time coauthoring in multiple languages, automatic versioning, and built-in data visualizations”
   • [claimed-docs] “Databricks notebooks provide real-time coauthoring in multiple languages, automatic versioning, and built-in data visualizations for develop…”
   • [claimed-docs] “Use a Databricks notebook to query sample data stored in Unity Catalog and then visualize the query results in the notebook.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Snowflake
   Snowflake~partialprobed6/10

   Snowflake exposes broad programmatic surfaces — the SQL API and REST APIs for resource management (queries, provisioning users/roles, tables), Snowpark APIs, Snowflake CLI for managing apps/workloads, and OpenAPI-compliant specs published on GitHub — indicating strong API/UI parity ambitions for developers and AI agents (docs-65, docs-66, docs-72, docs-73, snowflake-supp-openapi-specs, docs-1). However there is no explicit vendor claim or independent verification of full 1:1 parity between every Snowsight UI feature (e.g., notebooks cell UI, query profile visualizations, Cortex Analyst chat UI) and API equivalents, and a live probe found no discoverable openapi.json at conventional doc paths. Missing for 10: an explicit parity statement or audit confirming every UI action has an API/CLI equivalent, and independent/hands-on confirmation that AI-native workflows can fully replace UI usage.

   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [claimed-docs] “Snowflake REST APIs enable developers and partners to use the language of their choice to build integrations with Snowflake using the openAP…”
   • [claimed-docs] “You can use this API to develop custom applications and integrations that: Perform queries, Manage your deployment (e.g. provision users and…”
   • [claimed-docs] “Official snowflakedb/snowflake-rest-api-specs repo (specifications/ + collections/): "These REST APIs are compliant with the OpenAPI specifi…”
   • [claimed-docs] “With Snowflake CLI, developers can create, manage, update, and view apps running on Snowflake across workloads such as Streamlit in Snowflak…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.snowflake.com/openapi.json, https://docs.snowflake.com/swagger.json, https://docs.snowf…”

   proof ↗⚑ flag

   Databricks!disputedcontradicted5/10

   Databricks documents an extensive, versioned REST API surface (workspace-level API reference, SDKs, Terraform provider, CLI that itself is a thin wrapper around the REST API — `databricks api`) and states that Unity Catalog objects can be managed via 'Catalog Explorer, SQL, the Databricks CLI, and REST APIs,' suggesting broad UI/API parity. However, a hands-on community report specifically contradicts full parity, stating 'no good way to get usage info programmatically' and calling out other CLI/SQL config gaps (e.g., can't set Spark config easily), showing some UI-visible functionality isn't cleanly exposed via API. Missing for 10: a documented comprehensive parity guarantee, independent confirmation that admin/UI-only features (budgets, workspace settings) are fully scriptable, and resolution of the community-reported programmatic usage-info gap.

   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”
   • [claimed-docs] “You work with the objects Unity Catalog governs through Catalog Explorer, SQL, the Databricks CLI, and REST APIs.”
   • [claimed-docs] “you learn how to automate Databricks operations and accelerate development with the Databricks SDK for Python”
   • [probe] “PROBE runtime (recorded 2026-09-06): the Databricks CLI installed via the vendor's brew tap and printed `Databricks CLI v1.15.0` keylessly; …”
   • [community] “No persist() so can't cache dataframes; no good way to get usage info programmatically; can't set Spark config easily (had to hack S3A crede…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Databricks
   Snowflake~partialcommunity5/10

   Snowflake supports Apache Iceberg tables backed by open, customer-managed cloud storage, which is a genuine open-format, portable-data path, and it exposes SQL/REST APIs for programmatic data extraction. However, there is no direct documentation in the evidence pack of a comprehensive 'export all your data and leave' workflow (e.g., bulk UNLOAD/COPY INTO to open formats for all tables, migration tooling, or explicit anti-lock-in guidance), and community commentary even frames Snowflake's stickiness/lock-in as a concern rather than confirming easy full data egress. Missing for 10: documented bulk export/unload feature for all data, first-party migration/exit tooling, and independent confirmation that a full data exit is straightforward.

   • [claimed-docs] “Apache Iceberg™ tables for Snowflake combine the performance and query semantics of typical Snowflake tables with external cloud storage tha…”
   • [claimed-docs] “They are ideal for existing data lakes that you cannot, or choose not to, store in Snowflake.”
   • [claimed-docs] “Snowflake REST APIs for resource management provide a set of endpoints that lets users programmatically interact with and control various re…”
   • [claimed-docs] “The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database.”
   • [community] “I predict we'll see more people choosing Clickhouse over Snowflake in the next 5 years... and give people a better escape hatch if they want…”

   proof ↗⚑ flag

   Databricks~partialcommunity6/10

   Databricks stores data in the open Delta Lake/Parquet format and offers Delta Sharing (OpenSharing) to share or export data outside the organization regardless of platform, plus CLI/SDK/REST API access for programmatic extraction of data and metadata. However, there's no single documented 'export everything and leave' workflow or bulk account-export tool, and community commentary (e.g., migrating workloads to Postgres) suggests migration is done piecemeal rather than via a turnkey export feature. missing for 10: a dedicated full-account/bulk data export or migration tool, and independent hands-on confirmation of frictionless full data egress.

   • [claimed-docs] “OpenSharing is the secure data sharing platform in Databricks that lets you share data and AI assets with users outside your organization, r…”
   • [claimed-docs] “The Open Marketplace, which does not require access to a Databricks workspace.”
   • [claimed-docs] “You work with the objects Unity Catalog governs through Catalog Explorer, SQL, the Databricks CLI, and REST APIs.”
   • [claimed-docs] “This reference contains information about the Databricks workspace-level application programming interfaces (APIs).”
   • [community] “We've been moving our workflows out of Databricks to PostgreSQL to save a ton.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Snowflake—none0/10

   The evidence pack includes compliance certifications (SOC 2, ISO, FedRAMP, PCI DSS) but contains no mention of region selection, data residency controls, or ability to choose a storage location/cloud region for an account or database. No documentation cited addresses this specific capability.

   ⚑ flag

   Databricks—none0/10

   No evidence in the pack addresses regional deployment, data residency controls, or workspace region selection for Databricks; the compliance mention only covers SOC 2 attestations, not data-location choice.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Snowflake—none0/10

   The axis applies since Snowflake offers AI/Cortex features built on third-party LLMs, making data-use-for-training a fair privacy concern, but no evidence pack item documents an opt-out control, data-processing agreement, or explicit statement that customer data is excluded from model training. Compliance certifications and RBAC/access-history items are about general security/governance, not AI-training data use.

   ⚑ flag

   Databricks—none0/10

   The evidence pack covers Databricks' data platform, governance, agent, and dev-tool features but contains no mention of any control to opt out of, or prevent, customer data being used to train Databricks' (or third-party) AI models — no data-use policy, model-training opt-out setting, or contractual guarantee is cited. missing for 10: an explicit AI-training opt-out/data-use policy, documentation of contractual or technical controls preventing model training on customer data, and any independent confirmation of such a guarantee.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Snowflake
   Snowflake~partialclaimed5/10

   Snowflake's Time Travel docs show a defined retention window for querying/restoring changed or deleted data, and RBAC plus compliance certifications provide governance context, giving an AI-native user some levers over data lifecycle and access. Missing for 10: explicit documentation of configuring the retention period (e.g., DATA_RETENTION_TIME_IN_DAYS parameter), explicit purge/permanent-delete commands, and any GDPR/right-to-erasure specific deletion guarantees.

   • [claimed-docs] “Using Time Travel, you can perform the following actions within a defined period of time: Query data in the past that has since been updated…”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted.”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted. You can restore individual objects, such as tables, or restore…”
   • [claimed-docs] “Snowflake Time Travel enables accessing historical data (that is, data that has been changed or deleted) at any point within a defined perio…”
   • [claimed-docs] “Role-based Access Control (RBAC): Access privileges are assigned to roles, which are in turn assigned to users.”
   • [claimed-docs] “Docs, "Regulatory compliance": "Snowflake is committed to meeting industry-standard regulatory compliance requirements", with per-certificat…”

   proof ↗⚑ flag

   Databricks—none0/10

   Evidence covers Unity Catalog governance (access control, lineage, audit logging) and Delta Lake time-travel/versioning, but nothing documents user-controllable data retention periods, deletion/erasure APIs, or lifecycle policies for AI-native privacy control. Missing for 10: explicit retention configuration, right-to-delete/erasure mechanisms, data lifecycle/expiry policy documentation, and any independent verification of deletion behavior.

   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [claimed-docs] “Use history information to audit operations, roll back a table, or query a table at a specific point in time using time travel.”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Snowflake—none0/10

   No evidence pack item mentions telemetry, usage tracking, or an opt-out mechanism for Snowflake's own product telemetry; only compliance certifications and access-history/audit features are documented, which don't address user-facing telemetry opt-out. This axis is applicable to any AI-native SaaS product, so absence of evidence yields 'none'. Missing for 10: any documentation of a telemetry/usage-data collection policy or an opt-out/opt-in control for such tracking.

   ⚑ flag

   Databricks—none0/10

   No evidence pack item addresses telemetry/usage-tracking opt-out settings for Databricks; documentation covers compliance/SOC2 but not a specific telemetry toggle. missing for 10: any mention of telemetry collection, opt-out settings, or usage-tracking controls.

   ⚑ flag

Semantics

1. analystDefine a governed semantic model — metrics, dimensions, and joins declared once — that queries and AI tools answer against consistently

   weight 2 · round to Databricks
   Snowflake✓fullclaimed7/10

   Snowflake's Semantic Views let analysts declare business metrics, entities, and relationships once as schema-level objects, and Cortex Analyst answers natural-language questions against this same semantic layer without writing SQL, while Cortex Agents/MCP expose it to AI tools — directly matching the story of a governed semantic model queried consistently by both SQL and AI. missing for 10: no independent/community corroboration of Semantic Views in practice, and no detail on how BI/SQL query tools (beyond Cortex Analyst) consistently reuse the same semantic definitions.

   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object. You can define busines…”
   • [claimed-docs] “You can define business metrics and model business entities and their relationships.”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View ... define business metrics and model business entities…”
   • [claimed-docs] “You can store semantic business concepts directly in the database in a Semantic View, which is a schema-level object.”
   • [claimed-docs] “With Cortex Analyst, business users can ask questions in natural language and receive direct answers without writing SQL.”
   • [claimed-docs] “business users can ask questions in natural language and receive direct answers without writing SQL”
   • [claimed-docs] “The Snowflake-managed MCP server lets AI agents securely retrieve data from Snowflake accounts without needing to deploy separate infrastruc…”
   • [claimed-docs] “You can configure the MCP server to serve Cortex Analyst, Cortex Search, and Cortex Agents as tools, along with custom tools and SQL executi…”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Databricks Unity Catalog Metric Views let analysts define metrics, dimensions, and joins once ('you define the metric once... users can group by any available field. The query engine generates the correct computation') and this governed semantic layer is queryable consistently from SQL, AI/BI dashboards, Genie natural-language Q&A, and external BI tools like Power BI, Tableau, and Sigma. missing for 10: independent/hands-on corroboration of consistency across tools, and detail on join declaration beyond metric definition.

   • [claimed-docs] “you define the metric once, for example _sum of revenue divided by distinct customer count_, and users can group by any available field.”
   • [claimed-docs] “you define the metric once, for example sum of revenue divided by distinct customer count, and users can group by any available field”
   • [claimed-docs] “you define the metric once, for example sum of revenue divided by distinct customer count, and users can group by any available field. The q…”
   • [claimed-docs] “Query metric views from Power BI, Tableau, Sigma, and other external BI tools.”
   • [claimed-docs] “Define business metrics with consistent calculations using a semantic layer. Reuse metrics across queries and dashboards.”
   • [claimed-docs] “Ask data questions in natural language and get answers grounded in your organization's data.”

   proof ↗⚑ flag

Sharing

1. analystA marketplace of third-party datasets lets me enrich my own data directly inside the platform

   weight 1 · round to Databricks
   Snowflake—none0/10

   The evidence pack only documents Secure Data Sharing (share selected objects between Snowflake accounts) but contains no mention of a marketplace, data exchange, or third-party dataset listings that an analyst could browse and directly enrich their own data with — the specific marketplace capability described in the story is absent from the pack.

   • [claimed-docs] “Secure Data Sharing lets you share selected objects in a database in your account with other Snowflake accounts.”
   • [claimed-docs] “Secure Data Sharing lets you share selected objects in a database in your account with other Snowflake accounts. ... no actual data is copie…”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Databricks Marketplace is documented as an in-platform catalog where customers can discover, evaluate, and connect directly to third-party datasets (plus AI models, notebooks, apps, MCP servers) from within their workspace, and an Open Marketplace variant even works without a workspace. This directly matches the analyst story of enriching own data with third-party datasets inside the platform. Missing for 10: no independent/hands-on evidence of the enrichment workflow in practice, and no detail on how a discovered dataset is joined/merged with an analyst's own tables.

   • [claimed-docs] “The Open Marketplace, which does not require access to a Databricks workspace.”
   • [claimed-docs] “Listings include datasets, AI models, notebooks, apps, and Model Context Protocol (MCP) servers.”
   • [claimed-docs] “publish offerings that Databricks customers can discover, evaluate, and connect with directly from their workspace”
   • [claimed-docs] “Listings include datasets, AI models, notebooks, apps, and Model Context Protocol (MCP) servers. This gives customers a single catalog for f…”

   proof ↗⚑ flag

2. data-engineerShare live datasets with another account or organization without copying data or building an export pipeline

   weight 2 · round drawn
   Snowflake✓fullclaimed9/10

   Snowflake's Secure Data Sharing directly delivers this story: it lets accounts share selected database objects with other Snowflake accounts, with docs explicitly stating no actual data is copied or transferred between accounts, eliminating the need for export pipelines. This is a first-party, well-documented core Snowflake feature (also referenced as part of Standard plan capabilities). Missing for 10: independent/hands-on third-party confirmation of cross-organization sharing experience beyond vendor docs.

   • [claimed-docs] “Secure Data Sharing lets you share selected objects in a database in your account with other Snowflake accounts.”
   • [claimed-docs] “Secure Data Sharing lets you share selected objects in a database in your account with other Snowflake accounts. ... no actual data is copie…”
   • [claimed-docs] “Standard: An entry-level, introductory offering providing access to core functionality. ... Security with automatic encryption of all data, …”

   proof ↗⚑ flag

   Databricks✓fullclaimed9/10

   Delta Sharing (OpenSharing) is documented as a secure data sharing platform for sharing data and AI assets outside the organization without requiring the recipient to be on Databricks, explicitly avoiding data copying/export pipelines, and the Marketplace/Open Marketplace extends this to discovery and listing of shared datasets across organizations. missing for 10: independent hands-on validation of cross-account sharing beyond vendor docs.

   • [claimed-docs] “OpenSharing is the secure data sharing platform in Databricks that lets you share data and AI assets with users outside your organization, r…”
   • [claimed-docs] “The Open Marketplace, which does not require access to a Databricks workspace.”
   • [claimed-docs] “Listings include datasets, AI models, notebooks, apps, and Model Context Protocol (MCP) servers.”
   • [claimed-docs] “publish offerings that Databricks customers can discover, evaluate, and connect with directly from their workspace”
   • [claimed-docs] “Listings include datasets, AI models, notebooks, apps, and Model Context Protocol (MCP) servers. This gives customers a single catalog for f…”

   proof ↗⚑ flag

Lakehouse

1. data-engineerQuery open table formats and files in object storage — Iceberg, Delta, Parquet — without first loading them into proprietary storage

   weight 2 · round to Snowflake
   Snowflake✓fullclaimed8/10

   Snowflake supports Apache Iceberg tables directly on customer-managed external cloud storage, explicitly positioned for 'existing data lakes that you cannot, or choose not to, store in Snowflake,' and Snowpipe/COPY plus external stages allow querying files in object storage without loading them into proprietary storage. Missing for 10: explicit docs on Delta Lake table querying and independent hands-on benchmarks confirming performance parity for external Iceberg/Delta queries.

   • [claimed-docs] “Apache Iceberg™ tables for Snowflake combine the performance and query semantics of typical Snowflake tables with external cloud storage tha…”
   • [claimed-docs] “They are ideal for existing data lakes that you cannot, or choose not to, store in Snowflake.”

   proof ↗⚑ flag

   Databricks~partialclaimed6/10

   Docs confirm Databricks SQL runs directly on the data lake with ANSI SQL and Delta Lake extensions 'without moving your data' (databricks-docs-32), and Unity Catalog governs tables/external locations directly in object storage (databricks-docs-19, databricks-docs-38, databricks-docs-46). However, the evidence pack never explicitly mentions querying Iceberg tables or plain Parquet files in-place (e.g., via UniForm or external tables) — missing for 10: explicit Iceberg format support, Parquet file querying without ingestion, and independent/hands-on confirmation of in-place multi-format querying.

   • [claimed-docs] “It runs directly on your data lake, supports ANSI SQL with Delta Lake extensions, and provides the tools to build highly performant, cost-ef…”
   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”
   • [claimed-docs] “Unity Catalog operates beneath every data and AI interaction in your workspaces automatically: enforcing access control when you query a tab…”
   • [claimed-docs] “Create a table and grant privileges in Databricks using the Unity Catalog data governance model.”
   • [claimed-docs] “You work with the objects Unity Catalog governs through Catalog Explorer, SQL, the Databricks CLI, and REST APIs.”

   proof ↗⚑ flag

Performance

1. data-engineerInspect query profiles and execution plans to find why a query is slow or expensive

   weight 2 · round drawn
   Snowflake✓fullcommunity8/10

   Snowsight's Query History page lets data engineers monitor executed queries and drill into a detailed query profile that explores each step of execution, directly supporting root-cause analysis of slow/expensive queries; this is corroborated by community mention of Snowsight's query/visualize UI. missing for 10: no independent hands-on account of using query profile specifically to diagnose a slow query, and no detail on cost-per-query attribution tooling (one community comment even notes lack of query-level cost attribution).

   • [claimed-docs] “With the Query History page in Snowsight, you can do the following: Monitor individual or grouped queries that are executed by users in your…”
   • [claimed-docs] “The Query History page lets you explore queries executed in your Snowflake account over the last 14 days.”
   • [claimed-docs] “Explore each step of an executed query in the query profile.”
   • [claimed-docs] “Monitor individual or grouped queries that are executed by users in your account.”
   • [community] “Snowflake's preview app called Snowsight provides a way to both query and visualize the data.”
   • [community] “The problem with Snowflake is particularly worse due to its lack of query level attribution of costs and no in-built features for monitoring…”

   proof ↗⚑ flag

   Databricks✓fullclaimed8/10

   Docs explicitly describe inspecting execution plans to find bottlenecks/optimization opportunities and automatic insights/recommendations for inefficient queries, directly matching the story. This is first-party documentation without independent hands-on corroboration or deeper detail on cost/spill/skew diagnostics. Missing for 10: independent/community validation of query profile usability, and more detail on cost breakdown metrics beyond the brief doc snippets.

   • [claimed-docs] “Get automatic insights and recommendations when queries run inefficiently.”
   • [claimed-docs] “Inspect the execution plan for a query to identify bottlenecks and optimization opportunities.”
   • [claimed-docs] “It runs directly on your data lake, supports ANSI SQL with Delta Lake extensions, and provides the tools to build highly performant, cost-ef…”

   proof ↗⚑ flag

Recovery

1. data-engineerTime-travel — query data as of a past point and restore dropped or corrupted tables from history

   weight 2 · round drawn
   Snowflake✓fullclaimed9/10

   Snowflake's documented Time Travel feature explicitly supports querying data as of a past point and restoring accidentally/intentionally deleted objects (tables, schemas, databases) within a retention window, directly matching the story; Clone/UNDROP mechanics and object cloning (inheriting privileges) further support restoration workflows. Missing for 10: no independent/hands-on corroboration of restore success or retention-period limits from community evidence.

   • [claimed-docs] “Using Time Travel, you can perform the following actions within a defined period of time: Query data in the past that has since been updated…”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted.”
   • [claimed-docs] “Query data in the past that has since been updated or deleted.”
   • [claimed-docs] “Restoring objects that might have been accidentally or intentionally deleted. You can restore individual objects, such as tables, or restore…”
   • [claimed-docs] “Snowflake Time Travel enables accessing historical data (that is, data that has been changed or deleted) at any point within a defined perio…”
   • [claimed-docs] “the clone inherits all granted privileges on the clones of all child objects contained in the source object”
   • [claimed-docs] “If the source object is a database or schema, the clone inherits all granted privileges on the clones of all child objects contained in the …”

   proof ↗⚑ flag

   Databricks✓fullclaimed9/10

   Databricks documents Delta Lake history/time travel explicitly: querying tables as of a past version/timestamp and restoring/rolling back dropped or corrupted tables using history information, directly matching the story. This is a core, well-documented Delta Lake feature integrated into Databricks SQL/Unity Catalog. Missing for 10: no independent/hands-on corroboration of restore-after-drop specifically, beyond first-party docs.

   • [claimed-docs] “Use history information to audit operations, roll back a table, or query a table at a specific point in time using time travel.”

   proof ↗⚑ flag

Sql

1. analystI get a full analytical SQL surface — window functions, CTEs, semi-structured JSON, arrays, and rich date/time types — without bolt-on extensions

   weight 3 · round to Snowflake
   Snowflake~partialcommunity7/10

   Docs confirm window functions, semi-structured VARIANT/OBJECT/ARRAY types, and Time Travel/date handling are native SQL features, and community evidence corroborates JSON handling via COPY/JSON Lines. However, one community report notes a gap versus generate_series-style sequence generation, and CTE support and rich date/time type breadth aren't directly evidenced in the pack. missing for 10: explicit CTE documentation, comprehensive date/time type reference, independent corroboration beyond the noted generate_series gap.

   • [claimed-docs] “SQL reference, "Window functions": "Window functions are analytic functions that you can use for various calculations such as running totals…”
   • [claimed-docs] “SQL reference, "Semi-structured data types" (VARIANT/OBJECT/ARRAY) with guides "Introduction to loading semi-structured data", "Querying Sem…”
   • [community] “Snowflake doesn't have a generate_series function equivalent. The closest thing it has is a generator function which only accepts constants.”
   • [community] “Regarding combining to a single file for loading: not necessary... Just make them JSON Lines. The COPY command will even skip files it has a…”
   • [claimed-docs] “Using Time Travel, you can perform the following actions within a defined period of time: Query data in the past that has since been updated…”

   proof ↗⚑ flag

   Databricks~partialclaimed5/10

   Databricks SQL is documented as ANSI-SQL compliant with Delta Lake extensions (databricks-docs-32) and Unity Catalog governs SQL objects (databricks-docs-56), implying a broad native SQL surface without bolt-on tools, but the evidence pack never explicitly calls out window functions, CTEs, JSON/semi-structured handling, array types, or date/time type richness. missing for 10: explicit doc citations for window functions, CTE support, JSON/semi-structured query functions, array manipulation functions, and native date/time types.

   • [claimed-docs] “It runs directly on your data lake, supports ANSI SQL with Delta Lake extensions, and provides the tools to build highly performant, cost-ef…”
   • [claimed-docs] “You work with the objects Unity Catalog governs through Catalog Explorer, SQL, the Databricks CLI, and REST APIs.”
   • [claimed-docs] “enforcing access control when you query a table or call a model, tracking lineage as data and AI assets are used, logging activity for audit…”

   proof ↗⚑ flag

Streaming

1. data-engineerRun continuous or incremental transformations — streams, tasks, declarative pipelines, or continuous queries — inside the platform

   weight 1 · round to Databricks
   Snowflake✓fullclaimed8/10

   Snowflake documents Streams for CDC-based incremental change capture (doc-7/21/38/54), Dynamic Tables (GA, doc-15) for declarative continuous transformation pipelines, and Snowpipe for continuous/micro-batch ingestion (doc-6/20/29/34/44/76) — directly matching the story's streams/declarative-pipeline/continuous-processing capabilities inside the platform. Missing for 10: explicit documentation of the Tasks object (scheduling/orchestration companion to Streams), Snowpipe Streaming (true low-latency continuous ingestion) specifics, and independent/hands-on validation of these pipelines at production scale.

   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “CREATE OR ALTER DYNAMIC TABLE (General availability)”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts (including COPY INTO), updates, and delet…”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables, including inserts, updates, and deletes”
   • [claimed-docs] “A stream object records data manipulation language (DML) changes made to tables... so that actions can be taken using the changed data”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches”

   proof ↗⚑ flag

   Databricks✓fullclaimed9/10

   Databricks documents Structured Streaming for continuous/incremental processing with exactly-once guarantees and low-latency options, Lakeflow declarative pipelines with Auto Loader for incremental ingestion/ETL, and Databricks Workflows/Jobs orchestration referenced via CLI/tasks. This directly covers streams, declarative pipelines, and continuous/incremental transformations inside the platform. Missing for 10: no independent/hands-on benchmark validating claimed low-latency figures, and no explicit mention of scheduled/triggered task orchestration UI beyond CLI/Lakeflow docs.

   • [claimed-docs] “Create and deploy an ETL (extract, transform, and load) pipeline for data orchestration using Lakeflow pipelines and Auto Loader.”
   • [claimed-docs] “Incrementally and efficiently process new data files as they arrive in cloud storage.”
   • [claimed-docs] “Process data for real-time workloads with end-to-end latency as low as five milliseconds.”
   • [claimed-docs] “Structured Streaming lets you express computation on streaming data in the same way you express a batch computation on static data.”
   • [claimed-docs] “Use Delta Lake tables as streaming sources and sinks with exactly-once processing guarantees.”
   • [claimed-docs] “Develop and deploy your first ETL (extract, transform, and load) pipeline for data orchestration with Apache Spark™.”

   proof ↗⚑ flag

2. data-engineerStreaming writes land queryable within seconds through a documented streaming ingestion API

   weight 2 · round to Databricks
   Snowflake~partialclaimed4/10

   Snowflake documents Snowpipe as a streaming/micro-batch ingestion API, but the documentation explicitly states data becomes available 'within minutes,' not seconds, directly at odds with the story's 'queryable within seconds' requirement. There is no evidence pack mention of the lower-latency Snowpipe Streaming API or REST-based streaming ingestion that could close this gap. Missing for 10: documented sub-second/seconds-level ingestion latency, evidence of a dedicated low-latency streaming ingestion API (e.g., Snowpipe Streaming), and independent/hands-on confirmation of near-real-time query availability.

   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage.”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage.”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they’re available in a stage. This means you can load data from files in micro-batches, …”
   • [claimed-docs] “Snowpipe enables loading data from files as soon as they're available in a stage. This means you can load data from files in micro-batches”

   proof ↗⚑ flag

   Databricks✓fullclaimed7/10

   Databricks documents Structured Streaming as a first-class streaming API that treats streaming like batch, supports Delta Lake tables as streaming sources/sinks with exactly-once guarantees, and Auto Loader for incremental ingestion from cloud storage, with end-to-end latency claimed as low as 5ms — directly supporting near-real-time queryable ingestion. missing for 10: independent/hands-on benchmark confirming 'queryable within seconds' end-to-end, and no community corroboration specific to streaming latency claims.

   • [claimed-docs] “Structured Streaming lets you express computation on streaming data in the same way you express a batch computation on static data.”
   • [claimed-docs] “Incrementally and efficiently process new data files as they arrive in cloud storage.”
   • [claimed-docs] “Use Delta Lake tables as streaming sources and sinks with exactly-once processing guarantees.”
   • [claimed-docs] “Process data for real-time workloads with end-to-end latency as low as five milliseconds.”
   • [claimed-docs] “Create and deploy an ETL (extract, transform, and load) pipeline for data orchestration using Lakeflow pipelines and Auto Loader.”

   proof ↗⚑ flag