BigQuery 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 to MotherDuck
   BigQuery~partialprobed6/10

   BigQuery offers the bq CLI and REST/client APIs for authentication, schema discovery, querying, and reading results (bigquery-docs-12/49/58, bigquery-docs-30, bigquery-docs-104), plus an official MCP Toolbox server enabling agent-driven DB access (bigquery-docs-98, bigquery-probe-1) and IAM-based governance (bigquery-docs-31/94/104). However, evidence doesn't show a unified, agent-oriented end-to-end workflow (auth+discover+query+read) documented as a single flow, and cost/quota surprises reported by users (bigquery-comm-1, bigquery-comm-2) suggest governance/guardrails for autonomous agents aren't fully proven in practice. missing for 10: a first-party end-to-end agent workflow doc combining auth, schema discovery, query, and result retrieval; independent hands-on validation of agent-driven governed querying without a dashboard.

   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [claimed-docs] “GoogleSQL is an ANSI-compliant Structured Query Language (SQL) that includes the following types of supported statements”
   • [claimed-docs] “This document provides a list of Identity and Access Management (IAM) predefined roles and permissions for BigQuery.”
   • [claimed-docs] “MCP Toolbox for Databases is an open source MCP server for databases.”
   • [probe] “official MCP server documented at https://github.com/googleapis/mcp-toolbox”
   • [community] “User ran a script on BigQuery for HTTP Archive data and was billed $14,000 with zero warning; complained about lack of customer support and …”
   • [community] “BQ hides query cost behind abstracted 'TBs scanned' or 'slots' mechanism; if GCP returned query cost directly in API/console it would be muc…”
   • [community] “BigQuery provides a dry run option to estimate bytes/costs before running a query, and shows bytes-to-be-scanned in small text before you hi…”

   proof ↗⚑ flag

   MotherDuck✓fullprobed8/10

   MotherDuck's docs describe a complete agent-driven SQL path: authenticate via saved credentials or SaaS Mode, discover schemas via the remote MCP server, execute read-only or read-write SQL (including the new query_rw tool), and get results back via CLI, Python/Node/Go/Rust SDKs, or a Postgres-compatible endpoint — all without needing the dashboard UI. This directly matches the ai-native/agent-analytics story of an end-to-end governed SQL workflow through CLI/API only. Missing for 10: independent/hands-on verification of the full authenticate→discover→query→read-back loop working end-to-end (only vendor docs are cited), and no explicit documentation of governance/permissions scoping specifically for agent credentials beyond general secret scoping.

   • [claimed-docs] “Connect to MotherDuck using official drivers and APIs for various programming languages.”
   • [claimed-docs] “Install the DuckDB CLI and connect directly to MotherDuck”
   • [claimed-docs] “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] “Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “Use any Postgres-compatible tool, no DuckDB install needed”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “We just released write access for the MotherDuck remote MCP server via the new query_rw tool. Your agents can now INSERT, UPDATE, DELETE, cr…”
   • [claimed-docs] “Postgres endpoint: BI tools, any Postgres client - Use any Postgres-compatible tool, no DuckDB install needed”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases - Explore database schemas, tables…”
   • [probe] “official MCP server documented at https://motherduck.com/docs/sql-reference/mcp/”

   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
   BigQuery✓fullclaimed8/10

   Google documents 'Gemini in BigQuery' features (conversational analytics, data canvas) that let users converse in natural language to find/join/query data, generate or suggest SQL/Python code, and explain existing SQL queries — directly matching the story of an in-product AI assistant working with schemas from natural language (bigquery-docs-5, bigquery-docs-39, bigquery-docs-66, bigquery-docs-71, bigquery-docs-72). Missing for 10: independent/hands-on user corroboration of this specific assistant feature (community evidence covers pricing/performance, not the AI assistant), and explicit documentation of 'fixing' broken SQL rather than just generating/suggesting/explaining.

   • [claimed-docs] “BigQuery의 Gemini를 사용하여 SQL 또는 Python에서 코드를 생성하거나 제안하고 기존 SQL 쿼리를 설명할 수 있습니다.”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “您还可以使用自然语言查询来开始数据分析。如需了解如何生成、补全和总结代码”
   • [claimed-docs] “Conversational analytics lets you have natural language conversations with your data.”
   • [claimed-docs] “Data insights offers an automated, intuitive way to uncover patterns and perform statistical analysis by using insightful queries that are g…”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed8/10

   MotherDuck ships a first-party AI assistant ("Dives") that turns natural-language prompts into SQL-backed charts/dashboards and lets users iterate conversationally ("add a filter for US region", "switch to a bar chart"), plus a remote MCP server that lets an agent write, execute, and modify SQL against the user's schemas without the user writing SQL themselves, backed by Guides to keep generated SQL accurate to org schema conventions. This directly matches the story of an in-product AI assistant writing/fixing/explaining SQL from natural language. missing for 10: independent/hands-on third-party validation that Dives/MCP reliably produces correct SQL (community evidence found relates to a different feature, Instant SQL, not to Dives or MCP SQL generation).

   • [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] “Read and write Guides — markdown documents that capture your org's metric definitions, join conventions, and domain context, so agents produ…”
   • [claimed-docs] “You iterate conversationally (_"add a filter for US region"_, _"switch to a bar chart"_) and the Viewer updates in place.”
   • [claimed-docs] “We just released write access for the MotherDuck remote MCP server via the new query_rw tool. Your agents can now INSERT, UPDATE, DELETE, cr…”
   • [claimed-docs] “The MotherDuck **remote** MCP Server lets you analyze your data using natural language and generate interactive visualizations, all without …”

   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 MotherDuck
   BigQuery~partialclaimed6/10

   BigQuery's Conversational analytics (Gemini in BigQuery) explicitly lets business users converse with data in natural language, find/join/query tables and visualize results, and Data insights auto-generates queries from table metadata — aligning with the 'no hallucinated joins' framing. IAM-based access control (docs-94/104) provides governance around who can query. However, all evidence is first-party vendor docs; there is no independent/hands-on validation that the NL answers are reliably semantically-grounded or that joins are never hallucinated, and no dedicated semantic-layer/metrics-governance framework is described tying NL answers to certified definitions. Missing for 10: independent corroboration of NL answer accuracy, explicit semantic-layer/metrics governance framework preventing hallucinated joins, and any hands-on report validating this specifically.

   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “Conversational analytics lets you have natural language conversations with your data.”
   • [claimed-docs] “Data insights offers an automated, intuitive way to uncover patterns and perform statistical analysis by using insightful queries that are g…”
   • [claimed-docs] “Conversational analytics now supports questions about market basket analysis.”
   • [claimed-docs] “roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines”
   • [claimed-docs] “This document provides a list of Identity and Access Management (IAM) predefined roles and permissions for BigQuery.”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed7/10

   MotherDuck ships natural-language interfaces (Dives, MCP server) letting business users ask questions conversationally and get SQL/charts back, and explicitly supports 'Guides' - markdown docs capturing org metric definitions and join conventions so agents produce accurate SQL without hallucinated joins - plus governance controls (read-only restriction, role-based sharing) to keep answers scoped and safe. Missing for 10: independent/hands-on evidence that Guides actually reduce hallucinated joins in practice, and no third-party benchmark of answer accuracy vs. hallucination.

   • [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 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”
   • [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] “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.”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to MotherDuck
   BigQuery—none0/10

   No evidence in the pack mentions llms.txt or any agent-oriented documentation format for BigQuery; the docs cited are standard human-facing Google Cloud documentation pages.

   ⚑ flag

   MotherDuck✓fullprobed9/10

   MotherDuck ships a live llms.txt (HTTP 200, confirmed by probe) and also an llms-full.txt referenced in docs, giving agents a direct machine-readable entry point to agent-oriented documentation; this is corroborated by an actual probe hit rather than just a claim. Missing for 10: independent third-party confirmation that an agent successfully used llms.txt to complete a task end-to-end.

   • [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] “Cloud Storage Integration: Query data directly from S3, GCS, Azure Blob Storage, and more”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   BigQuery✓fullclaimed8/10

   BigQuery provides the `bq` CLI tool, client SDKs (Python, Rust, etc.), REST/gRPC APIs, and Storage Write API for programmatic/headless ingestion and querying, all of which are scriptable in CI pipelines; Dataform also supports scheduled, version-controlled transformation workflows suitable for automation. missing for 10: no explicit first-party CI/CD integration guide (e.g., GitHub Actions/Cloud Build recipes) or independent hands-on report of running bq/CLI in a CI pipeline.

   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [claimed-docs] “you learn how to use `bq`, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query …”
   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “Collaborate with team members on workflow development through Git.”
   • [claimed-docs] “The Rust SDK for BigQuery is now in Preview.”
   • [claimed-docs] “For new projects, we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has …”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed8/10

   MotherDuck supports headless automation via CLI, SDKs (Python, Node.js, Go, Rust, R, Java), scheduled Python jobs (Flights) for ingest/transformation, and credential persistence for non-interactive sessions, all of which are usable in CI pipelines; dbt integration further supports automated pipelines. Missing for 10: no explicit CI platform examples (e.g., GitHub Actions, GitLab CI templates) or independent hands-on confirmation of headless CI usage.

   • [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] “DuckDB SDKs: Python, Node.js, Go, Rust, R, Java”
   • [claimed-docs] “Flights handle the infrastructure: Python runtime, scheduling, secrets, logging, and versioning.”
   • [claimed-docs] “Python jobs built by your favorite agent and deployed in MotherDuck. Ingest, enrich, and transform data without expensive ETL.”
   • [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.”

   proof ↗⚑ flag

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

   weight 3 · round to MotherDuck
   BigQuery✓fullprobed6/10

   Google publishes an official MCP server (MCP Toolbox for Databases) under the googleapis org that supports connecting agents to BigQuery, satisfying the axis for a data platform product. Missing for 10: detailed first-party docs on the BigQuery docs site describing setup/capabilities, and independent/hands-on corroboration of the MCP server working with BigQuery.

   • [probe] “official MCP server documented at https://github.com/googleapis/mcp-toolbox”

   proof ↗⚑ flag

   MotherDuck✓fullprobed9/10

   MotherDuck documents both a remote MCP server and a local MCP server (mcp-server-motherduck) that let agents run read/write SQL, explore schemas, and use natural-language analytics, with explicit tool details (query_rw), read-only restriction options, and a public GitHub repo for the local server implementation. This is well-documented first-party evidence of an official MCP server for agent connection; missing for 10: independent/hands-on third-party verification of the MCP server's reliability beyond vendor docs.

   • [claimed-docs] “Analyze your data with natural language using the remote MCP Server”
   • [claimed-docs] “Execute read-only and read-write SQL against your databases”
   • [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”
   • [claimed-docs] “We just released write access for the MotherDuck remote MCP server via the new query_rw tool. Your agents can now INSERT, UPDATE, DELETE, cr…”
   • [claimed-docs] “We just released **write access for the MotherDuck remote MCP server** via the new `query_rw` tool. Your agents can now INSERT, UPDATE, DELE…”
   • [probe] “official MCP server documented at https://motherduck.com/docs/sql-reference/mcp/”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to BigQuery
   BigQuery✓fullprobed8/10

   BigQuery ships an official Python-based CLI tool ('bq') well documented for creating datasets, loading data, and querying tables, confirmed across multiple docs and a dedicated probe entry. Missing for 10: no independent/hands-on community corroboration specifically of the CLI's agentic/scripting fit for AI-native workflows, and no explicit mention of CLI support for AI-specific features (e.g., piping to LLM agents).

   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [claimed-docs] “you learn how to use `bq`, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query …”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”

   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

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

   weight 3 · round drawn
   BigQuery✓fullprobed8/10

   BigQuery exposes a well-documented public API surface: the Storage Write API (gRPC/REST) for streaming ingestion, GoogleSQL/DML for queries, a Python-based bq CLI, ODBC/JDBC drivers, and an open-source MCP Toolbox server for programmatic/agent access to databases including BigQuery. This gives AI-native users multiple first-party, documented ways to drive BigQuery programmatically beyond the console UI. missing for 10: independent/hands-on developer confirmation that the API is easy to automate for agentic workflows specifically, and clearer agent-oriented API examples beyond general docs.

   • [claimed-docs] “The Storage Write API (gRPC) has lower pricing and more robust features, including exactly-once delivery semantics.”
   • [claimed-docs] “we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has lower pricing and …”
   • [claimed-docs] “For new projects, we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has …”
   • [claimed-docs] “Puedes usar la API de BigQuery Storage Write (gRPC) para transmitir datos a BigQuery.”
   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery”
   • [claimed-docs] “MCP Toolbox for Databases is an open source MCP server for databases.”
   • [probe] “official MCP server documented at https://github.com/googleapis/mcp-toolbox”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”

   proof ↗⚑ flag

   MotherDuck✓fullprobed8/10

   MotherDuck exposes a documented public API surface via SDKs for multiple languages, a Postgres-compatible endpoint, a Wasm client, and a confirmed OpenAPI spec (probe-3), plus a remote/local MCP server that lets AI agents execute read/write SQL, explore schemas, and even write via the new query_rw tool. Missing for 10: independent third-party corroboration of API stability/versioning, and explicit rate-limit or auth-scheme documentation beyond secrets management.

   • [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] “Postgres endpoint: BI tools, any Postgres client - Use any Postgres-compatible tool, no DuckDB install needed”
   • [probe] “PROBE openapi: HTTP 200 at https://motherduck.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “We just released write access for the MotherDuck remote MCP server via the new query_rw tool. Your agents can now INSERT, UPDATE, DELETE, cr…”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases - Explore database schemas, tables…”
   • [probe] “official MCP server documented at https://motherduck.com/docs/sql-reference/mcp/”

   proof ↗⚑ flag

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

   weight 2 · round to MotherDuck
   BigQuery~partialclaimed5/10

   BigQuery documents IAM predefined roles and permissions for datasets/tables/views/routines, which is the underlying mechanism for issuing least-privilege credentials to any caller, including an agent (bigquery-docs-31, bigquery-docs-65, bigquery-docs-94, bigquery-docs-104). However, there is no documentation specifically addressing scoped credential issuance for AI agents (e.g., service account impersonation, short-lived tokens, workload identity federation for agentic use, or API-key scoping tailored to agent workflows). Missing for 10: agent-specific credential provisioning guidance, service-account/token-scoping examples, and any agent-oriented security best practices beyond generic IAM role docs.

   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “BigQuery: Roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines.”
   • [claimed-docs] “roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines”
   • [claimed-docs] “This document provides a list of Identity and Access Management (IAM) predefined roles and permissions for BigQuery.”

   proof ↗⚑ flag

   MotherDuck~partialclaimed6/10

   MotherDuck docs describe several least-privilege mechanisms usable for agents: restricting the MCP server to read-only access vs. the newer read-write query_rw tool, 'SaaS Mode' to limit local environment interaction, and per-account-scoped secrets not shared across the org. This covers the core intent of scoped agent credentials but stops short of fine-grained per-resource or time-boxed token scoping. Missing for 10: granular table/database-level credential scoping specifically for agent tokens, token expiration/rotation controls, and independent verification that read-only restriction is enforced robustly.

   • [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] “You can limit MotherDuck's ability to interact with your local environment using SaaS Mode”
   • [claimed-docs] “You can limit MotherDuck's ability to interact with your local environment using \`SaaS Mode\`”
   • [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 using the [CREATE SECRET](/sql-r…”
   • [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

7. ai-native userBuild against official SDKs

   weight 2 · round to MotherDuck
   BigQuery~partialprobed7/10

   Evidence confirms official BigQuery SDKs/tooling exist (Rust SDK in Preview, Python-based bq CLI, ODBC/JDBC drivers, Storage Write API gRPC client), supporting programmatic/AI-native integration. However, the pack lacks explicit mention of core language SDKs (Python, Java, Node.js, Go, C#) commonly used by AI-native builders, and there's no independent/hands-on corroboration of SDK developer experience. Missing for 10: comprehensive list of mainstream language client libraries, and community validation of SDK usability for AI-agent workflows.

   • [claimed-docs] “The Rust SDK for BigQuery is now in Preview.”
   • [claimed-docs] “The Rust SDK for BigQuery is now in Preview”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [claimed-docs] “conectam seus aplicativos ao BigQuery, permitindo que você use os recursos do BigQuery com as ferramentas e a infraestrutura de sua preferên…”
   • [claimed-docs] “For new projects, we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has …”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”

   proof ↗⚑ flag

   MotherDuck✓fullprobed8/10

   MotherDuck documents official SDKs across Python, Node.js, Go, Rust, R, and Java, plus a Wasm client, Postgres-compatible endpoint, and official CLI/drivers, giving AI-native developers multiple sanctioned ways to build integrations. This is reinforced by MCP server SDK-like tooling for agentic access and dbt adapter integration. Missing for 10: independent third-party benchmarking or hands-on developer reports specifically validating SDK completeness/quality across all listed languages.

   • [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.”
   • [claimed-docs] “The MotherDuck Wasm Client library enables using MotherDuck through DuckDB Wasm in your own browser applications.”
   • [claimed-docs] “Postgres endpoint: BI tools, any Postgres client - Use any Postgres-compatible tool, no DuckDB install needed”
   • [probe] “official CLI documented at https://duckdb.org/docs/installation/”
   • [claimed-docs] “dbt-duckdb is the adapter which allows dbt to use DuckDB and MotherDuck.”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   BigQuery—none0/10

   The evidence pack shows Pub/Sub-based streaming ingestion and continuous queries, but no documented webhook subscription mechanism for BigQuery events (e.g., job completion, data changes) that an AI agent could subscribe to. This is a fair capability to ask of a data platform, but no evidence supports it.

   ⚑ flag

   MotherDuck—none0/10

   No evidence anywhere in the pack of MotherDuck supporting webhooks or event subscriptions; the product's agentic surface is MCP tools and scheduled Python jobs, not event-driven webhook subscriptions.

   ⚑ flag

Agentic features

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

   weight 2 · round drawn
   BigQuery✓fullclaimed8/10

   BigQuery ships Gemini-powered conversational analytics (natural language Q&A with data), automated Data insights that generate statistical patterns from table metadata, and code generation/explanation for SQL/Python, all directly inside the product UI (data canvas). Missing for 10: independent/hands-on validation of insight quality and no evidence of proactive unprompted suggestions beyond query-time interactions.

   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “BigQuery의 Gemini를 사용하여 SQL 또는 Python에서 코드를 생성하거나 제안하고 기존 SQL 쿼리를 설명할 수 있습니다.”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “Conversational analytics lets you have natural language conversations with your data.”
   • [claimed-docs] “Data insights offers an automated, intuitive way to uncover patterns and perform statistical analysis by using insightful queries that are g…”
   • [claimed-docs] “Les insights sur les données offrent un moyen automatisé et intuitif d'identifier des schémas et d'effectuer des analyses statistiques”
   • [claimed-docs] “Os insights de dados oferecem uma maneira automatizada e intuitiva de descobrir padrões e realizar análises estatísticas usando consultas út…”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed8/10

   MotherDuck ships Dives (natural-language generated, conversationally editable dashboards/charts/insights) and a remote MCP server for natural-language querying and visualization without SQL, both first-party documented features directly matching the story. There is some independent corroboration of the natural-language/AI features (HN reactions to Instant SQL) though not specifically for Dives; missing for 10: independent hands-on validation of Dives' quality/accuracy and broader third-party reviews of AI-insight generation.

   • [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 ask a question and save the answer as a Dive that stays current with your data.”
   • [claimed-docs] “Create rich data apps and interactive visualizations for internal insights or embedding in your application.”

   proof ↗⚑ flag

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

   weight 2 · round to MotherDuck
   BigQuery~partialclaimed6/10

   BigQuery supports several forms of unattended, scheduled/continuous automation — continuous queries that run SQL statements indefinitely on streaming data (bigquery-docs-11/54/100), scheduled load jobs and Pub/Sub streaming ingestion (bigquery-docs-41/42), and Dataform-managed scheduled transformation workflows (bigquery-docs-7) — which can serve as backend automations for AI-native pipelines. However, evidence is docs-only with no independent/hands-on corroboration, and none of it frames these as AI-agent-triggered or agent-orchestrated automations specifically. Missing for 10: evidence of AI-agent/LLM-triggered automation workflows, third-party/hands-on validation that these scheduling features run reliably unattended, and any agent-framework integration for autonomous triggering beyond generic data-pipeline scheduling.

   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “Continuous queries let you analyze incoming data in BigQuery in real time.”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “Pub/Sub can handle high throughput of data loads into BigQuery. It supports real-time data streaming, loading data as it's generated.”
   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed7/10

   MotherDuck's 'Flights' product explicitly lets users (or their AI agents) build Python jobs that run on a schedule with managed infrastructure for scheduling, secrets, logging, and versioning, directly enabling autonomous background automation for ingest/transform tasks; Dives also let saved AI-generated answers 'stay current with your data' automatically. Missing for 10: independent/hands-on validation of Flights' scheduling reliability and failure handling, and more detail on monitoring/alerting for these background jobs.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Flights handle the infrastructure: Python runtime, scheduling, secrets, logging, and versioning.”
   • [claimed-docs] “Python jobs built by your favorite agent and deployed in MotherDuck. Ingest, enrich, and transform data without expensive ETL.”
   • [claimed-docs] “you can ask a question and save the answer as a Dive that stays current with your data.”

   proof ↗⚑ flag

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

   weight 3 · round to BigQuery
   BigQuery✓fullclaimed7/10

   BigQuery ships 'Gemini in BigQuery' with conversational analytics (natural-language chat with data), a data canvas for exploration/transformation, and code generation/explanation for SQL/Python, letting users delegate tasks like finding/joining/querying tables and visualizing results to a built-in AI assistant (bigquery-docs-3,4,5,39,66,71,72,88,107). missing for 10: independent/hands-on user corroboration of the assistant's real-world reliability, and clearer scope of what tasks it can autonomously execute vs. just suggest.

   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “BigQuery의 Gemini를 사용하여 SQL 또는 Python에서 코드를 생성하거나 제안하고 기존 SQL 쿼리를 설명할 수 있습니다.”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “您还可以使用自然语言查询来开始数据分析。如需了解如何生成、补全和总结代码”
   • [claimed-docs] “Conversational analytics lets you have natural language conversations with your data.”
   • [claimed-docs] “Data insights offers an automated, intuitive way to uncover patterns and perform statistical analysis by using insightful queries that are g…”
   • [claimed-docs] “Les insights sur les données offrent un moyen automatisé et intuitif d'identifier des schémas et d'effectuer des analyses statistiques”
   • [claimed-docs] “Os insights de dados oferecem uma maneira automatizada e intuitiva de descobrir padrões e realizar análises estatísticas usando consultas út…”

   proof ↗⚑ flag

   MotherDuck~partialclaimed6/10

   MotherDuck's 'Dives' feature is a built-in AI assistant that generates dashboards/visualizations from natural-language prompts and lets users iterate conversationally ('add a filter for US region', 'switch to a bar chart'), which is a genuine in-product AI delegation capability. However, this built-in assistant is scoped to dashboarding/visualization tasks rather than general task delegation across the whole product, and most of the deeper 'AI assistant' capability (SQL analysis, write access) is delivered via external MCP servers connecting third-party agents (e.g. Claude) rather than a native in-product assistant. Missing for 10: evidence of a general-purpose in-product assistant beyond Dives, independent/hands-on validation of the Dives conversational experience, and broader agentic task coverage beyond charts/dashboards.

   • [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] “Change the chart to a stacked bar chart”
   • [claimed-docs] “you can ask a question and save the answer as a Dive that stays current with your data.”
   • [claimed-docs] “Create rich data apps and interactive visualizations for internal insights or embedding in your application.”

   proof ↗⚑ flag

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

   weight 2 · round to MotherDuck
   BigQuery✓fullclaimed7/10

   BigQuery's Gemini/Conversational Analytics and Data Canvas features let users query, join, explore, and visualize data using natural-language input, and generate/explain SQL or Python code from natural language, directly matching the story. Missing for 10: independent/hands-on user reports specifically validating the natural-language conversational analytics experience (community evidence found only covers pricing/performance, not NL usage), and clarity on how broadly this feature is available (GA vs preview).

   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “BigQuery의 Gemini를 사용하여 SQL 또는 Python에서 코드를 생성하거나 제안하고 기존 SQL 쿼리를 설명할 수 있습니다.”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “您还可以使用自然语言查询来开始数据分析。如需了解如何生成、补全和总结代码”
   • [claimed-docs] “Conversational analytics lets you have natural language conversations with your data.”
   • [claimed-docs] “Data insights offers an automated, intuitive way to uncover patterns and perform statistical analysis by using insightful queries that are g…”
   • [claimed-docs] “Les insights sur les données offrent un moyen automatisé et intuitif d'identifier des schémas et d'effectuer des analyses statistiques”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed8/10

   MotherDuck's Dives feature and MCP server let users analyze data and build/iterate visualizations via natural language ('add a filter for US region', 'switch to a bar chart') without writing SQL, and agents can execute both read and read-write SQL through natural language via MCP tools. Missing for 10: independent hands-on verification of natural-language accuracy/reliability and broader coverage beyond Dives/MCP chat interactions.

   • [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] “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] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “We just released write access for the MotherDuck remote MCP server via the new query_rw tool. Your agents can now INSERT, UPDATE, DELETE, cr…”
   • [claimed-docs] “We just released **write access for the MotherDuck remote MCP server** via the new `query_rw` tool. Your agents can now INSERT, UPDATE, DELE…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   BigQuery—none0/10

   No evidence in the pack mentions an interactive API reference, embedded code playground, or runnable examples within BigQuery's documentation; only static docs, CLI guides, notebooks, and release notes are cited. The axis is plausible for a cloud API product, but nothing supports this specific capability.

   ⚑ flag

   MotherDuck—none0/10

   The evidence shows a raw OpenAPI JSON file exists (motherduck-probe-3) but no interactive API reference UI, no 'try-it' console, and no runnable code examples embedded in docs are described anywhere in the docs pages; the extensive doc set covers SQL reference, MCP tools, and integrations but never an interactive API explorer.

   ⚑ flag

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

   weight 2 · round to MotherDuck
   BigQuery—none0/10

   The evidence pack covers BigQuery's SQL, CLI, notebooks, sharing, and pricing features but contains no mention of a downloadable OpenAPI/Swagger spec, Google API Discovery Document, or any machine-readable API schema for BigQuery's REST/gRPC APIs. Since BigQuery does expose REST APIs, this axis is applicable, but with no supporting citation the story is unmet.

   ⚑ flag

   MotherDuck✓fullprobed8/10

   A probe confirms a live OpenAPI spec at https://motherduck.com/openapi.json returning HTTP 200 with an 'openapi' key, directly satisfying the machine-readable API spec requirement, and this complements documented multi-language SDK/driver APIs. Missing for 10: no first-party docs page explicitly linking/describing the OpenAPI spec's coverage or versioning, and no independent/community corroboration of its completeness.

   • [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”

   proof ↗⚑ flag

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

   weight 1 · round to BigQuery
   BigQuery~partialclaimed5/10

   BigQuery Sandbox is a well-documented feature letting users explore BigQuery without a billing account/credit card and without touching a paid production project, which functions as a low-stakes test environment (bigquery-docs-6, -48, -62, -73). However, it is explicitly described as offering only 'limited BigQuery capabilities,' not a full mirror of production data/schema, and there is no evidence tying this to AI-agent-driven testing workflows specifically. Missing for 10: explicit AI-native/agentic testing workflow support, evidence of full-fidelity sandbox mirroring production schemas/data, and any hands-on corroboration of sandbox use for agent testing.

   • [claimed-docs] “Mit der BigQuery-Sandbox können Sie BigQuery nutzen, ohne eine Kreditkarte anzugeben oder ein Rechnungskonto für Ihr Projekt zu erstellen.”
   • [claimed-docs] “The BigQuery sandbox lets you explore limited BigQuery capabilities at no cost to confirm whether BigQuery fits your needs.”
   • [claimed-docs] “The BigQuery sandbox lets you experience BigQuery without providing a credit card or creating a billing account for your project.”
   • [claimed-docs] “BigQuery 샌드박스를 사용하면 신용카드 정보를 제공하거나 프로젝트에 결제 계정을 만들지 않고도 BigQuery를 경험할 수 있습니다.”

   proof ↗⚑ flag

   MotherDuck~partialclaimed4/10

   MotherDuck's docs describe local development ("develop and iterate locally, then share and scale in the cloud"), isolated per-user/agent compute via hypertenancy, and read-only restriction options for MCP/shares — all of which let a user work without directly touching production data. However there's no explicit sandbox/staging database, cloning, or test-environment feature described, so the story is only indirectly supported. Missing for 10: a dedicated sandbox/branching feature, explicit guidance on testing against non-production copies, and independent confirmation this isolation prevents production data exposure.

   • [claimed-docs] “Develop and iterate locally, then share and scale in the cloud when you need it.”
   • [claimed-docs] “Its hypertenancy architecture gives every user or AI agent an isolated compute instance, so you get sub-second analytics with no infrastruct…”
   • [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”
   • [claimed-docs] “The remote MCP server exposes both read-only and read-write tools.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   BigQuery—none0/10

   The evidence pack covers many BigQuery features (Storage Write API, notebooks, pricing, CLI, IAM, etc.) but contains no documentation of API versioning schemes or a formal deprecation policy for BigQuery's APIs. Google Cloud does have general deprecation policies, but none are cited here.

   ⚑ flag

   MotherDuck—none0/10

   No evidence of API versioning scheme or documented deprecation policy for MotherDuck's SQL, MCP, or driver APIs; docs cover connectivity, sharing, MCP tools, and pricing but never mention version numbers, backward-compatibility guarantees, or deprecation timelines. missing for 10: versioned API/endpoint scheme, published deprecation policy, changelog or migration guides for breaking changes.

   ⚑ flag

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

   weight 2 · round to BigQuery
   BigQuery✓fullcommunity7/10

   BigQuery natively supports bulk operations via DML for batch insert/update/delete, batch load jobs with scheduling, and the high-throughput Storage Write API for large-scale bulk ingestion, plus the bq CLI for scripting these operations across many items/tables. Community evidence corroborates BigQuery's ability to process petabyte-scale data efficiently. Missing for 10: explicit evidence of AI-agent-driven orchestration of bulk operations (e.g., an agent issuing many bulk actions via MCP/API in one flow) and independent benchmarks specifically on DML/bulk-write scale rather than just query scale.

   • [claimed-docs] “Data Manipulation Language (DML) statements enable you to update, insert, and delete data from your BigQuery tables.”
   • [claimed-docs] “we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has lower pricing and …”
   • [claimed-docs] “For new projects, we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has …”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [community] “I've worked with much larger datasets on BQ (petabyte scale) and managed to not spend more than $1000 in an hour; BQ tells you how much data…”
   • [claimed-docs] “the distributed and scalable analysis engine of BigQuery allows querying terabytes in seconds and petabytes in minutes”

   proof ↗⚑ flag

   MotherDuck~partialclaimed6/10

   MotherDuck supports SQL-based bulk operations (batch SQL execution, dbt transformations, Python 'Flights' jobs for scheduled ingest/transform, MCP write access for INSERT/UPDATE/DELETE at scale, and loading data from many sources), which can be leveraged by an AI agent to act on many items programmatically. However there is no explicit evidence of a dedicated bulk/batch API primitive (e.g., batch job submission across many records with progress tracking) tailored for AI-native multi-item operations beyond standard SQL/ETL patterns. missing for 10: dedicated bulk-operation API/tooling distinct from standard SQL, independent hands-on validation of large-scale bulk agent operations, and any documented batch-size limits or guarantees for AI-driven bulk edits.

   • [claimed-docs] “We just released write access for the MotherDuck remote MCP server via the new query_rw tool. Your agents can now INSERT, UPDATE, DELETE, cr…”
   • [claimed-docs] “We just released **write access for the MotherDuck remote MCP server** via the new `query_rw` tool. Your agents can now INSERT, UPDATE, DELE…”
   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Python jobs built by your favorite agent and deployed in MotherDuck. Ingest, enrich, and transform data without expensive ETL.”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases - Explore database schemas, tables…”
   • [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.”

   proof ↗⚑ flag

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

   weight 3 · round to BigQuery
   BigQuery~partialclaimed4/10

   BigQuery's continuous queries feature lets you run SQL statements continuously against incoming data for real-time analysis, which is the closest capability to event-driven automation, and Dataform/scheduled queries allow time-based (not event-based) automation of transformations. However, there's no documented rule-engine construct (e.g., 'when X happens, do Y') or explicit action-triggering integrations (webhooks, notifications, external actions) tied to specific event conditions. Missing for 10: explicit conditional rule definition syntax, documented action triggers (e.g., calling external APIs/functions on events), and independent evidence of this being used for automation workflows.

   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “Continuous queries let you analyze incoming data in BigQuery in real time.”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”

   proof ↗⚑ flag

   MotherDuck—none0/10

   Evidence shows only schedule-based automation (Python 'Flights' jobs on a schedule) and MCP-driven conversational actions, but no rule/event-trigger system (e.g., triggers on data changes, webhooks, alerts) that fires actions automatically on events as described in the story.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Flights handle the infrastructure: Python runtime, scheduling, secrets, logging, and versioning.”
   • [claimed-docs] “Python jobs built by your favorite agent and deployed in MotherDuck. Ingest, enrich, and transform data without expensive ETL.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to BigQuery
   BigQuery✓fullclaimed7/10

   Docs show native scheduling of load jobs and batch transfers (docs-41) plus Dataform, a first-party service for scheduling complex recurring data transformation workflows with dependency visualization and Git-based collaboration (docs-7, docs-40, docs-50, docs-61), directly covering recurring job/workflow automation for AI-native/data pipeline use cases. Missing for 10: no mention of the native 'Scheduled Queries' UI feature by name, no independent/hands-on evidence corroborating scheduling reliability at scale.

   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “View a visualization of the dependency tree of your workflow.”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”
   • [claimed-docs] “Collaborate with team members on workflow development through Git.”

   proof ↗⚑ flag

   MotherDuck~partialclaimed6/10

   MotherDuck's 'Flights' product explicitly supports running Python jobs on a schedule with built-in scheduling, secrets, logging, and versioning, and is marketed as buildable by an AI agent — directly matching the automation-depth story. However, evidence is entirely first-party marketing/docs with no independent or hands-on corroboration, and no detail on complex multi-step workflow orchestration (e.g., dependencies between jobs, retries, DAGs) beyond simple recurring Python jobs. missing for 10: independent/hands-on validation of scheduling reliability, documentation of multi-step workflow/DAG orchestration beyond single scheduled jobs.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Flights handle the infrastructure: Python runtime, scheduling, secrets, logging, and versioning.”
   • [claimed-docs] “Python jobs built by your favorite agent and deployed in MotherDuck. Ingest, enrich, and transform data without expensive ETL.”

   proof ↗⚑ flag

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

   weight 1 · round to BigQuery
   BigQuery~partialclaimed5/10

   Dataform (integrated with BigQuery) supports version control and team collaboration on workflows via Git, and BigQuery now lets you store/manage pipelines in Git folders, which covers versioning and review of automation workflows. However, there is no explicit documentation of a rollback mechanism for automations/pipelines beyond implicit Git revert, and this capability is scoped to Dataform/pipelines rather than all BigQuery automation types (e.g., scheduled queries, continuous queries). Missing for 10: explicit rollback/undo feature for automation runs, review workflow specifics (e.g., PR-based approval), and coverage across all automation types beyond Dataform pipelines.

   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “Collaborate with team members on workflow development through Git.”
   • [claimed-docs] “You can now create, store, and manage pipelines in Git folders.”
   • [claimed-docs] “View a visualization of the dependency tree of your workflow.”

   proof ↗⚑ flag

   MotherDuck—none0/10

   No evidence of version control, review workflows, diffing, or rollback mechanisms for automations (Flights, Dives, scheduled jobs). Docs mention Flights handle 'versioning' as infrastructure detail but give no user-facing capability to review, diff, or roll back automation versions.

   ⚑ 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
   BigQuery!disputedcontradicted5/10

   BigQuery's docs clearly lay out the pricing model (on-demand per TiB with free tier, slot-based reserved pricing, custom quotas) and community reports confirm dry-run/bytes-scanned previews help estimate costs before running queries [bigquery-docs-19,28,46,89,76,bigquery-comm-3,bigquery-comm-4,bigquery-comm-10]. However, a hands-on account describes an unexpected $14,000 bill with 'zero warning' and criticizes that BQ 'hides query cost behind abstracted TBs scanned or slots mechanism,' directly contradicting the claim that pricing is transparent/estimable in practice [bigquery-comm-1,bigquery-comm-2]. Missing for 10: clear vendor guidance/tooling for estimating recurring/monthly costs (vs. single-query dry runs), and resolution of the community-reported surprise-billing incident.

   • [claimed-docs] “On-demand pricing (per TiB). With this pricing model, you are charged for the number of bytes processed by each query. The first 1 TiB of qu…”
   • [claimed-docs] “BigQuery offers a choice of two compute pricing models for running queries”
   • [claimed-docs] “You can also reserve compute capacity ahead of time in the form of slots, which represent virtual CPUs.”
   • [claimed-docs] “you are charged for compute capacity used to run queries, measured in slots (virtual CPUs) over time”
   • [claimed-docs] “you can manage costs by requesting a custom quota that specifies a limit on the amount of data processed per day”
   • [community] “User ran a script on BigQuery for HTTP Archive data and was billed $14,000 with zero warning; complained about lack of customer support and …”
   • [community] “BQ hides query cost behind abstracted 'TBs scanned' or 'slots' mechanism; if GCP returned query cost directly in API/console it would be muc…”
   • [community] “BigQuery provides a dry run option to estimate bytes/costs before running a query, and shows bytes-to-be-scanned in small text before you hi…”
   • [community] “I've worked with much larger datasets on BQ (petabyte scale) and managed to not spend more than $1000 in an hour; BQ tells you how much data…”
   • [community] “BigQuery has on-demand pricing metered by data read, plus reserved slot pricing metered by time; reserved slots offer a considerable discoun…”

   proof ↗⚑ flag

   MotherDuck~partialclaimed6/10

   MotherDuck's docs describe a free Lite tier, per-second/instance-based billing (Pulse through Giga sizing), and a billing dashboard with SQL views to monitor compute/storage consumption and identify cost-saving opportunities, giving a platform engineer real levers to reason about spend. However, the evidence pack lacks an explicit rate card or worked example (e.g., $/second per instance size) that would let someone precisely forecast a monthly bill before committing. missing for 10: concrete price-per-instance-size figures, a worked cost-estimation example, and independent verification that the dashboard/estimates match actual bills.

   • [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] “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.”

   proof ↗⚑ flag

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

   weight 2 · round to MotherDuck
   BigQuery!disputedcontradicted4/10

   BigQuery documents custom quotas that cap daily bytes processed and dry-run cost previews to curb runaway spend (bigquery-docs-63, bigquery-docs-76, bigquery-comm-3, bigquery-comm-4), but there is no evidence of Snowflake/Redshift-style 'resource monitors' or true auto-suspend for idle compute, and a concrete community report describes a script that ran unattended and racked up a surprise $14,000 bill with zero warning and no recourse to reverse it, showing the cost-guard mechanisms did not actually stop the runaway job (bigquery-comm-1, bigquery-comm-2). Missing for 10: documented automatic query-kill/resource-monitor feature, evidence of auto-suspend for idle compute, and a case showing quotas actually prevented a real overrun.

   • [claimed-docs] “複数の BigQuery プロジェクトとユーザーが存在している場合は、カスタム割り当てを要求することで費用を管理できます。この割り当てでは、1 日に処理されるデータ量の上限を指定します。”
   • [claimed-docs] “you can manage costs by requesting a custom quota that specifies a limit on the amount of data processed per day”
   • [community] “BigQuery provides a dry run option to estimate bytes/costs before running a query, and shows bytes-to-be-scanned in small text before you hi…”
   • [community] “I've worked with much larger datasets on BQ (petabyte scale) and managed to not spend more than $1000 in an hour; BQ tells you how much data…”
   • [community] “User ran a script on BigQuery for HTTP Archive data and was billed $14,000 with zero warning; complained about lack of customer support and …”
   • [community] “BQ hides query cost behind abstracted 'TBs scanned' or 'slots' mechanism; if GCP returned query cost directly in API/console it would be muc…”

   proof ↗⚑ flag

   MotherDuck~partialclaimed5/10

   MotherDuck docs confirm idle-instance auto-suspend ('idle instances shut down automatically, zero idle cost') and a billing dashboard with SQL views to monitor compute/storage usage, which covers part of the 'stop idle compute from burning money' story. However, there is no evidence of configurable budgets, spend-cap alerts, or resource-monitor policies that would abort a runaway query mid-execution — only usage visibility and automatic idle shutdown are documented. Missing for 10: budget/alert thresholds, hard spend caps, automatic termination of long-running/runaway queries, and any monitoring-triggered kill-switch.

   • [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 drawn
   BigQuery✓fullclaimed8/10

   BigQuery Sandbox explicitly lets users try BigQuery 'without providing a credit card or creating a billing account,' and the free tier (1 TiB queries + 10 GiB storage per month) is documented directly in pricing/marketing docs, satisfying the no-card, real-data evaluation story. Missing for 10: independent hands-on corroboration of the sandbox experience and clearer detail on sandbox feature limits (only quota/billing docs, no community confirmation of trial ease).

   • [claimed-docs] “Mit der BigQuery-Sandbox können Sie BigQuery nutzen, ohne eine Kreditkarte anzugeben oder ein Rechnungskonto für Ihr Projekt zu erstellen.”
   • [claimed-docs] “The BigQuery sandbox lets you explore limited BigQuery capabilities at no cost to confirm whether BigQuery fits your needs.”
   • [claimed-docs] “The BigQuery sandbox lets you experience BigQuery without providing a credit card or creating a billing account for your project.”
   • [claimed-docs] “BigQuery 샌드박스를 사용하면 신용카드 정보를 제공하거나 프로젝트에 결제 계정을 만들지 않고도 BigQuery를 경험할 수 있습니다.”
   • [claimed-docs] “Store 10 GiB of data and run up to 1 TiB of queries for free per month.”
   • [claimed-docs] “On-demand pricing (per TiB). With this pricing model, you are charged for the number of bytes processed by each query. The first 1 TiB of qu…”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed8/10

   Official pricing docs explicitly confirm a 7-day free trial with no credit card, followed by a free-forever Lite plan (10GB storage, free monthly compute) that supports real queries on real data, plus billing/usage dashboards to monitor costs. This directly matches the analyst story of evaluating without a credit card or sales call. Missing for 10: independent/hands-on confirmation of the free-tier signup flow (no community evidence corroborating ease of trial signup, only 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.”

   proof ↗⚑ flag

Bi

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

   weight 1 · round to BigQuery
   BigQuery✓fullclaimed7/10

   BigQuery documents official Simba JDBC/ODBC drivers explicitly built to 'connect your applications to BigQuery, letting you use BigQuery features with your preferred tooling and infrastructure,' directly addressing the analyst's need to plug dashboards in without custom glue. Missing for 10: explicit named BI-tool integration guides (e.g., Tableau/Looker/Power BI certified connectors) and independent/hands-on confirmation from analysts that dashboard connections work smoothly without extra glue.

   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery”
   • [claimed-docs] “connect your applications to BigQuery, letting you use BigQuery features with your preferred tooling and infrastructure”
   • [claimed-docs] “conectam seus aplicativos ao BigQuery, permitindo que você use os recursos do BigQuery com as ferramentas e a infraestrutura de sua preferên…”

   proof ↗⚑ flag

   MotherDuck~partialclaimed6/10

   MotherDuck documents a Postgres-compatible wire endpoint explicitly for BI tools/any Postgres client (no DuckDB install needed), plus SDKs and DuckDB CLI connectivity, which covers ODBC/JDBC-style BI-tool access without custom glue. However there is no explicit mention of standard JDBC/ODBC drivers or a list of documented BI-tool integrations (e.g. Tableau, PowerBI) beyond the generic Postgres-wire claim, and no independent/community confirmation of BI tool hookups working smoothly. missing for 10: explicit JDBC/ODBC driver documentation, named BI-tool integration guides, independent hands-on confirmation of dashboard connectivity.

   • [claimed-docs] “Use any Postgres-compatible tool, no DuckDB install needed”
   • [claimed-docs] “Postgres endpoint: BI tools, any Postgres client - Use any Postgres-compatible tool, no DuckDB install needed”
   • [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.”
   • [claimed-docs] “Install the DuckDB CLI and connect directly to MotherDuck”

   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
   BigQuery~partialclaimed6/10

   BigQuery Sandbox lets developers try BigQuery without a billing account or credit card, giving a genuine free dev loop for querying/testing before committing to production billing, and the free tier (10GiB storage, 1TiB queries/month) reinforces this. However, this is still Google's live cloud service (not a local engine or true emulator), and no evidence of an offline/local BigQuery emulator or CLI-based local dev environment is provided. Missing for 10: a documented local/offline emulator, evidence of sandbox limitations relative to production, and independent developer accounts confirming the sandbox workflow is sufficient for real transformation development.

   • [claimed-docs] “Mit der BigQuery-Sandbox können Sie BigQuery nutzen, ohne eine Kreditkarte anzugeben oder ein Rechnungskonto für Ihr Projekt zu erstellen.”
   • [claimed-docs] “The BigQuery sandbox lets you explore limited BigQuery capabilities at no cost to confirm whether BigQuery fits your needs.”
   • [claimed-docs] “The BigQuery sandbox lets you experience BigQuery without providing a credit card or creating a billing account for your project.”
   • [claimed-docs] “BigQuery 샌드박스를 사용하면 신용카드 정보를 제공하거나 프로젝트에 결제 계정을 만들지 않고도 BigQuery를 경험할 수 있습니다.”
   • [claimed-docs] “Store 10 GiB of data and run up to 1 TiB of queries for free per month.”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed8/10

   MotherDuck is built on DuckDB, which runs fully local/embedded, and docs explicitly promote 'Develop and iterate locally, then share and scale in the cloud when you need it,' plus a free Lite plan/7-day trial with no credit card, enabling a genuine free/local dev loop before touching production compute. dbt-duckdb lets engineers build/test transformations locally and swap only a path setting to point at MotherDuck when ready. missing for 10: independent hands-on validation of the local dev loop workflow (only one community bug report about duckdb -ui, not the core local/dev story) and clearer docs on parity/limits between local DuckDB dev and MotherDuck production behavior.

   • [claimed-docs] “Develop and iterate locally, then share and scale in the cloud when you need it.”
   • [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] “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] “Install the DuckDB CLI and connect directly to MotherDuck”

   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 to MotherDuck
   BigQuery—none0/10

   The evidence pack contains no vendor documentation from Google Cloud/BigQuery describing a dbt adapter or native dbt project support. The only dbt-related evidence is a passing community remark that BigQuery's new SQL pipe syntax is 'great for dbt macros' — this is a tangential community observation, not vendor docs or an adapter reference for dbt itself.

   • [community] “Review after a week of using BigQuery's new SQL pipe syntax: much more productive for data exploration/cleaning, unifies WHERE/HAVING/QUALIF…”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed8/10

   MotherDuck has dedicated vendor docs for dbt integration confirming dbt-duckdb adapter support, with MotherDuck-specific setup requiring only a `path:` config change, and mentions running dbt workloads sized to a 'Standard' instance. This is documented, first-party adapter support rather than a full native dbt project template. Missing for 10: independent/community corroboration of the dbt workflow in production and more depth beyond the single path-setting note.

   • [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 BigQuery
   BigQuery~partialclaimed4/10

   Docs confirm IAM predefined roles/permissions governing BigQuery resources such as datasets, tables, views, and routines, satisfying the 'roles' and table-level portion of the story. However, the evidence pack contains no mention of column-level security (policy tags), row-level access policies, or dynamic data masking policies that the story explicitly requires. missing for 10: column-level security/policy tags, row-level security policies, dynamic data masking, and any independent/hands-on confirmation of fine-grained masking in production.

   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “BigQuery: Roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines.”
   • [claimed-docs] “roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines”
   • [claimed-docs] “This document provides a list of Identity and Access Management (IAM) predefined roles and permissions for BigQuery.”

   proof ↗⚑ flag

   MotherDuck~partialclaimed3/10

   MotherDuck documents role-based Shares that can restrict which tables/views are exposed (include patterns, preset roles like Explorer) enabling multi-team access control at the table level, but there is no evidence of column-level masking, row-level security policies, or dynamic data masking mechanisms. missing for 10: column-level masking policies, row-level security/filtering, and any granular attribute-based access control beyond table/view inclusion.

   • [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] “Sharing data with every preset role in your organization by granting access to the Explorer role. This is typical of small, highly collabora…”
   • [claimed-docs] “MotherDuck's sharing model is specifically optimized for the following scenarios: Sharing data with every preset role in your organization..…”

   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 BigQuery
   BigQuery~partialclaimed6/10

   BigQuery provides IAM roles/permissions docs (access control) and Dataplex data lineage which shows origin, destinations, and transformations of data, supporting column/table-level lineage. However, there is no explicit evidence of audit logs showing 'who ran what' (e.g., Cloud Audit Logs / Data Access logs for BigQuery jobs) in this pack, and lineage evidence is at the Dataplex platform level rather than confirmed column-level granularity within BigQuery itself. missing for 10: explicit BigQuery audit log documentation (who ran what query, job-level audit trail), confirmation of column-level (not just table-level) lineage granularity, and independent/hands-on corroboration of these governance features.

   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “BigQuery: Roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines.”
   • [claimed-docs] “roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines”
   • [claimed-docs] “This document provides a list of Identity and Access Management (IAM) predefined roles and permissions for BigQuery.”
   • [claimed-docs] “It shows you where your data comes from (the origin), where it travels (the destinations), and all the changes or transformations that happe…”
   • [claimed-docs] “Data lineage is a visual map that tracks the entire lifecycle of your data.”
   • [claimed-docs] “Die Datenherkunft ist eine visuelle Karte, die den gesamten Lebenszyklus Ihrer Daten nachvollzieht.”

   proof ↗⚑ flag

   MotherDuck—none0/10

   The evidence pack covers authentication, sharing, secrets, and billing/usage dashboards, but contains no mention of audit logs recording who ran which queries, nor any column-level data lineage tracking feature. This is a fair governance axis for a cloud data warehouse, but no supporting evidence exists.

   ⚑ flag

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

   weight 1 · round to BigQuery
   BigQuery✓fullclaimed8/10

   Google Cloud's compliance resource center explicitly lists BigQuery-covered attestations (ISO 9001/22301/50001, SOC 1/2/3, HIPAA support) with downloadable per-certification reports, directly addressing security review needs; IAM access control docs further support governance review readiness. Missing for 10: explicit PCI DSS attestation mention and independent third-party confirmation of audit report accessibility/process.

   • [claimed-docs] “Google Cloud compliance resource center lists BigQuery-covered attestations and certifications including ISO 9001:2015, ISO 22301:2019, ISO …”
   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “This document provides a list of Identity and Access Management (IAM) predefined roles and permissions for BigQuery.”

   proof ↗⚑ flag

   MotherDuck—none0/10

   No evidence pack item mentions SOC 2, HIPAA, PCI, or any compliance attestation/certification documentation; the pack covers connectivity, sharing, MCP, and pricing but nothing on compliance reports or trust center pages.

   ⚑ 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 drawn
   BigQuery~partialcommunity5/10

   BigQuery docs show multiple first-party ingestion paths (Storage Write API, Pub/Sub streaming, scheduled load jobs/transfers, near-real-time database replication, Dataform for ELT/transformation, ODBC/JDBC drivers) but there is no explicit documentation pack entry naming a broad catalog of SaaS-app connectors (e.g., Data Transfer Service for Ads/Analytics/Salesforce) with per-source setup guides, and a community report notes it was 'hard to get a Google CloudSQL DB into BigQuery' requiring a third-party tool. missing for 10: named SaaS-app connector list with setup docs, independent hands-on confirmation that database/ETL connectors work smoothly without third-party workarounds.

   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub. Pub/Sub can handle high throughput of data loads into BigQuery…”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub.”
   • [claimed-docs] “This method enables replicating data from databases to BigQuery in near real time.”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [community] “Last time I checked, it was still hard to get a Google CloudSQL DB into BigQuery, so it's surprising they did the Sheets integration first; …”

   proof ↗⚑ flag

   MotherDuck~partialclaimed5/10

   MotherDuck documents loading data from databases (Postgres/MySQL), cloud object storage (S3/GCS/Azure), and dbt as a transformation integration, plus a Postgres-compatible endpoint for BI tools — giving decent database/ETL coverage. However there is no evidence of a broader partner connector catalog for SaaS apps (e.g., Salesforce, Stripe, marketing/CRM tools) or named ETL/ELT partner integrations beyond dbt. Missing for 10: documented SaaS-app connectors, a partner connector directory/marketplace, and named ETL/ELT tool integrations beyond dbt.

   • [claimed-docs] “Learn to load a table from your PostgreSQL or MySQL database into MotherDuck.”
   • [claimed-docs] “Cloud Storage Integration: Query data directly from S3, GCS, Azure Blob Storage, and more”
   • [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] “Use any Postgres-compatible tool, no DuckDB install needed”
   • [claimed-docs] “Postgres endpoint: BI tools, any Postgres client - Use any Postgres-compatible tool, no DuckDB install needed”
   • [claimed-docs] “Load your data from other databases and object storage”

   proof ↗⚑ flag

Loading

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

   weight 3 · round drawn
   BigQuery~partialprobed5/10

   BigQuery's docs confirm a documented `bq` CLI tool used to load data into tables, plus a general 'loading data' guide covering various ingestion methods (scheduled load jobs, streaming via Pub/Sub, database replication), which implies bulk-load support from cloud storage. However, no cited evidence explicitly names CSV, JSON, and Parquet as supported formats or shows a single documented command load from GCS with all three formats. Missing for 10: explicit documentation citation confirming multi-format (CSV/JSON/Parquet) bulk load from GCS via bq load or LOAD DATA statement, and independent/hands-on confirmation of this specific workflow.

   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “you can schedule load jobs. You can schedule one-time or batch data transfers at regular intervals”
   • [claimed-docs] “learn how to use bq, the Python-based command-line interface (CLI) tool for BigQuery to create a dataset, load sample data, and query tables”
   • [probe] “official CLI documented at https://cloud.google.com/bigquery/docs/bq-command-line-tool”

   proof ↗⚑ flag

   MotherDuck~partialclaimed5/10

   Docs confirm cloud object-storage integration (S3, GCS, Azure) with secrets management and general data-loading guidance, implying DuckDB-style single-command ingestion, but no evidence pack item shows an explicit documented command or example loading CSV, JSON, and Parquet specifically from cloud storage in one step. Missing for 10: explicit command syntax/examples (e.g. read_csv/read_json/read_parquet from s3://) and confirmation these formats are all supported via one unified command.

   • [claimed-docs] “Load your data from other databases and object storage”
   • [claimed-docs] “Cloud Storage Integration: Query data directly from S3, GCS, Azure Blob Storage, and more”
   • [claimed-docs] “You can safely store your Amazon S3 credentials in MotherDuck for convenience by creating a SECRET object”
   • [claimed-docs] “You can safely store your Amazon S3 credentials in MotherDuck for convenience by creating a `SECRET` object using the [CREATE SECRET](/sql-r…”
   • [claimed-docs] “Load a DuckDB database into MotherDuck: Upload a local DuckDB database file to MotherDuck cloud storage.”

   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 BigQuery
   BigQuery~partialclaimed6/10

   BigQuery supports continuous ingestion via Pub/Sub subscriptions, Storage Write API streaming, and Datastream-like near-real-time database replication, and Continuous Queries let it process incoming data in real time without customer-managed infra. However, this is a set of ingestion APIs/connectors rather than a single fully managed 'files or events arrive automatically' pipeline product — users still need to configure Pub/Sub topics, write jobs, or use third-party connectors for file-based ingestion (e.g., GCS event triggers aren't detailed here). missing for 10: dedicated managed file-landing-zone auto-ingestion (e.g., GCS auto-load on arrival) evidence, independent hands-on validation of continuous ingestion reliability, and details on error-handling/backfill for streaming pipelines.

   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub. Pub/Sub can handle high throughput of data loads into BigQuery…”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub.”
   • [claimed-docs] “This method enables replicating data from databases to BigQuery in near real time.”
   • [claimed-docs] “Pub/Sub can handle high throughput of data loads into BigQuery. It supports real-time data streaming, loading data as it's generated.”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “Continuous queries let you analyze incoming data in BigQuery in real time.”
   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”

   proof ↗⚑ flag

   MotherDuck~partialclaimed5/10

   MotherDuck offers Flights (scheduled Python jobs for ingest/transform, docs-3, docs-57, docs-62) and connectors to load data from databases/object storage (docs-6, docs-42, docs-56), which reduce some pipeline plumbing, but these are scheduled/batch jobs rather than a true continuous/event-driven streaming ingestion service, and users still must author and manage the job logic. missing for 10: evidence of true real-time/event-driven (CDC or streaming) ingestion, automatic file-arrival triggers (e.g., S3 event notifications), and independent confirmation that Flights eliminates all pipeline maintenance at scale.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Flights handle the infrastructure: Python runtime, scheduling, secrets, logging, and versioning.”
   • [claimed-docs] “Python jobs built by your favorite agent and deployed in MotherDuck. Ingest, enrich, and transform data without expensive ETL.”
   • [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] “Cloud Storage Integration: Query data directly from S3, GCS, Azure Blob Storage, and more”

   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 BigQuery
   BigQuery✓fullclaimed8/10

   BigQuery's first-party notebooks (Colab Enterprise notebooks in BigQuery) explicitly let analysts combine SQL queries with Python code, rich text, and inline visualizations in one integrated interface, directly matching the story. missing for 10: independent/hands-on user corroboration of the notebook experience (evidence is entirely vendor docs) and detail on chart/visualization rendering fidelity.

   • [claimed-docs] “notebooks let you combine SQL queries with Python code, rich text, and visualizations to tell a comprehensive story with your data.”
   • [claimed-docs] “Colab Enterprise notebooks in BigQuery let you perform end-to-end data science and machine learning workflows within a single, integrated in…”
   • [claimed-docs] “End-to-end ML workflows: build, evaluate, and deploy a BigQuery ML model within a single notebook interface.”
   • [claimed-docs] “notebooks let you combine SQL queries with Python code, rich text, and visualizations to tell a comprehensive story with your data”
   • [claimed-docs] “notebook memungkinkan Anda menggabungkan kueri SQL dengan kode Python, teks kaya, dan visualisasi”

   proof ↗⚑ flag

   MotherDuck~partialclaimed4/10

   MotherDuck offers separate pieces that touch this story—SQL querying via CLI/UI, scheduled Python jobs ('Flights'), and AI-generated chart dashboards ('Dives')—but there's no evidence of a first-party notebook interface that lets an analyst interleave SQL and Python cells with inline results/charts in one document. Dives are AI-prompt-driven dashboards, not code notebooks, and Flights are scheduled batch jobs rather than interactive analysis. missing for 10: a unified notebook UI mixing SQL+Python cells, inline chart rendering within that notebook, and any independent/hands-on confirmation of such a workflow.

   • [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.”
   • [claimed-docs] “Flights handle the infrastructure: Python runtime, scheduling, secrets, logging, and versioning.”
   • [claimed-docs] “Python jobs built by your favorite agent and deployed in MotherDuck. Ingest, enrich, and transform data without expensive ETL.”

   proof ↗⚑ flag

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

   weight 2 · round to MotherDuck
   BigQuery~partialclaimed6/10

   BigQuery is fundamentally API/CLI-driven — core operations (querying, DML, loading, streaming via Storage Write API, IAM, Iceberg tables, continuous queries, sharing) all have documented REST/gRPC APIs and a Python-based `bq` CLI, plus ODBC/JDBC drivers, supporting near-full parity for classic data-warehouse functions. However, newer Gemini-powered UI features like conversational analytics, data canvas, and AI-generated SQL/Python assistance are documented only as console experiences with no evidence of an equivalent public API for driving the same conversational/canvas workflows programmatically. Missing for 10: explicit API/SDK parity documentation for conversational analytics and data canvas, and independent confirmation that all UI-exclusive AI features are scriptable via API.

   • [claimed-docs] “Data Manipulation Language (DML) statements enable you to update, insert, and delete data from your BigQuery tables.”
   • [claimed-docs] “vai aprender a usar o `bq`, a ferramenta de interface de linha de comandos (CLI) baseada em Python para o BigQuery, para criar um conjunto d…”
   • [claimed-docs] “we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has lower pricing and …”
   • [claimed-docs] “The Simba Open Database Connectivity (ODBC) and Java Database Connectivity (JDBC) drivers for BigQuery connect your applications to BigQuery…”
   • [claimed-docs] “In diesem Dokument finden Sie eine Liste der vordefinierten IAM-Rollen (Identity and Access Management) und Berechtigungen für BigQuery.”
   • [claimed-docs] “대화형 분석을 사용하면 자연어로 데이터와 대화할 수 있습니다.”
   • [claimed-docs] “BigQuery 데이터 캔버스로 데이터 탐색, 변환, 쿼리, 시각화”
   • [claimed-docs] “BigQuery의 Gemini로 자연어를 사용하여 테이블 애셋을 찾고 조인하고 쿼리하고 결과를 시각화하며 전체 프로세스에서 다른 사용자와 원활하게 공동작업할 수 있습니다.”
   • [claimed-docs] “Data insights offers an automated, intuitive way to uncover patterns and perform statistical analysis by using insightful queries that are g…”

   proof ↗⚑ flag

   MotherDuck~partialcommunity7/10

   MotherDuck exposes broad SQL/API surface—drivers/SDKs, a Postgres endpoint, CLI, and both local and remote MCP servers with read-write SQL (query_rw), schema exploration, sharing/GRANT commands, secrets, and even natural-language dashboard ('Dive') generation via MCP—suggesting most UI actions (querying, sharing, dashboarding, agent workflows) can be done programmatically. However, there's no explicit statement that 100% of UI capabilities (e.g., Instant SQL editor behavior, billing dashboard interactions, Flights scheduling UI) are fully mirrored in the API/CLI, and community threads show confusion about product boundaries (on-prem vs SaaS) rather than confirming parity. missing for 10: explicit vendor claim of full UI/API parity, evidence that billing/Flights scheduling UI actions are fully API-driven, independent confirmation of parity beyond docs.

   • [claimed-docs] “Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “We just released write access for the MotherDuck remote MCP server via the new query_rw tool. Your agents can now INSERT, UPDATE, DELETE, cr…”
   • [claimed-docs] “We just released **write access for the MotherDuck remote MCP server** via the new `query_rw` tool. Your agents can now INSERT, UPDATE, DELE…”
   • [claimed-docs] “The MotherDuck remote MCP Server lets you analyze your data using natural language and generate interactive visualizations, all without writ…”
   • [claimed-docs] “The MotherDuck **remote** MCP Server lets you analyze your data using natural language and generate interactive visualizations, all without …”
   • [claimed-docs] “Postgres endpoint: BI tools, any Postgres client - Use any Postgres-compatible tool, no DuckDB install needed”
   • [claimed-docs] “DuckDB SDKs: Python, Node.js, Go, Rust, R, Java”
   • [claimed-docs] “Grant read access to users or roles for multi-tenant applications and collaboration.”
   • [claimed-docs] “MotherDuck provides SQL views and a billing dashboard to help you understand your compute and storage consumption.”
   • [community] “User confusion about product scope: "Will this be available in duckdb -ui? Is mother duck editor features available on-prem? My understandin…”

   proof ↗⚑ flag

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

   weight 3 · round to BigQuery
   BigQuery~partialclaimed6/10

   BigQuery documents support for open table formats (Iceberg, Delta, Hudi) and Iceberg managed tables that store data in customer-owned buckets, which directly supports data portability/exit without lock-in (docs-10, docs-26, docs-57, docs-86, docs-105). However, there is no explicit documentation of a full 'export all data' workflow (e.g., bq extract to Parquet/Avro/CSV for all datasets) or independent confirmation that this is smooth/complete. missing for 10: explicit export/extract tooling documentation, evidence of exporting non-table data (e.g., logs, ML models, metadata) in open formats, and independent verification of ease of full data export.

   • [claimed-docs] “Iceberg managed tables offer the same fully managed experience as standard BigQuery tables, but store data in customer-owned storage buckets…”
   • [claimed-docs] “Iceberg managed tables support the open Iceberg table format for better interoperability with open-source and third-party compute engines”
   • [claimed-docs] “BigQuery provides a uniform way to work with both structured and unstructured data and supports open table formats like Apache Iceberg, Delt…”
   • [claimed-docs] “supports open table formats like Apache Iceberg, Delta, and Apache Hudi”
   • [claimed-docs] “טבלאות מנוהלות בפורמט Iceberg מציעות את אותה חוויה מנוהלת במלואה כמו טבלאות BigQuery רגילות, אבל הנתונים מאוחסנים בדלי אחסון בבעלות הלקוח”
   • [claimed-docs] “Iceberg managed tables support the open Iceberg table format for better interoperability with open-source and third-party compute engines on…”

   proof ↗⚑ flag

   MotherDuck—none0/10

   The evidence pack covers loading data into MotherDuck (uploading DuckDB files, connecting to Postgres/MySQL, S3 integration) and various query/access surfaces (CLI, Postgres endpoint, MCP, dbt), but there is no documentation of an explicit bulk-export or 'take all your data and leave' capability in open formats (e.g., dumping all tables to Parquet/CSV or full database export for migration away from MotherDuck). Missing for 10: explicit export/download-all-data documentation, open-format bulk export tooling, and any migration-out guide or independent confirmation of full data portability.

   • [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] “Load a DuckDB database into MotherDuck: Upload a local DuckDB database file to MotherDuck cloud storage.”
   • [claimed-docs] “Spin up a fully managed lakehouse with MotherDuck handling both metadata and storage, or bring your own cloud object storage.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   BigQuery—none0/10

   The evidence pack covers BigQuery's SQL, pricing, notebooks, sharing, ML, and compliance certifications, but contains no documentation on dataset/table region selection or data residency controls (e.g., choosing dataset location across regions). This is a standard and applicable feature for a cloud data warehouse, but no evidence in the pack demonstrates it. missing for 10: any mention of dataset location/region selection, multi-region vs single-region storage options, or data residency configuration.

   ⚑ flag

   MotherDuck—none0/10

   The evidence pack mentions sharing data 'publicly with anyone with a MotherDuck account in the same cloud region' (implying multiple regions exist) but contains no documentation of a mechanism for users to select or configure their data's storage region/residency. Absence of evidence for an applicable, common enterprise/privacy capability yields 'none'.

   • [claimed-docs] “MotherDuck's sharing model is specifically optimized for the following scenarios: Sharing data with every preset role in your organization..…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   BigQuery—none0/10

   The evidence pack covers BigQuery features, pricing, compliance certifications, and Gemini-based AI capabilities, but contains no statement or documentation about whether customer data is used to train Google's AI models or how to opt out of such use. Given BigQuery's AI features (Gemini in BigQuery, conversational analytics), this is a fair and applicable privacy question for buyers, but no evidence addresses it either way.

   ⚑ flag

   MotherDuck—none0/10

   No evidence in the pack addresses AI-training data-usage opt-outs or a data-processing policy stating customer data is not used to train models; the pack covers sharing, secrets, SaaS Mode, and MCP access control but not AI-training-data policy.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to BigQuery
   BigQuery~partialclaimed5/10

   BigQuery supports DML DELETE statements, table/dataset-level expiration, time travel windows, and IAM controls for access, which give admins levers to manage retention and deletion, but there is no dedicated documentation on AI-native data retention policies, automated deletion workflows, or privacy-specific controls tailored to AI agents/data used in model training. missing for 10: explicit retention policy configuration docs, AI-specific data deletion/opt-out controls, independent verification of deletion effectiveness.

   • [claimed-docs] “Data Manipulation Language (DML) statements enable you to update, insert, and delete data from your BigQuery tables.”
   • [claimed-docs] “Time travel for historical data access in BigQuery.”
   • [claimed-docs] “This document provides a list of Identity and Access Management (IAM) predefined roles and permissions for BigQuery.”
   • [claimed-docs] “roles and permissions that apply to BigQuery resources such as datasets, tables, views, and routines”

   proof ↗⚑ flag

   MotherDuck—none0/10

   The evidence pack covers authentication, sharing, secrets scoping, billing/usage monitoring, and SaaS Mode for limiting local interaction, but contains no documentation of data retention policies, TTL settings, or explicit data-deletion controls for stored databases/tables. Since a cloud data warehouse could plausibly document such controls, the axis applies, but no evidence shows it is delivered.

   • [claimed-docs] “Secrets are scoped to your user account and are not shared with other users in your organization.”
   • [claimed-docs] “MotherDuck provides SQL views and a billing dashboard to help you understand your compute and storage consumption.”
   • [claimed-docs] “You can limit MotherDuck's ability to interact with your local environment using SaaS Mode”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   BigQuery—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out settings for BigQuery; docs cover IAM, pricing, and features but nothing on data collection or opt-out controls. missing for 10: any documentation of telemetry collection, opt-out settings, or privacy controls for AI-native usage tracking.

   ⚑ flag

   MotherDuck—none0/10

   No evidence in the pack addresses telemetry or usage-tracking opt-out controls for MotherDuck; existing docs cover authentication, SaaS Mode restrictions, sharing, and billing dashboards but never mention telemetry collection or an opt-out mechanism.

   ⚑ 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 MotherDuck
   BigQuery—none0/10

   The evidence pack covers BigQuery's SQL, ML, notebooks, Dataform (ELT transforms), sharing, and Gemini/NL features, but contains no evidence of a governed semantic layer (unified metrics/dimensions/joins definition consumed consistently by BI tools and AI agents) — that capability lives in Looker's modeling layer, not documented here as part of BigQuery itself.

   ⚑ flag

   MotherDuck~partialclaimed4/10

   MotherDuck's MCP docs mention 'Guides' — markdown documents capturing an org's metric definitions, join conventions, and domain context so AI agents produce consistent SQL — which gestures at a semantic-layer intent, but this is informal documentation rather than a structured, declared semantic model (no defined metric/dimension/join objects, no evidence of enforcement across BI tools or non-AI queries). Missing for 10: a first-class semantic-model schema (metrics/dimensions/joins as queryable objects), evidence that both ad-hoc SQL and AI tools consistently resolve against the same governed definitions, and independent confirmation of this working in practice.

   • [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”
   • [claimed-docs] “With the remote MCP server, your agent can: - Execute read-only and read-write SQL against your databases - Explore database schemas, tables…”

   proof ↗⚑ flag

Sharing

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

   weight 1 · round to BigQuery
   BigQuery✓fullclaimed7/10

   BigQuery sharing (Analytics Hub) explicitly lets analysts discover curated third-party and Google datasets via listings and combine them with internal data directly inside BigQuery, including monetized Marketplace listings. missing for 10: independent/hands-on evidence of analysts actually using the marketplace to enrich data, and details on breadth/quality of third-party dataset catalog.

   • [claimed-docs] “La condivisione di BigQuery (precedentemente Analytics Hub) è una piattaforma di scambio di dati che consente di condividere, scoprire e acc…”
   • [claimed-docs] “Puoi utilizzare BigQuery sharing per scoprire set di dati curati di terze parti e di Google e combinarli con i tuoi dati interni”
   • [claimed-docs] “BigQuery sharing (formerly Analytics Hub) is a data exchange platform that lets you securely share, discover, and access data across organiz…”
   • [claimed-docs] “Listings let you share data without replicating data, and you can monetize listings on Google Cloud Marketplace”
   • [claimed-docs] “a data exchange platform that lets you securely share, discover, and access data across organizational boundaries without replicating data”

   proof ↗⚑ flag

   MotherDuck—none0/10

   Evidence shows MotherDuck's data-sharing features (grant roles/orgs access, public shares within a region) but nothing describing a marketplace where analysts can browse and pull in third-party datasets from other providers to enrich their own data. The closest is a single demo share link (hacker_news share) which is not a marketplace feature.

   ⚑ flag

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

   weight 2 · round to BigQuery
   BigQuery✓fullclaimed9/10

   BigQuery sharing (formerly Analytics Hub) is explicitly documented as a data exchange platform that lets you securely share, discover, and access data across organizational boundaries without replicating data, including monetizable listings via Google Cloud Marketplace. This directly matches the story of sharing live datasets cross-account/org without copying or building export pipelines. Missing for 10: independent hands-on corroboration of the sharing/Analytics Hub feature specifically (community evidence in the pack is about pricing/performance, not sharing).

   • [claimed-docs] “La condivisione di BigQuery (precedentemente Analytics Hub) è una piattaforma di scambio di dati che consente di condividere, scoprire e acc…”
   • [claimed-docs] “BigQuery sharing (formerly Analytics Hub) is a data exchange platform that lets you securely share, discover, and access data across organiz…”
   • [claimed-docs] “Listings let you share data without replicating data, and you can monetize listings on Google Cloud Marketplace”
   • [claimed-docs] “Puoi utilizzare BigQuery sharing per scoprire set di dati curati di terze parti e di Google e combinarli con i tuoi dati interni”
   • [claimed-docs] “a data exchange platform that lets you securely share, discover, and access data across organizational boundaries without replicating data”

   proof ↗⚑ flag

   MotherDuck✓fullclaimed8/10

   MotherDuck's Sharing feature lets data-engineers grant read access to Shares across roles/accounts/organizations (including publicly to any account in the same cloud region) without copying data or building ETL pipelines, and lets them scope exposure via include patterns for multi-tenant isolation; the getting-started MCP guide even shows attaching a live share via a 'md:_share/...' path. missing for 10: no independent/hands-on confirmation of cross-organization sharing at scale or performance under live data changes.

   • [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] “Sharing data with every preset role in your organization by granting access to the Explorer role. This is typical of small, highly collabora…”
   • [claimed-docs] “MotherDuck's sharing model is specifically optimized for the following scenarios: Sharing data with every preset role in your organization..…”
   • [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 BigQuery
   BigQuery✓fullclaimed8/10

   BigQuery documents native support for querying open table formats (Iceberg, Delta, Hudi) and external Parquet files in object storage via BigLake/Iceberg managed tables and external tables, without requiring load into proprietary storage. Missing for 10: independent/hands-on corroboration specifically for Delta/Parquet querying (community evidence only covers S3/external table comparisons via Athena, not BigQuery's own Delta/Parquet support) and no detail on performance/limitations of querying Delta directly.

   • [claimed-docs] “BigQuery provides a uniform way to work with both structured and unstructured data and supports open table formats like Apache Iceberg, Delt…”
   • [claimed-docs] “支援 Apache Iceberg、Delta 和 Apache Hudi 等開放資料表格式”
   • [claimed-docs] “Iceberg managed tables offer the same fully managed experience as standard BigQuery tables, but store data in customer-owned storage buckets…”
   • [claimed-docs] “Iceberg managed tables support the open Iceberg table format for better interoperability with open-source and third-party compute engines”
   • [claimed-docs] “Iceberg managed tables support the open Iceberg table format for better interoperability with open-source and third-party compute engines on…”
   • [claimed-docs] “_Schema evolution_, which lets you add, drop, and rename columns to suit your needs.”
   • [claimed-docs] “Time travel for historical data access in BigQuery.”

   proof ↗⚑ flag

   MotherDuck~partialclaimed6/10

   Docs confirm querying data directly from S3/GCS/Azure Blob Storage and building an open lakehouse on your own files via DuckLake (bring-your-own object storage), which covers the 'files in object storage' part of the story, but the evidence never explicitly mentions querying Iceberg or Delta table formats specifically — DuckLake is MotherDuck's own open table format, not documented here as Iceberg/Delta-compatible. missing for 10: explicit Iceberg support, explicit Delta Lake support, independent hands-on confirmation of querying external open-table formats without ingestion.

   • [claimed-docs] “Cloud Storage Integration: Query data directly from S3, GCS, Azure Blob Storage, and more”
   • [claimed-docs] “Use DuckLake to build a data lake on top of your own files”
   • [claimed-docs] “Spin up a fully managed lakehouse with MotherDuck handling both metadata and storage, or bring your own cloud object storage.”
   • [claimed-docs] “A petabyte-scale LAKEHOUSE in 4 lines Spin up a fully managed lakehouse with MotherDuck handling both metadata and storage, or bring your o…”
   • [claimed-docs] “CREATE DATABASE my_ducklake ( TYPE DUCKLAKE, DATA_PATH 's3://mybucket/my_optional_path/' );”

   proof ↗⚑ flag

Performance

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

   weight 2 · round to BigQuery
   BigQuery✓fullcommunity7/10

   BigQuery documents built-in diagnostic query plan and timing information analogous to EXPLAIN, letting engineers see per-stage execution details (bigquery-docs-56/64/75/91/102), and community evidence confirms cost/data-scanned estimation before running queries (bigquery-comm-3, bigquery-comm-4), directly supporting cost/performance debugging. Missing for 10: independent hands-on account specifically using the query plan UI to diagnose a slow query, and deeper docs on slot-utilization/contention visualization in the console.

   • [claimed-docs] “BigQuery includes diagnostic query plan and timing information. This is similar to the information provided by statements such as EXPLAIN in…”
   • [claimed-docs] “BigQuery includes diagnostic query plan and timing information. This is similar to the information provided by statements such as `EXPLAIN` …”
   • [claimed-docs] “Tersemat dalam tugas kueri, BigQuery menyertakan informasi paket kueri dan waktu diagnostik.”
   • [claimed-docs] “BigQuery includes diagnostic query plan and timing information”
   • [claimed-docs] “BigQuery includes diagnostic query plan and timing information.”
   • [community] “BigQuery provides a dry run option to estimate bytes/costs before running a query, and shows bytes-to-be-scanned in small text before you hi…”
   • [community] “I've worked with much larger datasets on BQ (petabyte scale) and managed to not spend more than $1000 in an hour; BQ tells you how much data…”

   proof ↗⚑ flag

   MotherDuck—none0/10

   The evidence pack references a query-performance doc only for read-scaling/Ducklings concurrency, and a billing dashboard for cost visibility, but there is no mention of EXPLAIN/query profiling, execution plan visualization, or slow-query diagnostics tooling. This is a fair and applicable axis for a cloud data warehouse, but no evidence in the pack supports it.

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

   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 BigQuery
   BigQuery~partialclaimed3/10

   Only one thin doc snippet confirms BigQuery has 'Time travel for historical data access,' but the evidence pack provides no detail on querying with FOR SYSTEM_TIME AS OF syntax, the default 7-day retention window, or explicit restoration of dropped/corrupted tables, and no independent/hands-on corroboration. Missing for 10: documented syntax for point-in-time queries, explicit dropped-table restore workflow, retention/configuration details, and independent confirmation.

   • [claimed-docs] “Time travel for historical data access in BigQuery.”

   proof ↗⚑ flag

   MotherDuck—none0/10

   No evidence pack item mentions time travel, point-in-time query, table restore, or history/versioning features; MotherDuck's documented capabilities focus on sharing, MCP, dbt, DuckLake, and cloud storage rather than time-travel/restore functionality.

   ⚑ 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
   BigQuery~partialcommunity5/10

   Docs confirm GoogleSQL is an ANSI-compliant SQL surface with DML, procedural extensions, pipe syntax, and table-valued functions, and community feedback praises its productivity for data exploration (bigquery-docs-23, bigquery-docs-30, bigquery-docs-70, bigquery-docs-87, bigquery-comm-15, bigquery-comm-16), implying a rich native SQL surface without bolt-ons. However, the pack never explicitly documents window functions, CTEs, JSON/semi-structured handling, ARRAY/STRUCT types, or the rich DATE/TIME/TIMESTAMP type system that the story specifically calls out. Missing for 10: explicit evidence of window functions, CTE support, native JSON/semi-structured querying, array/struct handling, and date/time type richness.

   • [claimed-docs] “Query statements... are the primary method to analyze data in BigQuery.”
   • [claimed-docs] “GoogleSQL is an ANSI-compliant Structured Query Language (SQL) that includes the following types of supported statements”
   • [claimed-docs] “Prozedurale Sprachanweisungen sind prozedurale Erweiterungen für GoogleSQL, mit denen Sie mehrere SQL Anweisungen”
   • [claimed-docs] “Le istruzioni di query possono includere la sintassi con operatore pipe”
   • [community] “Review after a week of using BigQuery's new SQL pipe syntax: much more productive for data exploration/cleaning, unifies WHERE/HAVING/QUALIF…”
   • [community] “BigQuery has table-valued functions already, which can be used with pipes with a CALL clause.”

   proof ↗⚑ flag

   MotherDuck~partialcommunity5/10

   MotherDuck is built directly on DuckDB's engine, and evidence confirms CTE support works well in practice (community praise for 'CTE inspection' in Instant SQL) plus general SQL execution via the MCP server and dbt integration, implying the underlying DuckDB SQL dialect (which natively supports window functions, JSON, arrays, and rich date/time types) is exposed. However, the evidence pack contains no explicit documentation citing window functions, JSON/array types, or date/time type support as first-class SQL features. missing for 10: explicit docs/examples of window functions, semi-structured JSON functions, array manipulation, and date/time type handling in MotherDuck's SQL reference.

   • [community] “Praise for MotherDuck's CTE inspection feature in Instant SQL: "CTE inspection is amazing. I spend too much time doing that manually."”
   • [claimed-docs] “Execute read-only and read-write SQL against your databases”
   • [claimed-docs] “The only change needed for motherduck is the path: setting.”

   proof ↗⚑ flag

Streaming

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

   weight 1 · round to BigQuery
   BigQuery✓fullclaimed7/10

   BigQuery documents continuous queries (SQL statements that run continuously to analyze streaming data in real time) and Dataform for declarative, version-controlled ELT pipelines, plus streaming ingestion via the Storage Write API and Pub/Sub subscriptions for near-real-time loading. Together these give data engineers continuous/incremental transformation capabilities natively in the platform. Missing for 10: independent/hands-on corroboration of continuous queries or Dataform pipelines in production, and detail on orchestration/scheduling maturity comparable to dedicated task schedulers.

   • [claimed-docs] “BigQuery の継続的クエリは、継続的に実行される SQL ステートメントです。継続的クエリを使用すると、BigQuery で受信データをリアルタイムで分析できます。”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “Continuous queries let you analyze incoming data in BigQuery in real time.”
   • [claimed-docs] “Dataform is a service for data analysts to develop, test, control versions, and schedule complex workflows for data transformation in BigQue…”
   • [claimed-docs] “Dataform lets you manage data transformation in the Extraction, Loading, and Transformation (ELT) process for data integration.”
   • [claimed-docs] “View a visualization of the dependency tree of your workflow.”
   • [claimed-docs] “Collaborate with team members on workflow development through Git.”
   • [claimed-docs] “The Storage Write API (gRPC) has lower pricing and more robust features, including exactly-once delivery semantics.”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub. Pub/Sub can handle high throughput of data loads into BigQuery…”
   • [claimed-docs] “Pub/Sub can handle high throughput of data loads into BigQuery. It supports real-time data streaming, loading data as it's generated.”
   • [claimed-docs] “You can now create, store, and manage pipelines in Git folders.”

   proof ↗⚑ flag

   MotherDuck~partialclaimed3/10

   MotherDuck offers 'Flights' — scheduled Python jobs for ingest/transform/operational tasks — and dbt integration for batch transformations, which cover incremental/scheduled pipelines but not true continuous or streaming semantics (no CDC, no continuous query engine, no stream/task primitives like Snowflake Streams/Tasks). Missing for 10: native streaming ingestion or CDC support, continuous/materialized query semantics, and declarative pipeline orchestration beyond scheduled batch jobs.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Flights handle the infrastructure: Python runtime, scheduling, secrets, logging, and versioning.”
   • [claimed-docs] “Python jobs built by your favorite agent and deployed in MotherDuck. Ingest, enrich, and transform data without expensive ETL.”
   • [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.”

   proof ↗⚑ flag

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

   weight 2 · round to BigQuery
   BigQuery✓fullclaimed7/10

   BigQuery's documented Storage Write API (gRPC) is explicitly the recommended real-time streaming ingestion path, offering exactly-once delivery semantics, and Pub/Sub streaming subscriptions and continuous queries further support near-real-time analysis of incoming data (docs-1, docs-35, docs-59, docs-93, docs-18, docs-42, docs-54). This directly matches the story's core claim of a documented streaming ingestion API enabling near-real-time queryability. Missing for 10: an explicit 'queryable within seconds' latency benchmark and independent/hands-on corroboration of actual end-to-end streaming latency.

   • [claimed-docs] “The Storage Write API (gRPC) has lower pricing and more robust features, including exactly-once delivery semantics.”
   • [claimed-docs] “we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has lower pricing and …”
   • [claimed-docs] “For new projects, we recommend using the Storage Write API (gRPC) instead of the Storage Write API (REST). The Storage Write API (gRPC) has …”
   • [claimed-docs] “Puedes usar la API de BigQuery Storage Write (gRPC) para transmitir datos a BigQuery.”
   • [claimed-docs] “To stream data into BigQuery, you can use a BigQuery subscription in Pub/Sub. Pub/Sub can handle high throughput of data loads into BigQuery…”
   • [claimed-docs] “Pub/Sub can handle high throughput of data loads into BigQuery. It supports real-time data streaming, loading data as it's generated.”
   • [claimed-docs] “BigQuery continuous queries are SQL statements that run continuously. Continuous queries let you analyze incoming data in BigQuery in real t…”
   • [claimed-docs] “Continuous queries let you analyze incoming data in BigQuery in real time.”

   proof ↗⚑ flag

   MotherDuck—none0/10

   Evidence shows batch-oriented ingestion (file uploads, scheduled Python 'Flights' jobs, database loads) and MCP write access for ad-hoc SQL writes, but no documented streaming ingestion API or guarantee that streamed writes become queryable within seconds. missing for 10: a dedicated streaming/ingest API (e.g. Kafka connector, continuous append endpoint), latency guarantees for streamed data, and any independent confirmation of near-real-time queryability.

   • [claimed-docs] “Run Python jobs on a schedule for ingest, transformation, and operational tasks”
   • [claimed-docs] “Flights handle the infrastructure: Python runtime, scheduling, secrets, logging, and versioning.”
   • [claimed-docs] “Python jobs built by your favorite agent and deployed in MotherDuck. Ingest, enrich, and transform data without expensive ETL.”
   • [claimed-docs] “We just released write access for the MotherDuck remote MCP server via the new query_rw tool. Your agents can now INSERT, UPDATE, DELETE, cr…”
   • [claimed-docs] “Load a DuckDB database into MotherDuck: Upload a local DuckDB database file to MotherDuck cloud storage.”

   proof ↗⚑ flag