Databricks vs MotherDuck

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
   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

   MotherDuck✓fullprobed8/10

   MotherDuck ships official CLI/SDK/API access (docs-1, docs-2, docs-25), a documented auth flow with local credential caching (docs-8, docs-20), and both local and remote MCP servers that execute read-only/read-write SQL and support schema/context discovery via 'Guides' (docs-30, docs-49, docs-38), letting an agent authenticate, discover, query and read results with no dashboard involved. This is corroborated by runtime probes showing a real authenticated MCP handshake plus executed aggregate SQL query (motherduck-probe-rt-2) and a live OAuth-gated remote MCP endpoint (motherduck-probe-rt-3). Missing for 10: an end-to-end demonstration against an authenticated (non-keyless) MotherDuck cloud database showing schema discovery + query + result retrieval in one continuous agent session, and clearer documentation of a dedicated schema-listing API beyond Guides.

   • [claimed-docs] “Connect to MotherDuck using official drivers and APIs for various programming languages.”
   • [claimed-docs] “you can securely save your credentials locally”
   • [claimed-docs] “If you are using Python or CLI and don't want to authenticate every session, you can securely save your credentials locally.”
   • [claimed-docs] “Read and write Guides — markdown documents that capture your org's metric definitions, join conventions, and domain context, so agents produ…”
   • [claimed-docs] “To restrict your AI assistant to read-only access, see Restricting to read-only access”
   • [claimed-docs] “The remote MCP server exposes both read-only and read-write tools.”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”
   • [probe] “official CLI documented at https://duckdb.org/docs/installation/”

   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 drawn
   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

   MotherDuck✓fullprobed8/10

   MotherDuck ships both a remote MCP server and a Dives natural-language interface that write, execute, and iteratively refine SQL/visualizations against user schemas via conversational prompts (e.g., 'add a filter for US region', 'build a chart of top 10 products'), and runtime probes confirm the MCP handshake and real query execution work end-to-end. Guides let the assistant learn schema/metric context to produce accurate SQL without repetitive prompting, directly matching the story's 'against my schemas' requirement. missing for 10: independent hands-on evidence specifically of the assistant 'explaining' or fixing broken SQL (evidence focuses on generation/iteration, not debugging existing queries), and broader third-party corroboration beyond vendor docs.

   • [claimed-docs] “Analyze your data with natural language using the remote MCP Server”
   • [claimed-docs] “Build a Dive with a chart of our top 10 products by sales volume. Use MotherDuck's brand colors”
   • [claimed-docs] “you iterate conversationally ("add a filter for US region", "switch to a bar chart") and the Viewer updates in place.”
   • [claimed-docs] “The MotherDuck remote MCP Server lets you analyze your data using natural language and generate interactive visualizations, all without writ…”
   • [claimed-docs] “Read and write Guides — markdown documents that capture your org's metric definitions, join conventions, and domain context, so agents produ…”
   • [claimed-docs] “The remote MCP server exposes both read-only and read-write tools.”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”

   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
   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

   MotherDuck~partialprobed6/10

   MotherDuck ships concrete building blocks for this story: MCP-based natural-language querying (Dives, remote/local MCP servers) and 'Guides' — markdown docs capturing org metric definitions, join conventions, and domain context so agents produce accurate SQL without repetitive prompting, i.e. a governance/semantic-grounding mechanism directly aimed at preventing hallucinated joins. Governance controls (read-only restriction, SaaS Mode, role-based Shares) reinforce this for business users. Missing for 10: independent/hands-on evidence that Guides actually reduce hallucinated joins in practice, no case study or benchmark showing accuracy improvement, and the semantic layer relies on manually authored Guides rather than an automated governed semantic model.

   • [claimed-docs] “Read and write Guides — markdown documents that capture your org's metric definitions, join conventions, and domain context, so agents produ…”
   • [claimed-docs] “To restrict your AI assistant to read-only access, see Restricting to read-only access”
   • [claimed-docs] “The remote MCP server exposes both read-only and read-write tools.”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “The MotherDuck remote MCP Server lets you analyze your data using natural language and generate interactive visualizations, all without writ…”
   • [claimed-docs] “Build a Dive with a chart of our top 10 products by sales volume. Use MotherDuck's brand colors”
   • [claimed-docs] “you iterate conversationally ("add a filter for US region", "switch to a bar chart") and the Viewer updates in place.”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to MotherDuck
   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

   MotherDuck✓fullprobed9/10

   MotherDuck publishes a working llms.txt (HTTP 200, verified content) and goes further with a first-class agent-discovery surface: an agentskills.io-conformant manifest at /.well-known/agent-skills/index.json, /.well-known/mcp.json, and an every-page-as-markdown convention, explicitly framed as agent-oriented docs. This directly matches the story of pointing an agent at llms.txt or agent docs. Missing for 10: independent/community confirmation that an agent successfully consumed these files in practice (only first-party probes cited).

   • [probe] “PROBE llms.txt: HTTP 200 at https://motherduck.com/llms.txt # MotherDuck MotherDuck is a modern serverless data warehouse built on DuckDB. …”
   • [probe] “PROBE runtime (recorded 2026-09-06): MotherDuck publishes an agentskills.io-conformant discovery manifest at /.well-known/agent-skills/index…”
   • [probe] “official MCP server documented at https://motherduck.com/docs/sql-reference/mcp/”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   MotherDuck✓fullprobed8/10

   MotherDuck supports headless/CI automation via CLI, Python SDKs, saved credentials for non-interactive sessions, and scheduled Python jobs for ingest/transformation; dbt integration and SaaS Mode further support scripted, non-interactive pipelines. Runtime probes confirm a keyless CLI roundtrip and a fully automatable MCP server flow, both consistent with CI usage. Missing for 10: an explicit CI/CD example (e.g., GitHub Actions workflow) or documented non-interactive auth token flow for pipelines.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “you can securely save your credentials locally”
   • [claimed-docs] “If you are using Python or CLI and don't want to authenticate every session, you can securely save your credentials locally.”
   • [claimed-docs] “You can limit MotherDuck's ability to interact with your local environment using SaaS Mode”
   • [claimed-docs] “dbt-duckdb is the adapter which allows dbt to use DuckDB and MotherDuck.”
   • [probe] “PROBE runtime (recorded 2026-09-06): the engine under MotherDuck ran FULLY keyless on a laptop — `duckdb -c` built a 1,000,000-row table and…”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”

   proof ↗⚑ flag

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

   weight 3 · round to Databricks
   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

   MotherDuck—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

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

   weight 3 · round to MotherDuck
   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

   MotherDuck✓fullprobed9/10

   MotherDuck ships both a remote hosted MCP server (api.motherduck.com/mcp, OAuth-secured) and an official local MCP server (mcp-server-motherduck), both well documented with read/write SQL tool access, and runtime probes confirm the local server completes a full stdio handshake and executes a real query, while the remote endpoint is live and speaks proper MCP OAuth. Missing for 10: no independent third-party hands-on report of the remote MCP server itself (only official docs and probes) and no community corroboration of production-grade reliability at scale.

   • [claimed-docs] “Analyze your data with natural language using the remote MCP Server”
   • [claimed-docs] “Local MCP server for DuckDB and MotherDuck”
   • [claimed-docs] “For local DuckDB databases, custom configurations, or self-hosted scenarios, use the local MCP server”
   • [claimed-docs] “use the **local MCP server** (mcp-server-motherduck)”
   • [claimed-docs] “The remote MCP server exposes both read-only and read-write tools.”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [probe] “official MCP server documented at https://motherduck.com/docs/sql-reference/mcp/”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Databricks
   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

   MotherDuck~partialprobed6/10

   MotherDuck relies on the DuckDB CLI (an official, third-party-maintained but DuckDB-branded CLI) to connect directly to MotherDuck, and docs describe CLI-based authentication/credential caching, but there is no MotherDuck-specific CLI (e.g., a 'motherduck' binary) with agentic/AI-native command features documented. missing for 10: a dedicated MotherDuck-branded CLI tool, evidence of AI-native/agentic command support within the CLI itself, and independent hands-on confirmation of CLI workflows beyond basic connection.

   • [claimed-docs] “Install the DuckDB CLI and connect directly to MotherDuck”
   • [claimed-docs] “you can securely save your credentials locally”
   • [claimed-docs] “If you are using Python or CLI and don't want to authenticate every session, you can securely save your credentials locally.”
   • [probe] “official CLI documented at https://duckdb.org/docs/installation/”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   MotherDuck✓fullprobed9/10

   MotherDuck publishes a documented public API surface: official SDKs/drivers in multiple languages, a live OpenAPI spec (probe confirms HTTP 200 with 'openapi' key), and a documented SQL/MCP interface with both local and remote MCP servers verified working end-to-end at runtime. Machine-readable agent-skills and llms.txt manifests further support programmatic/AI-native access. missing for 10: no independent third-party API client review beyond MotherDuck's own docs/probes.

   • [probe] “PROBE openapi: HTTP 200 at https://motherduck.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Connect to MotherDuck using official drivers and APIs for various programming languages.”
   • [claimed-docs] “DuckDB SDKs: Python, Node.js, Go, Rust, R, Java”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”
   • [probe] “PROBE runtime (recorded 2026-09-06): MotherDuck publishes an agentskills.io-conformant discovery manifest at /.well-known/agent-skills/index…”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”

   proof ↗⚑ flag

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

   weight 2 · round to MotherDuck
   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

   MotherDuck~partialprobed6/10

   MotherDuck documents concrete least-privilege options for agent access: restricting an AI assistant/MCP client to read-only SQL access, SaaS Mode to limit local environment interaction, and role/account-scoped Shares for multi-tenant isolation, plus a probed OAuth-protected resource flow on the hosted remote MCP endpoint (401 + WWW-Authenticate Bearer) confirming a real scoped-auth mechanism. However, there is no documented ability to mint a distinct, narrowly-scoped API key/token per agent (e.g. table- or query-level permission grants beyond read/write toggle), so it's read-only-vs-read-write plus share-based isolation rather than fine-grained credential issuance. Missing for 10: granular per-resource API key scoping beyond binary read-only/read-write, first-class 'create scoped credential for agent X' workflow, independent verification of the read-only restriction in practice.

   • [claimed-docs] “To restrict your AI assistant to read-only access, see Restricting to read-only access”
   • [claimed-docs] “The remote MCP server exposes both read-only and read-write tools.”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “You can limit MotherDuck's ability to interact with your local environment using SaaS Mode”
   • [claimed-docs] “Sharing data with specific preset roles or accounts in your organization. This is popular with data application builders that need to isolat…”
   • [claimed-docs] “Secrets are scoped to your user account and are not shared with other users in your organization.”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Databricks
   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

   MotherDuck✓fullprobed8/10

   MotherDuck documents official SDKs across multiple languages (Python, Node.js, Go, Rust, R, Java) built on DuckDB, plus an official CLI, MCP servers (local and remote), and an OpenAPI spec confirmed by probes. This directly supports AI-native/agentic developers building against official interfaces, with runtime probes confirming keyless SDK, CLI, and MCP functionality. Missing for 10: independent third-party benchmarking or reviews of SDK completeness/quality beyond vendor docs.

   • [claimed-docs] “DuckDB SDKs: Python, Node.js, Go, Rust, R, Java”
   • [claimed-docs] “Connect to MotherDuck using official drivers and APIs for various programming languages.”
   • [probe] “PROBE openapi: HTTP 200 at https://motherduck.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://motherduck.com/docs/sql-reference/mcp/”
   • [probe] “official CLI documented at https://duckdb.org/docs/installation/”
   • [probe] “PROBE runtime (recorded 2026-09-06): the engine under MotherDuck ran FULLY keyless on a laptop — `duckdb -c` built a 1,000,000-row table and…”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   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

   MotherDuck—none0/10

   MotherDuck offers MCP servers, scheduled jobs, and data sharing, but nothing in the evidence describes a webhook subscription mechanism for event notifications. Missing for 10: any webhook endpoint registration, event-driven push notification system, or documentation of subscribable events.

   ⚑ flag

Agentic features

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

   weight 2 · round drawn
   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

   MotherDuck✓fullprobed8/10

   MotherDuck's 'Dives' feature and MCP integration let users generate charts, dashboards, and insights via natural language prompts ('build a Dive with a chart of top 10 products', 'add a filter for US region'), with conversational iteration and no SQL required, confirmed by both docs and a runtime probe showing a working MCP tool call returning real query results. Missing for 10: independent/community hands-on validation specifically of the Dives/insights UX (community evidence covers MCP and SQL editor features but not Dives directly), and no evidence of proactive/unprompted AI-generated suggestions (all examples are user-initiated prompts).

   • [claimed-docs] “Generate interactive, shareable dashboards from natural language prompts”
   • [claimed-docs] “Build a Dive with a chart of our top 10 products by sales volume. Use MotherDuck's brand colors”
   • [claimed-docs] “Add a filter for the US region only”
   • [claimed-docs] “you iterate conversationally ("add a filter for US region", "switch to a bar chart") and the Viewer updates in place.”
   • [claimed-docs] “The MotherDuck remote MCP Server lets you analyze your data using natural language and generate interactive visualizations, all without writ…”
   • [claimed-docs] “you can refine it through conversation: "Add a filter for the US region only"”
   • [claimed-docs] “You iterate conversationally (_"add a filter for US region"_, _"switch to a bar chart"_) and the Viewer updates in place.”
   • [claimed-docs] “Change the chart to a stacked bar chart”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”

   proof ↗⚑ flag

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

   weight 2 · round to Databricks
   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

   MotherDuck~partialclaimed5/10

   MotherDuck documents scheduling Python jobs for ingest/transformation/operational tasks (docs-3), which supports background automations, but there is no evidence of a broader autonomous agent-scheduling framework, triggers, or orchestration for AI-driven background workflows beyond scheduled jobs. Missing for 10: evidence of autonomous agent-initiated scheduling/triggers, monitoring/retry of automated jobs, and independent confirmation of reliability of scheduled runs.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Read and write Guides — markdown documents that capture your org's metric definitions, join conventions, and domain context, so agents produ…”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”

   proof ↗⚑ flag

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

   weight 3 · round to Databricks
   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

   MotherDuck~partialclaimed7/10

   MotherDuck ships 'Dives,' a native feature that lets users build and iteratively refine dashboards via natural-language prompts ('add a filter for US region', 'switch to a bar chart') directly inside the product, and it also exposes a remote MCP server for natural-language SQL and visualization generation. This is real built-in agentic behavior, but the natural-language SQL/agent capability is delivered mainly via MCP, which requires an external AI client (e.g., Claude) rather than a self-contained chat assistant, and there's no independent/hands-on corroboration of the Dives assistant experience. Missing for 10: independent hands-on validation of Dives as a true in-product chat assistant, and clarity on whether any AI runs natively without an external MCP-connected LLM client.

   • [claimed-docs] “Generate interactive, shareable dashboards from natural language prompts”
   • [claimed-docs] “Build a Dive with a chart of our top 10 products by sales volume. Use MotherDuck's brand colors”
   • [claimed-docs] “Add a filter for the US region only”
   • [claimed-docs] “you iterate conversationally ("add a filter for US region", "switch to a bar chart") and the Viewer updates in place.”
   • [claimed-docs] “you can refine it through conversation: "Add a filter for the US region only"”
   • [claimed-docs] “You iterate conversationally (_"add a filter for US region"_, _"switch to a bar chart"_) and the Viewer updates in place.”
   • [claimed-docs] “The MotherDuck remote MCP Server lets you analyze your data using natural language and generate interactive visualizations, all without writ…”
   • [claimed-docs] “Analyze your data with natural language using the remote MCP Server”

   proof ↗⚑ flag

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

   weight 2 · round to MotherDuck
   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

   MotherDuck✓fullprobed8/10

   MotherDuck ships natural-language interaction via 'Dives' (NL-to-dashboard generation with conversational refinement like 'add a filter for US region') and both local and remote MCP servers that let AI agents run SQL from natural-language prompts without writing SQL themselves; runtime probes confirm the MCP server actually executes real analytical queries end-to-end. missing for 10: independent/community validation specifically of the natural-language accuracy (only vendor docs and technical probes, no hands-on user review of NL command quality).

   • [claimed-docs] “Generate interactive, shareable dashboards from natural language prompts”
   • [claimed-docs] “Analyze your data with natural language using the remote MCP Server”
   • [claimed-docs] “Build a Dive with a chart of our top 10 products by sales volume. Use MotherDuck's brand colors”
   • [claimed-docs] “you iterate conversationally ("add a filter for US region", "switch to a bar chart") and the Viewer updates in place.”
   • [claimed-docs] “The MotherDuck remote MCP Server lets you analyze your data using natural language and generate interactive visualizations, all without writ…”
   • [claimed-docs] “you can refine it through conversation: "Add a filter for the US region only"”
   • [claimed-docs] “You iterate conversationally (_"add a filter for US region"_, _"switch to a bar chart"_) and the Viewer updates in place.”
   • [claimed-docs] “Change the chart to a stacked bar chart”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”
   • [probe] “PROBE runtime (recorded 2026-09-06): MotherDuck publishes an agentskills.io-conformant discovery manifest at /.well-known/agent-skills/index…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Databricks
   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

   MotherDuck—none0/10

   The evidence shows an OpenAPI spec exists at /openapi.json (a machine-readable schema) and various driver/API docs, but there is no evidence of an actual interactive reference UI (e.g., Swagger-style 'try it' console) or runnable in-browser examples tied to that spec. missing for 10: an interactive API explorer page, runnable/live code examples, and any confirmation the OpenAPI spec is surfaced as a browsable interactive reference.

   • [probe] “PROBE openapi: HTTP 200 at https://motherduck.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Connect to MotherDuck using official drivers and APIs for various programming languages.”

   proof ↗⚑ flag

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

   weight 2 · round to MotherDuck
   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

   MotherDuck✓fullprobed9/10

   A live OpenAPI JSON spec is confirmed at https://motherduck.com/openapi.json (HTTP 200, contains 'openapi' key), directly satisfying the machine-readable API spec requirement; MotherDuck also publishes additional machine-readable discovery surfaces (llms.txt, agent-skills manifest, mcp.json). Missing for 10: independent third-party confirmation/discussion of the OpenAPI spec's completeness or usage in the community evidence.

   • [probe] “PROBE openapi: HTTP 200 at https://motherduck.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE runtime (recorded 2026-09-06): MotherDuck publishes an agentskills.io-conformant discovery manifest at /.well-known/agent-skills/index…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://motherduck.com/llms.txt # MotherDuck MotherDuck is a modern serverless data warehouse built on DuckDB. …”

   proof ↗⚑ flag

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

   weight 1 · round to MotherDuck
   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

   MotherDuck~partialprobed5/10

   MotherDuck supports local/in-memory DuckDB development (via CLI or local MCP server) that lets an agent run real analytical queries with zero MotherDuck account or production data touched, and offers read-only restriction and SaaS Mode to limit AI/agent access to local environment before syncing to cloud (docs-18, docs-31, docs-9, probe-rt-2). However, there is no dedicated 'sandbox' or database-branching feature that clones or isolates production data for testing—developers must manually use local files or in-memory DBs instead. Missing for 10: an explicit sandbox/branch/clone-of-production feature, first-party guidance framing this as a test-vs-prod workflow, and independent confirmation of safe isolation from prod data.

   • [claimed-docs] “Develop and iterate locally, then share and scale in the cloud when you need it.”
   • [claimed-docs] “You can limit MotherDuck's ability to interact with your local environment using SaaS Mode”
   • [claimed-docs] “To restrict your AI assistant to read-only access, see Restricting to read-only access”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [claimed-docs] “You can limit MotherDuck's ability to interact with your local environment using \`SaaS Mode\`”

   proof ↗⚑ flag

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

   weight 2 · round to Databricks
   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

   MotherDuck—none0/10

   While MotherDuck exposes an OpenAPI spec and various SDKs/drivers, the evidence pack contains no mention of API versioning scheme or a documented deprecation policy for its APIs, drivers, or MCP servers. Missing for 10: any docs describing API version numbers, backward-compatibility guarantees, or a deprecation/sunset policy.

   • [probe] “PROBE openapi: HTTP 200 at https://motherduck.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

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

   weight 2 · round to Databricks
   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

   MotherDuck~partialprobed6/10

   SQL is inherently set-based, and MotherDuck documents bulk data loading (from Postgres/MySQL, S3, DuckDB files) and read-write SQL execution via both local and remote MCP servers, which lets an AI agent issue bulk INSERT/UPDATE/COPY operations across many rows or tables in one call. However, there's no explicit documentation of an AI-native 'bulk operations across many items' primitive (e.g., batch MCP tool calls, bulk-apply-to-many-objects UX) — the evidence shows general bulk data movement/SQL rather than an agent-oriented batch-processing feature. Missing for 10: explicit agent-facing batch/bulk-operation tooling or examples, and independent confirmation of large-scale bulk SQL runs via MCP.

   • [claimed-docs] “Load your data from other databases and object storage”
   • [claimed-docs] “Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “Load a DuckDB database into MotherDuck: Upload a local DuckDB database file to MotherDuck cloud storage.”
   • [claimed-docs] “Learn to load a table from your PostgreSQL or MySQL database into MotherDuck.”
   • [claimed-docs] “You can safely store your Amazon S3 credentials in MotherDuck for convenience by creating a SECRET object”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”

   proof ↗⚑ flag

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

   weight 3 · round to Databricks
   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

   MotherDuck—none0/10

   Evidence shows scheduled Python jobs (time-based cron-style automation) but no capability for defining rules that trigger actions automatically on data or system events (e.g., event-driven triggers, alerts, webhooks on conditions). This is a fair axis for a data platform, but no evidence supports event-driven rule automation.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Databricks
   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

   MotherDuck~partialclaimed4/10

   Docs mention running Python jobs 'on a schedule for ingest, transformation, and operational tasks' (motherduck-docs-3), indicating some support for recurring automation, but there is no detail on how scheduling is configured (cron syntax, UI, triggers) nor independent verification of this capability. Missing for 10: documented scheduling mechanism/UI, examples of workflow definitions, and independent or hands-on confirmation that recurring jobs actually run reliably.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”

   proof ↗⚑ flag

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

   weight 1 · round to Databricks
   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

   MotherDuck—none0/10

   MotherDuck documents scheduled Python jobs and AI-generated Dives, but nothing in the evidence describes versioning, reviewing, or rolling back these automations/schedules — no changelog, diff, approval, or rollback mechanism is mentioned anywhere in the docs or community evidence.

   ⚑ 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 MotherDuck
   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

   MotherDuck~partialclaimed6/10

   MotherDuck documents billing mechanics well—per-second billing, sized instances (Pulse–Giga), a free Lite tier, and a billing dashboard with SQL views to monitor consumption and identify savings—giving a platform engineer real levers to reason about cost drivers. However, the evidence pack never surfaces an actual price list or $/instance-hour rate card needed to project a concrete monthly bill before signing up. Missing for 10: published per-instance-size dollar rates, a documented cost-estimation worksheet/example calculation, and independent confirmation that the dashboard estimates match real invoices.

   • [claimed-docs] “Size each instance to its job, Pulse through Giga.”
   • [claimed-docs] “Size each instance to its job, Pulse through Giga. Backfill on a Mega instance, run dbt workloads on a Standard, let end users query a fleet…”
   • [claimed-docs] “Moving to MotherDuck, a billed by-the-second cloud offering is a no-brainer for us, considering the elegance and efficiency of a single node…”
   • [claimed-docs] “MotherDuck provides SQL views and a billing dashboard to help you understand your compute and storage consumption.”
   • [claimed-docs] “Pricing docs: "New users who sign up for MotherDuck and create an organization automatically get access to a 7-day Free Trial without enteri…”
   • [claimed-docs] “Billing docs, "Monitoring usage and costs": "MotherDuck provides SQL views and a billing dashboard to help you understand your compute and s…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   MotherDuck~partialclaimed5/10

   MotherDuck docs confirm auto-suspend behavior ('idle instances shut down automatically, zero idle cost') and a billing dashboard/SQL views for monitoring compute and storage consumption, addressing the 'idle compute burning money' half of the story. However there is no evidence of configurable budgets, spend alerts/caps, or resource monitors that can kill a runaway query in progress — missing for 10: budget/spend-limit enforcement, automatic query cancellation on runaway cost, alerting thresholds tied to actions.

   • [claimed-docs] “Billing docs, "Monitoring usage and costs": "MotherDuck provides SQL views and a billing dashboard to help you understand your compute and s…”
   • [claimed-docs] “MotherDuck provides SQL views and a billing dashboard to help you understand your compute and storage consumption.”

   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 MotherDuck
   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

   MotherDuck✓fullprobed9/10

   Docs explicitly confirm a 7-day free trial with no credit card, followed by a free Lite plan (no credit card, 10GB storage, free monthly compute), and billing/monitoring tools let analysts run real queries on real data without a sales call. Runtime probes further show real analytical queries executing without any account at all via local DuckDB/MCP. Missing for 10: independent third-party confirmation of the no-CC signup flow beyond vendor docs.

   • [claimed-docs] “Pricing docs: "New users who sign up for MotherDuck and create an organization automatically get access to a 7-day Free Trial without enteri…”
   • [claimed-docs] “Billing docs, "Monitoring usage and costs": "MotherDuck provides SQL views and a billing dashboard to help you understand your compute and s…”
   • [claimed-docs] “MotherDuck provides SQL views and a billing dashboard to help you understand your compute and storage consumption.”
   • [probe] “PROBE runtime (recorded 2026-09-06): the engine under MotherDuck ran FULLY keyless on a laptop — `duckdb -c` built a 1,000,000-row table and…”

   proof ↗⚑ flag

Bi

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

   weight 1 · round to Databricks
   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

   MotherDuck~partialclaimed4/10

   Docs claim Postgres wire-protocol compatibility ('Use any Postgres-compatible tool, no DuckDB install needed') which implies some BI tools could connect without custom glue, and DuckDB SDKs exist for several languages, but there is no explicit mention of JDBC/ODBC drivers or named, documented BI-tool integrations (e.g., Tableau, Power BI, Looker) in the evidence pack. Missing for 10: explicit JDBC/ODBC driver documentation, named/certified BI-tool integration guides, and any hands-on confirmation that dashboards connect without custom glue.

   • [claimed-docs] “Use any Postgres-compatible tool, no DuckDB install needed”
   • [claimed-docs] “DuckDB SDKs: Python, Node.js, Go, Rust, R, Java”

   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 MotherDuck
   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

   MotherDuck✓fullprobed8/10

   MotherDuck is built on DuckDB, which runs fully local/embedded (confirmed by runtime probe showing a keyless local DuckDB engine executing real analytical queries with zero accounts or config), and docs explicitly describe a 'develop and iterate locally, then share and scale in the cloud when you need it' workflow plus a free Lite plan/trial with no credit card for early dev use. This gives data engineers a genuine free/local dev loop before touching production compute. Missing for 10: no first-party 'emulator' or sandbox mode specific to MotherDuck's cloud extensions (e.g., DuckLake, MotherDuck-specific SQL features) that fully mirrors production compute locally, and no independent case study explicitly describing a local-dev-then-promote-to-prod workflow.

   • [claimed-docs] “Develop and iterate locally, then share and scale in the cloud when you need it.”
   • [probe] “PROBE runtime (recorded 2026-09-06): the engine under MotherDuck ran FULLY keyless on a laptop — `duckdb -c` built a 1,000,000-row table and…”
   • [claimed-docs] “Pricing docs: "New users who sign up for MotherDuck and create an organization automatically get access to a 7-day Free Trial without enteri…”
   • [claimed-docs] “Upload a local DuckDB database file to MotherDuck cloud storage.”

   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
   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

   MotherDuck✓fullclaimed8/10

   MotherDuck's docs explicitly document dbt integration via the dbt-duckdb adapter, noting the only change needed is the `path:` setting for MotherDuck, and evidence shows dbt workloads sized to specific instances (e.g. 'run dbt workloads on a Standard'), indicating dbt is a recognized first-class workflow. missing for 10: no independent/hands-on report of a real dbt run against MotherDuck, and no dedicated MotherDuck-branded dbt adapter (relies on community dbt-duckdb rather than a vendor-authored adapter).

   • [claimed-docs] “The only change needed for motherduck is the path: setting.”
   • [claimed-docs] “dbt-duckdb is the adapter which allows dbt to use DuckDB and MotherDuck.”
   • [claimed-docs] “The only change needed for motherduck is the `path:` setting.”
   • [claimed-docs] “Size each instance to its job, Pulse through Giga. Backfill on a Mega instance, run dbt workloads on a Standard, let end users query a fleet…”

   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 MotherDuck
   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

   MotherDuck~partialclaimed4/10

   MotherDuck documents role-based Shares that grant read access to users/roles and can restrict exposure to specific tables/views via include patterns, plus preset roles for tenant isolation — covering table-level RBAC for multi-tenant use. However, there is no evidence of column-level masking policies or row-level security filters, which the story explicitly requires. Missing for 10: column masking policies, row-level security/filtering, unified role hierarchy spanning column+row+table grants.

   • [claimed-docs] “Grant read access to users or roles for multi-tenant applications and collaboration.”
   • [claimed-docs] “Limit which tables and views a Share exposes with an include pattern.”
   • [claimed-docs] “Sharing data with specific preset roles or accounts in your organization. This is popular with data application builders that need to isolat…”
   • [claimed-docs] “You can securely share data in MotherDuck.”

   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
   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

   MotherDuck—none0/10

   Evidence shows billing/usage dashboards (docs-44) and secret scoping/sharing permissions (docs-43, docs-47) but nothing describing query-level audit logs tied to user identity or column-level data lineage tracking. missing for 10: audit log documentation (who ran what query, when), column-level lineage tracking or metadata catalog, any independent verification of these governance features.

   • [claimed-docs] “MotherDuck provides SQL views and a billing dashboard to help you understand your compute and storage consumption.”
   • [claimed-docs] “Secrets are scoped to your user account and are not shared with other users in your organization.”
   • [claimed-docs] “Sharing data with specific preset roles or accounts in your organization. This is popular with data application builders that need to isolat…”

   proof ↗⚑ flag

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

   weight 1 · round to Databricks
   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

   MotherDuck—none0/10

   No evidence pack entry references SOC 2, HIPAA, PCI, or any formal compliance/attestation program, trust center, or security review documentation; the pack covers connectivity, MCP, sharing, and billing but not compliance certifications. missing for 10: SOC 2 report/attestation, HIPAA compliance statement, PCI attestation, trust center or security whitepaper, audit/certification documentation.

   ⚑ 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
   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

   MotherDuck~partialclaimed5/10

   MotherDuck documents loading from other databases (Postgres/MySQL) and object storage (S3), plus dbt as an ETL/transformation integration point, all with setup docs — covering the 'databases' and 'ETL/ELT tools' parts of the story. However there is no evidence of a broad partner/connector catalog for SaaS apps (e.g., Salesforce, Stripe, HubSpot) or a marketplace of pre-built connectors comparable to dedicated ETL platforms. Missing for 10: documented SaaS-app connectors, a partner connector directory/marketplace, and coverage beyond Postgres/MySQL/S3/dbt.

   • [claimed-docs] “Load your data from other databases and object storage”
   • [claimed-docs] “Learn to load a table from your PostgreSQL or MySQL database into MotherDuck.”
   • [claimed-docs] “You can safely store your Amazon S3 credentials in MotherDuck for convenience by creating a SECRET object”
   • [claimed-docs] “dbt-duckdb is the adapter which allows dbt to use DuckDB and MotherDuck.”
   • [claimed-docs] “The only change needed for motherduck is the path: setting.”
   • [claimed-docs] “Load a DuckDB database into MotherDuck: Upload a local DuckDB database file to MotherDuck cloud storage.”

   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
   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

   MotherDuck~partialclaimed5/10

   MotherDuck's docs reference loading data from object storage and databases, and support S3 credential/secret management for cloud storage access, implying use of DuckDB's native read_csv/read_parquet/read_json functions against S3 paths. However, the evidence pack never shows an explicit single documented command example bulk-loading CSV, JSON, and Parquet uniformly from cloud storage. Missing for 10: explicit command syntax/example for each format (CSV, JSON, Parquet) from S3/GCS, and any independent hands-on confirmation of a single-command bulk load.

   • [claimed-docs] “Load your data from other databases and object storage”
   • [claimed-docs] “Secrets are scoped to your user account and are not shared with other users in your organization.”
   • [claimed-docs] “You can safely store your Amazon S3 credentials in MotherDuck for convenience by creating a SECRET object”
   • [claimed-docs] “Load a DuckDB database into MotherDuck: Upload a local DuckDB database file to MotherDuck cloud storage.”
   • [claimed-docs] “Learn to load a table from your PostgreSQL or MySQL database into MotherDuck.”

   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 to Databricks
   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

   MotherDuck~partialclaimed4/10

   MotherDuck documents scheduled Python jobs for ingest/transformation and connectors for loading data from other databases and object storage (S3, Postgres, MySQL) without managing your own infra, which reduces pipeline-ops burden. However, this is scheduled/batch-oriented rather than a managed continuous/event-driven ingestion service that automatically picks up new files or streaming events as they arrive — there's no CDC, file-watcher, or event-trigger ingestion documented. Missing for 10: evidence of true event-driven/streaming ingestion (e.g., auto-detecting new files in a bucket, Kafka/CDC connectors, or push-based triggers) rather than cron-style scheduled jobs.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Load your data from other databases and object storage”
   • [claimed-docs] “Learn to load a table from your PostgreSQL or MySQL database into MotherDuck.”
   • [claimed-docs] “You can safely store your Amazon S3 credentials in MotherDuck for convenience by creating a SECRET object”
   • [claimed-docs] “Spin up a fully managed lakehouse with MotherDuck handling both metadata and storage, or bring your own cloud object storage.”
   • [claimed-docs] “Use DuckLake to build a data lake on top of your own files”

   proof ↗⚑ flag

Notebooks

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

   weight 2 · round to Databricks
   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

   MotherDuck~partialcommunity4/10

   MotherDuck's UI supports SQL notebooks with inline results and AI-generated charts (Instant SQL, Dives with GROUP BY visualizations, conversational chart edits), and Python is supported as a first-class SDK/scheduled-job language, but there is no evidence of a single first-party notebook interface that mixes SQL and Python cells together with inline charts as the story describes. missing for 10: evidence of Python cells inline within the same notebook/workspace as SQL cells, evidence of mixed-language notebook execution rather than separate SQL editor vs Python SDK/job usage.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Generate interactive, shareable dashboards from natural language prompts”
   • [claimed-docs] “Build a Dive with a chart of our top 10 products by sales volume. Use MotherDuck's brand colors”
   • [claimed-docs] “you iterate conversationally ("add a filter for US region", "switch to a bar chart") and the Viewer updates in place.”
   • [community] “Praise for MotherDuck's CTE inspection feature in Instant SQL: "CTE inspection is amazing. I spend too much time doing that manually."”

   proof ↗⚑ flag

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

   weight 2 · round to MotherDuck
   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

   MotherDuck~partialprobed6/10

   MotherDuck exposes a broad API surface (SDKs in Python/Node/Go/Rust/R/Java, a documented OpenAPI spec, SQL access, and both local/remote MCP servers that can execute read/write SQL and even generate visualizations conversationally), giving AI-native users substantial parity with UI capabilities like Dives and querying. However, several UI-only surfaces (billing dashboard, org/user management console, Instant SQL editor features) have no documented API/MCP equivalent, and no evidence explicitly confirms full feature parity across the board. Missing for 10: explicit documentation or confirmation that admin/billing/org-management UI actions are also API-accessible, and independent verification of full parity beyond query/visualization workflows.

   • [claimed-docs] “Connect to MotherDuck using official drivers and APIs for various programming languages.”
   • [claimed-docs] “DuckDB SDKs: Python, Node.js, Go, Rust, R, Java”
   • [claimed-docs] “The MotherDuck remote MCP Server lets you analyze your data using natural language and generate interactive visualizations, all without writ…”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [probe] “PROBE openapi: HTTP 200 at https://motherduck.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official mcp-server-motherduck (pypi, via uvx) completed a FULL keyless stdio initialize handshake …”
   • [probe] “PROBE runtime (recorded 2026-09-06): a keyless JSON-RPC initialize POST to the hosted remote MCP server https://api.motherduck.com/mcp retur…”
   • [claimed-docs] “MotherDuck provides SQL views and a billing dashboard to help you understand your compute and storage consumption.”

   proof ↗⚑ flag

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

   weight 3 · round to Databricks
   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

   MotherDuck~partialprobed5/10

   MotherDuck is built on DuckDB and documents local-first workflows (upload/download DuckDB files, local CLI/SDKs in Python/Node/Go/Rust/R/Java), implying data can move between local open DuckDB files and the cloud service, but there is no explicit documentation of a bulk 'export all your data to open formats (Parquet/CSV) and migrate away' workflow or data-portability guarantee. missing for 10: an explicit export-all-data/backup feature or migration guide, independent confirmation that a full account's data can be extracted losslessly, and any statement addressing vendor lock-in/exit.

   • [claimed-docs] “Upload a local DuckDB database file to MotherDuck cloud storage.”
   • [claimed-docs] “Develop and iterate locally, then share and scale in the cloud when you need it.”
   • [claimed-docs] “DuckDB SDKs: Python, Node.js, Go, Rust, R, Java”
   • [claimed-docs] “Load your data from other databases and object storage”
   • [probe] “PROBE runtime (recorded 2026-09-06): the engine under MotherDuck ran FULLY keyless on a laptop — `duckdb -c` built a 1,000,000-row table and…”

   proof ↗⚑ flag

3. ai-native userSelf-host the core product

   weight 3 · round drawn
   Databricks—none0/10

   Databricks is offered exclusively as a managed cloud service (AWS/Azure/GCP workspaces, pay-as-you-go billing) with no documented option to self-host the core platform on your own infrastructure; the closest analog (Free Edition) is still a hosted SaaS trial, not a self-hostable deployment. Community evidence even references how self-hosting Spark used to be painful specifically because Databricks replaced that with a hosted service, reinforcing that the core product is not self-hostable.

   • [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] “Databricks Free Edition is a no-cost version of Databricks designed for students, educators, hobbyists, and anyone interested in learning or…”
   • [community] “They had an excellent Spark-as-a-Service product, at a time when you'd have better luck finding a leprechaun than a reliable self-hosted Spa…”

   proof ↗⚑ flag

   MotherDuck—none0/10

   MotherDuck is explicitly a managed serverless cloud data warehouse; while DuckDB itself is open-source and can run locally, the core MotherDuck service (multi-tenant cloud engine, billing, sharing, dives, remote MCP) is not offered as a self-hosted deployment. Community discussion explicitly surfaces confusion about whether MotherDuck's editor/UI features are available on-prem, with no confirming answer that self-hosting is possible.

   • [community] “User confusion about product scope: "Will this be available in duckdb -ui? Is mother duck editor features available on-prem? My understandin…”
   • [claimed-docs] “Develop and iterate locally, then share and scale in the cloud when you need it.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://motherduck.com/llms.txt # MotherDuck MotherDuck is a modern serverless data warehouse built on DuckDB. …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   MotherDuck—none0/10

   No evidence pack material addresses data region/residency selection, geographic data center choice, or compliance certifications tied to storage location; the pack covers connectivity, sharing, MCP, and billing but nothing about where data physically resides. missing for 10: region selection options, data residency documentation, compliance/geo controls, any mention of storage location choice.

   ⚑ flag

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

   weight 3 · round drawn
   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

   MotherDuck—none0/10

   The evidence pack contains no statement about whether MotherDuck uses customer data to train AI models, nor any opt-out/data-training policy control; this is a fair question given MotherDuck's AI features (Dives, natural language MCP querying) but no documentation addresses it.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   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

   MotherDuck—none0/10

   The evidence pack covers authentication, sharing, secrets scoping, and MCP access controls but contains no documentation of data retention periods, deletion APIs, or purge/right-to-be-forgotten mechanisms for a MotherDuck-hosted database. As a cloud data warehouse, retention/deletion controls are a fair and expected axis, but no citation here shows explicit user-facing retention or deletion controls beyond generic DROP TABLE-type SQL implied by being a database.

   ⚑ flag

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

   weight 2 · round drawn
   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

   MotherDuck—none0/10

   The evidence pack covers SaaS Mode (limiting local environment interaction), secret scoping, and billing/usage dashboards, but none of it addresses telemetry or product usage tracking opt-out specifically — these are different concerns (environment access control and cost monitoring, not telemetry collection).

   ⚑ 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
   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

   MotherDuck~partialclaimed4/10

   MotherDuck documents "Guides" — markdown documents capturing metric definitions, join conventions, and domain context so AI agents produce consistent SQL without repetitive prompting — which is a lightweight step toward a governed semantic layer for AI consumers via MCP. However, this is informal markdown context rather than a structured semantic model with declared metrics/dimensions objects enforced across all query paths (SQL, BI tools, dashboards), and there's no evidence of validation, versioning, or joins-as-schema enforcement outside the AI/MCP context. Missing for 10: a structured metric/dimension definition schema (not just markdown guides), enforcement of consistency across non-AI query paths (BI/dashboard tools), and independent verification that guides actually produce consistent results across different AI tools.

   • [claimed-docs] “Read and write Guides — markdown documents that capture your org's metric definitions, join conventions, and domain context, so agents produ…”

   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
   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

   MotherDuck—none0/10

   MotherDuck's docs describe secure data *sharing* (grants, roles, presets, share links like md:_share/hacker_news/...) for collaboration within or across an organization, but there is no evidence of a curated marketplace of third-party datasets from external providers that an analyst could browse and attach for enrichment.

   • [claimed-docs] “Grant read access to users or roles for multi-tenant applications and collaboration.”
   • [claimed-docs] “Limit which tables and views a Share exposes with an include pattern.”
   • [claimed-docs] “You can securely share data in MotherDuck.”
   • [claimed-docs] “Sharing data with specific preset roles or accounts in your organization. This is popular with data application builders that need to isolat…”
   • [claimed-docs] “Attach this db 'md:_share/hacker_news/de11a0e3-9d68-48d2-ac44-40e07a1d496b' give me some analytics.”

   proof ↗⚑ flag

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

   weight 2 · round to Databricks
   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

   MotherDuck✓fullclaimed8/10

   MotherDuck's Sharing Data docs describe granting read access to specific users, roles, or accounts (including cross-org) via Shares without copying data, with the shared database attachable directly (e.g. `md:_share/...`), and include ways to restrict exposed tables/views — exactly a live-share model without export pipelines. This is corroborated by concrete attach syntax in the MCP getting-started doc showing a live shared dataset being queried directly. missing for 10: independent/hands-on confirmation of cross-organization (not just cross-user) sharing in production and any limits/latency of live share updates.

   • [claimed-docs] “You can securely share data in MotherDuck.”
   • [claimed-docs] “Grant read access to users or roles for multi-tenant applications and collaboration.”
   • [claimed-docs] “Limit which tables and views a Share exposes with an include pattern.”
   • [claimed-docs] “Sharing data with specific preset roles or accounts in your organization. This is popular with data application builders that need to isolat…”
   • [claimed-docs] “Attach this db 'md:_share/hacker_news/de11a0e3-9d68-48d2-ac44-40e07a1d496b' give me some analytics.”

   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 Databricks
   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

   MotherDuck~partialclaimed5/10

   MotherDuck's docs show S3 object-storage integration (secrets for S3 credentials) and DuckLake for building a lakehouse on top of 'your own files' or bring-your-own object storage, implying in-place querying of external storage rather than mandatory ingestion. However, the pack never explicitly names Iceberg or Delta table format support, or demonstrates querying Parquet/Iceberg/Delta files directly without first loading them into MotherDuck-managed storage — most 'loading data' docs (docs-6, docs-29, docs-42) describe explicit load/upload workflows instead. Missing for 10: explicit documentation or example of querying Iceberg/Delta tables in place, a worked example reading Parquet directly from S3 without a load step, and independent/hands-on confirmation of zero-copy querying against object storage.

   • [claimed-docs] “Spin up a fully managed lakehouse with MotherDuck handling both metadata and storage, or bring your own cloud object storage.”
   • [claimed-docs] “You can safely store your Amazon S3 credentials in MotherDuck for convenience by creating a SECRET object”
   • [claimed-docs] “Use DuckLake to build a data lake on top of your own files”
   • [claimed-docs] “Load your data from other databases and object storage”
   • [claimed-docs] “Secrets are scoped to your user account and are not shared with other users in your organization.”

   proof ↗⚑ flag

Performance

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

   weight 2 · round to Databricks
   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

   MotherDuck—none0/10

   The evidence pack mentions a query-performance doc and billing/usage dashboards (docs-44, docs-46) but none of it describes actual query profiling tools, EXPLAIN/ANALYZE output, or execution-plan visualization for diagnosing slow or expensive queries. Missing for 10: any documentation of an EXPLAIN/PROFILE command, a query plan visualizer, or per-query cost/latency breakdown tool for MotherDuck specifically.

   • [claimed-docs] “MotherDuck provides SQL views and a billing dashboard to help you understand your compute and storage consumption.”
   • [claimed-docs] “read scaling adds read-only Ducklings so concurrent users don't queue behind each other.”

   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 to Databricks
   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

   MotherDuck—none0/10

   The evidence pack covers connectivity, sharing, MCP, dbt integration, pricing, and dashboards, but contains no mention of time-travel querying, point-in-time recovery, or restoring dropped/corrupted tables from history — a capability common in some cloud warehouses but not documented here for MotherDuck.

   ⚑ 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 drawn
   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

   MotherDuck~partialprobed5/10

   MotherDuck runs on DuckDB and evidence confirms native CTE support (praised CTE inspection feature) and a real keyless aggregate GROUP BY analytical query executed without extensions, suggesting a native, non-bolt-on SQL engine. However, the pack contains no explicit documentation or examples of window functions, semi-structured JSON handling, array types, or rich date/time types. Missing for 10: explicit docs/examples of window functions, JSON/semi-structured querying, array types, and date/time type support.

   • [community] “Praise for MotherDuck's CTE inspection feature in Instant SQL: "CTE inspection is amazing. I spend too much time doing that manually."”
   • [probe] “PROBE runtime (recorded 2026-09-06): the engine under MotherDuck ran FULLY keyless on a laptop — `duckdb -c` built a 1,000,000-row table and…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://motherduck.com/llms.txt # MotherDuck MotherDuck is a modern serverless data warehouse built on DuckDB. …”
   • [claimed-docs] “Use DuckLake to build a data lake on top of your own files”

   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
   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

   MotherDuck~partialclaimed3/10

   MotherDuck's docs mention running scheduled Python jobs for ingest/transformation (docs-3) and dbt integration supporting incremental models (docs-7/19/32), which gives some incremental transformation capability, but there is no evidence of native streaming primitives, continuous queries, declarative pipeline objects, or task/stream constructs (à la Snowflake Streams & Tasks or Materialize) — MotherDuck is positioned as a serverless analytical warehouse, not a streaming engine. Missing for 10: native stream/CDC ingestion, continuous query execution, declarative pipeline DSL, task scheduling beyond generic Python cron jobs, and any independent evidence of these being used for continuous transformations.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “The only change needed for motherduck is the path: setting.”
   • [claimed-docs] “dbt-duckdb is the adapter which allows dbt to use DuckDB and MotherDuck.”
   • [claimed-docs] “The only change needed for motherduck is the `path:` setting.”

   proof ↗⚑ flag

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

   weight 2 · round to Databricks
   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

   MotherDuck—none0/10

   Evidence shows batch-style ingestion (file uploads, scheduled Python jobs, database/object-storage loads) but no documented streaming ingestion API with seconds-level queryability guarantees. No mention of Kafka/CDC connectors, streaming inserts, or latency SLAs for streamed data.

   ⚑ flag