ClickHouse vs CockroachDB

Agent ops

1. ai-native userMy coding agent can provision a database end to end — create it, fetch the connection string, apply schema, and run queries — through the API, CLI, or MCP without touching the dashboard

   weight 3 · round to CockroachDB
   ClickHouse~partialprobed6/10

   ClickHouse's CLI (clickhousectl) documentation shows it can create/manage ClickHouse Cloud clusters, manage cloud resources, and execute queries against ClickHouse servers entirely from the command line (clickhouse-docs-17,20,31,32), and an official MCP server (mcp-clickhouse) lets AI assistants connect and query ClickHouse (clickhouse-docs-5,6, clickhouse-probe-4), plus an OpenAPI spec exists for API-based automation (clickhouse-probe-3). However, no evidence explicitly documents fetching a connection string as a discrete step, and the MCP server is framed for connecting to/querying existing databases rather than full provisioning, so the end-to-end 'create→connect→schema→query' agent workflow is only partially evidenced rather than demonstrated as a single seamless path. Missing for 10: explicit connection-string retrieval step, an end-to-end walkthrough or hands-on example of an agent provisioning a fresh cluster via CLI/MCP without dashboard, and independent corroboration of this workflow succeeding in practice.

   • [claimed-docs] “Push your local ClickHouse development to cloud”
   • [claimed-docs] “Set up ClickHouse Cloud and create cloud-managed ClickHouse clusters * Create and manage ClickHouse Cloud Postgres services * Manage ClickHo…”
   • [claimed-docs] “Run and manage local Postgres instances * Execute queries against ClickHouse servers * Set up ClickHouse Cloud and create cloud-managed Clic…”
   • [claimed-docs] “Install and manage local ClickHouse versions * Launch and manage local ClickHouse servers”
   • [claimed-docs] “Choose an MCP client or framework to connect an AI assistant to ClickHouse.”
   • [claimed-docs] “Connect ClickHouse to your AI assistants.”
   • [probe] “PROBE openapi: HTTP 200 at https://clickhouse.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://github.com/ClickHouse/mcp-clickhouse”
   • [probe] “official CLI documented at https://clickhouse.com/docs/concepts/features/interfaces/cli”

   proof ↗⚑ flag

   CockroachDB~partialprobed7/10

   Local provisioning and full SQL schema/query workflows are verified end-to-end via CLI (`cockroach demo` booted a keyless cluster and executed a real CREATE TABLE/INSERT/SELECT roundtrip with no cloud account), and CockroachDB Cloud has a dedicated `ccloud` CLI for creating/connecting clusters plus an official MCP server that supports natural-language table listing, statement execution, and row inserts. However, the managed MCP endpoint is OAuth-gated (401 requiring bearer auth against a protected resource), meaning cloud provisioning via MCP/API isn't fully dashboard-free without an auth setup step, and no REST/API spec was found (openapi probes all 404'd). Missing for 10: a demonstrated single continuous agent flow (create→connect→schema→query) purely through API or MCP without any OAuth/dashboard touchpoint, and a documented REST API surface.

   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [claimed-docs] “The `ccloud` tool is a command-line interface (CLI) tool that allows you to create, manage, and connect to CockroachDB Cloud clusters.”
   • [claimed-docs] “install `ccloud` and use the `ccloud quickstart` command to interactively log in and create a new CockroachDB Serverless cluster.”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cockroachlabs.com/openapi.json, https://docs.cockroachlabs.com/swagger.json, https://do…”

   proof ↗⚑ flag

2. ai-native userAn agent can run SQL and schema operations through scoped tools that distinguish read-only from destructive actions, so I can safely delegate database work

   weight 2 · round to CockroachDB
   ClickHouse~partialprobed4/10

   ClickHouse ships an official MCP server (mcp-clickhouse) letting AI assistants connect and run queries against ClickHouse, and docs mention agent skills/CLI integration, so agents can execute SQL through a sanctioned tool interface. However, none of the evidence describes scoped tool definitions that explicitly separate read-only queries from destructive/schema-changing operations, nor any permissioning model for safe delegation. missing for 10: documentation of read-only vs write/destructive tool scoping, permission controls or guardrails within the MCP server, independent confirmation that agents can't run destructive ops unintentionally.

   • [claimed-docs] “Choose an MCP client or framework to connect an AI assistant to ClickHouse.”
   • [claimed-docs] “Connect ClickHouse to your AI assistants.”
   • [probe] “official MCP server documented at https://github.com/ClickHouse/mcp-clickhouse”
   • [claimed-docs] “Install the official ClickHouse agent skills into supported coding agents”

   proof ↗⚑ flag

   CockroachDB~partialprobed5/10

   CockroachDB Cloud ships an official MCP server (confirmed live and OAuth-gated in probe) that lets an agent run natural-language-driven SQL operations including listing tables, executing statements, and inserting rows, which supports the 'agent runs SQL via tools' half of the story. However, no evidence describes distinct scoped tools separating read-only from destructive/write actions, or any safety controls for delegation. Missing for 10: documented read-only vs. write/destructive tool separation, permission scoping or confirmation gates for destructive operations, and any independent hands-on account of using these MCP tools safely.

   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [probe] “official MCP server documented at https://docs.cockroachlabs.com/docs/cockroachcloud/connect-to-the-cockroachdb-cloud-mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”

   proof ↗⚑ flag

3. ai-native userCheaply create thousands of isolated databases — one per agent, tenant, or preview — and manage the fleet programmatically

   weight 2 · round drawn
   ClickHouse~partialprobed4/10

   ClickHouse Cloud offers a CLI/API to programmatically create and manage cloud-managed clusters and resources, plus usage-based pricing that scales compute to zero when idle, which supports cost-efficient fleet-style provisioning. However, there is no direct evidence describing a pattern for spinning up thousands of isolated per-agent/tenant databases, no documented multi-tenant isolation guidance, and no explicit 'fleet management' API for bulk database lifecycle at that scale. missing for 10: explicit multi-tenant/isolated-database-per-agent provisioning docs, bulk/fleet management API examples, and evidence of cost/performance at thousands-of-databases scale.

   • [claimed-docs] “Set up ClickHouse Cloud and create cloud-managed ClickHouse clusters”
   • [claimed-docs] “Set up ClickHouse Cloud and create cloud-managed ClickHouse clusters * Create and manage ClickHouse Cloud Postgres services * Manage ClickHo…”
   • [claimed-docs] “pay only for the compute and storage you use, scaled separately and down to zero when idle”
   • [claimed-docs] “Usage-based pricing: pay only for the compute and storage you use, scaled separately and down to zero when idle.”
   • [probe] “official CLI documented at https://clickhouse.com/docs/concepts/features/interfaces/cli”

   proof ↗⚑ flag

   CockroachDB~partialprobed4/10

   CockroachDB Cloud offers a programmatic CLI (`ccloud`) for creating/managing clusters and serverless billing that scales to zero when idle, which could support cost-efficient per-tenant provisioning, and `cockroach demo`/single-node clusters show lightweight instance creation is possible. However there is no evidence of a purpose-built mechanism for creating thousands of cheap, isolated databases (e.g., per-agent/tenant sandboxes) or bulk/programmatic fleet management at that scale. Missing for 10: evidence of bulk/batch database creation APIs, per-database cost/isolation guarantees at thousands-scale, and documented tenant-isolation patterns for AI-agent workflows.

   • [claimed-docs] “The `ccloud` tool is a command-line interface (CLI) tool that allows you to create, manage, and connect to CockroachDB Cloud clusters.”
   • [claimed-docs] “install `ccloud` and use the `ccloud quickstart` command to interactively log in and create a new CockroachDB Serverless cluster.”
   • [claimed-docs] “Request Unit consumption scales to zero when your cluster has no activity.”
   • [claimed-docs] “The `cockroach demo` starts a temporary, in-memory CockroachDB cluster of one or more nodes, with or without a preloaded dataset, and opens …”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to ClickHouse
   ClickHouse✓fullprobed9/10

   A live probe confirms llms.txt is served at clickhouse.com/llms.txt returning HTTP 200 with structured content describing ClickHouse, directly satisfying the story; ClickHouse also documents agent skills and MCP integration as complementary agent-oriented resources. Missing for 10: independent/community confirmation that agents actually consume this llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://clickhouse.com/llms.txt # ClickHouse > ClickHouse is a fast open-source column-oriented database manage…”
   • [claimed-docs] “Install the official ClickHouse agent skills into supported coding agents”
   • [claimed-docs] “Choose an MCP client or framework to connect an AI assistant to ClickHouse.”

   proof ↗⚑ flag

   CockroachDB✓fullprobed8/10

   CockroachDB serves a working llms.txt at docs.cockroachlabs.com/llms.txt (HTTP 200, indexing 6364 pages) plus a docs/.md agent-oriented endpoint, both confirmed live via direct probes rather than just vendor claims. missing for 10: no independent/community confirmation that agents actually consume these endpoints successfully, and no OpenAPI spec (404s) to complement the docs for agent tooling.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.cockroachlabs.com/llms.txt # CockroachDB - [CockroachDB (6364 pages)](https://docs.cockroachlabs.c…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.cockroachlabs.com/docs/.md > ## Documentation Index > Fetch the complete documentation index at: htt…”

   proof ↗⚑ flag

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

   weight 2 · round to CockroachDB
   ClickHouse✓fullprobed7/10

   ClickHouse ships a single-binary CLI, clickhouse-local for scripting without a full install, and an HTTP interface with explicit format control (X-ClickHouse-Format), all of which support headless/automated use, plus a simple curl-based install script suited for CI environments. Missing for 10: no explicit CI/pipeline example or GitHub Actions integration doc, and no independent hands-on report specifically confirming CI usage.

   • [claimed-docs] “developers can use SQL commands ... directly from the command line, providing a simple and efficient way to access ClickHouse features witho…”
   • [claimed-docs] “clickhouse-local is an easy-to-use version of ClickHouse that is ideal for developers who need to perform fast processing on local and remot…”
   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment. Quick install gets you a single binary fast”
   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment.”
   • [claimed-docs] “The X-ClickHouse-Format HTTP request header now explicitly selects the format of the response”
   • [claimed-docs] “The X-ClickHouse-Format HTTP request header now explicitly selects the format of the response: it is an alias for the output_format setting,…”
   • [github] “curl https://clickhouse.com/ | sh”
   • [probe] “official CLI documented at https://clickhouse.com/docs/concepts/features/interfaces/cli”

   proof ↗⚑ flag

   CockroachDB✓fullprobed8/10

   The `cockroach demo` and `cockroach start-single-node` commands can run entirely headlessly with no interactive shell or account (verified by a runtime probe executing SQL via `-e` flag, offline, insecure mode), and CockroachDB installs via simple package managers (brew) suitable for CI pipelines. missing for 10: no explicit CI recipe/Docker/GitHub Actions example in docs, and no independent CI-integration case study.

   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach version` printed `Build Tag: v26.3.1` keylessly after `brew install cockroachdb/tap/cockroac…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”
   • [claimed-docs] “The `cockroach demo` starts a temporary, in-memory CockroachDB cluster of one or more nodes, with or without a preloaded dataset, and opens …”
   • [claimed-docs] “A single-node cluster is appropriate for quick SQL testing or app development.”
   • [claimed-docs] “Instruct Homebrew to install CockroachDB: $ brew install cockroachdb/tap/cockroach”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   ClickHouse✓fullprobed8/10

   ClickHouse ships an official MCP server (mcp-clickhouse on GitHub) plus docs guiding users to choose an MCP client/framework to connect an AI assistant to ClickHouse, directly matching the story. Missing for 10: independent hands-on verification of the MCP server's reliability/feature completeness beyond first-party docs.

   • [claimed-docs] “Choose an MCP client or framework to connect an AI assistant to ClickHouse.”
   • [claimed-docs] “Connect ClickHouse to your AI assistants.”
   • [probe] “official MCP server documented at https://github.com/ClickHouse/mcp-clickhouse”

   proof ↗⚑ flag

   CockroachDB✓fullprobed8/10

   CockroachDB Cloud offers an official, documented MCP server enabling natural-language agent interactions (listing tables, executing statements, inserting rows), and a runtime probe confirms the endpoint is live and OAuth-gated exactly as documented. Missing for 10: independent/community hands-on validation of agent workflows beyond first-party docs and probes, and details on feature completeness/limits of the MCP server's tool surface.

   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [probe] “official MCP server documented at https://docs.cockroachlabs.com/docs/cockroachcloud/connect-to-the-cockroachdb-cloud-mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   ClickHouse✓fullprobed8/10

   ClickHouse ships an official CLI (clickhousectl, installed via curl https://clickhouse.com/cli | sh) that manages local/cloud ClickHouse instances, and it explicitly supports installing official agent skills into coding agents, directly targeting AI-native/agentic workflows. missing for 10: independent hands-on community corroboration of the CLI's agentic features specifically (community evidence pack covers general ClickHouse use, not this CLI).

   • [claimed-docs] “Install and manage local ClickHouse versions”
   • [claimed-docs] “Install the official ClickHouse agent skills into supported coding agents”
   • [claimed-docs] “With clickhousectl you can: * Install and manage local ClickHouse versions * Launch and manage local ClickHouse servers”
   • [claimed-docs] “clickhousectl works as a version manager for ClickHouse, inspired by tools like uv and pnpm.”
   • [claimed-docs] “curl https://clickhouse.com/cli | sh”
   • [probe] “official CLI documented at https://clickhouse.com/docs/concepts/features/interfaces/cli”

   proof ↗⚑ flag

   CockroachDB✓fullprobed8/10

   CockroachDB ships an official `cockroach` CLI (demo, start, sql shell) verified via runtime probes performing real SQL roundtrips, plus a separate `ccloud` CLI for cloud cluster management, both documented and hands-on confirmed. This is a general-purpose DB CLI rather than one purpose-built for AI-native/agentic workflows, though the product does offer an MCP server for natural-language agent interaction as a complementary path. Missing for 10: CLI features explicitly marketed toward AI-agent automation (e.g., structured/JSON output modes tailored for agent consumption, agent-specific CLI subcommands) and independent third-party corroboration of ccloud CLI usage.

   • [claimed-docs] “CockroachDB changefeeds have an at-least-once delivery guarantee as well as message ordering guarantees.”
   • [claimed-docs] “The `ccloud` tool is a command-line interface (CLI) tool that allows you to create, manage, and connect to CockroachDB Cloud clusters.”
   • [claimed-docs] “install `ccloud` and use the `ccloud quickstart` command to interactively log in and create a new CockroachDB Serverless cluster.”
   • [probe] “official CLI documented at https://docs.cockroachlabs.com/docs/stable/cockroach-demo”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach version` printed `Build Tag: v26.3.1` keylessly after `brew install cockroachdb/tap/cockroac…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”

   proof ↗⚑ flag

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

   weight 3 · round to ClickHouse
   ClickHouse✓fullprobed8/10

   ClickHouse exposes a documented public HTTP/SQL API, an OpenAPI spec (clickhouse-probe-3), and an llms.txt for AI-native discovery (clickhouse-probe-1), plus a CLI and official MCP server for programmatic/agentic access. This gives AI-native users multiple documented, machine-consumable interfaces to drive the product. missing for 10: independent hands-on validation of the OpenAPI/HTTP API from third parties, and more detail on API versioning/stability guarantees.

   • [probe] “PROBE llms.txt: HTTP 200 at https://clickhouse.com/llms.txt # ClickHouse > ClickHouse is a fast open-source column-oriented database manage…”
   • [probe] “PROBE openapi: HTTP 200 at https://clickhouse.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://github.com/ClickHouse/mcp-clickhouse”
   • [probe] “official CLI documented at https://clickhouse.com/docs/concepts/features/interfaces/cli”
   • [claimed-docs] “Choose an MCP client or framework to connect an AI assistant to ClickHouse.”
   • [claimed-docs] “Connect ClickHouse to your AI assistants.”

   proof ↗⚑ flag

   CockroachDB~partialprobed7/10

   CockroachDB exposes a well-documented, driver-agnostic PostgreSQL wire protocol (verified live via `cockroach demo` running real SQL) plus a documented MCP server for natural-language driving of read/write operations, both confirmed live in the probes. However, there is no discoverable OpenAPI/REST spec (all candidate paths 404), so a fully machine-readable HTTP API for cloud/cluster management is absent — missing for 10: a public OpenAPI/REST spec for cluster administration, independent hands-on confirmation of the MCP server's read/write actions beyond the documented claim.

   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”
   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cockroachlabs.com/openapi.json, https://docs.cockroachlabs.com/swagger.json, https://do…”
   • [probe] “official MCP server documented at https://docs.cockroachlabs.com/docs/cockroachcloud/connect-to-the-cockroachdb-cloud-mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach version` printed `Build Tag: v26.3.1` keylessly after `brew install cockroachdb/tap/cockroac…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   ClickHouse—none0/10

   No evidence describes issuing scoped or least-privilege API credentials/tokens specifically for AI agents; ClickHouse Cloud has general access controls but nothing in this pack documents credential scoping tailored to agentic use.

   ⚑ flag

   CockroachDB—none0/10

   The evidence shows CockroachDB's Cloud MCP server is gated by OAuth (401 + WWW-Authenticate Bearer, resource_metadata endpoint) and that SQL-level roles exist in general, but nothing in the pack documents an actual mechanism for issuing scoped, least-privilege API credentials specifically for an AI agent (e.g., agent-specific API keys, granular OAuth scopes, or role templates for automated clients). Missing for 10: documentation of scoped credential/token issuance workflow for agents, evidence of least-privilege role templates tied to the MCP/API surface, and any hands-on confirmation that such scoping works as intended.

   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to CockroachDB
   ClickHouse—none0/10

   The evidence pack documents ClickHouse's CLI, MCP server, and OpenAPI spec but contains no mention of official client SDKs (e.g., Python, Go, Java client libraries) for building applications, which is what this story specifically asks about.

   ⚑ flag

   CockroachDB~partialcommunity3/10

   CockroachDB doesn't maintain distinct official SDKs; it relies on PostgreSQL wire-protocol compatibility so any standard Postgres client library works, which is documented, but there is no evidence of CockroachDB-branded official SDKs for Python/Go/Java/etc. or AI-agent-specific SDK tooling. missing for 10: dedicated first-party SDKs beyond Postgres driver compatibility, independent corroboration of official SDK maintenance, and any SDK docs targeting AI-native/agentic use cases.

   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”
   • [community] “The wire protocol is compatible with Postgres, which allows re-using battle-tested Postgres clients. However it's a non-starter for my use c…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   ClickHouse—none0/10

   No evidence of any webhook subscription or event-notification mechanism in ClickHouse; the evidence covers CLI, MCP, cloud pricing, vector search, and materialized views but nothing about webhooks for event-driven notifications.

   ⚑ flag

   CockroachDB—none0/10

   The evidence only shows CockroachDB changefeeds with at-least-once delivery guarantees (cockroachdb-docs-5), but no citation explicitly confirms webhook sinks or a webhook subscription mechanism as part of the changefeed feature; older community comments even note the lack of a 'change notification' mechanism. Missing for 10: explicit documentation of webhook sink configuration, webhook payload/auth setup, and any hands-on confirmation of webhook delivery.

   • [claimed-docs] “CockroachDB changefeeds have an at-least-once delivery guarantee as well as message ordering guarantees.”
   • [community] “It looks like there is still no mechanism for change notification, which in our particular case is the only missing feature that prevents us…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   ClickHouse~partialclaimed4/10

   ClickHouse shows early in-product AI features — an AI agent that queries logs/traces/metrics and surfaces summaries in ClickStack notebooks, plus private-preview AI Functions/Inference Service in ClickHouse Cloud — but both are waitlist/private-preview only, not generally available, and no hands-on or community evidence confirms them working in production. Missing for 10: GA availability, independent/community validation of insight quality, and broader in-product suggestion features beyond observability notebooks.

   • [claimed-docs] “You can describe an issue in plain language, and the AI agent will query logs, traces, and metrics on your behalf — surfacing relevant data,…”
   • [claimed-docs] “Sign up for private preview access to AI Functions and the AI Inference Service in ClickHouse Cloud. Use AI functions in si”

   proof ↗⚑ flag

   CockroachDB~partialprobed4/10

   CockroachDB Cloud's official MCP server lets users issue natural-language prompts to query and manipulate data, and a runtime probe confirms the endpoint is live and OAuth-gated as documented, which enables AI-agent-driven exploration of data. However, this is a natural-language query interface, not a native AI insights/suggestions engine (e.g., automatic anomaly detection, recommended optimizations, or generated summaries) built into the product. Missing for 10: evidence of built-in generative insights/analytics beyond NL query passthrough, and independent hands-on validation of insight quality.

   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [probe] “official MCP server documented at https://docs.cockroachlabs.com/docs/cockroachcloud/connect-to-the-cockroachdb-cloud-mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”

   proof ↗⚑ flag

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

   weight 2 · round to ClickHouse
   ClickHouse~partialclaimed4/10

   ClickHouse offers building blocks that could let an AI-native user configure background automation — Incremental Materialized Views that run computation automatically at insert time, ClickPipes for continuous automated data ingestion, and an official MCP server/agent skills so an AI assistant can issue the SQL to set these up — but there is no first-party or independent evidence of a named 'autonomous agent automation' feature that an AI agent sets up and monitors end-to-end in the background; the closest agentic feature (AI notebooks in ClickStack) is an interactive waitlist preview, not an autonomous background automation. Missing for 10: a documented autonomous scheduling/orchestration feature explicitly designed for AI agents, and evidence of it being used hands-on to run unattended background jobs.

   • [claimed-docs] “allow you to shift the cost of computation from query time to insert time, resulting in faster SELECT queries”
   • [claimed-docs] “Incremental Materialized Views (Materialized Views) allow you to shift the cost of computation from query time to insert time, resulting in …”
   • [claimed-docs] “Create and manage ClickPipes for data ingestion (S3, Kafka, Kinesis, Postgres, MySQL, MongoDB, BigQuery)”
   • [claimed-docs] “Choose an MCP client or framework to connect an AI assistant to ClickHouse.”
   • [claimed-docs] “Connect ClickHouse to your AI assistants.”
   • [claimed-docs] “Install the official ClickHouse agent skills into supported coding agents”
   • [claimed-docs] “You can describe an issue in plain language, and the AI agent will query logs, traces, and metrics on your behalf — surfacing relevant data,…”

   proof ↗⚑ flag

   CockroachDB—none0/10

   CockroachDB documents background data mechanisms like changefeeds and backups, but there is no evidence of an AI-native automation framework where an agent can configure tasks that run autonomously in the background; the MCP server evidence only covers interactive read/write operations, not scheduled or persistent automations.

   • [claimed-docs] “CockroachDB changefeeds have an at-least-once delivery guarantee as well as message ordering guarantees.”
   • [claimed-docs] “You can create full or incremental backups of a , , or . Taking regular backups of your data is an operational best practice.”
   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”

   proof ↗⚑ flag

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

   weight 3 · round to ClickHouse
   ClickHouse~partialclaimed3/10

   ClickHouse Cloud is previewing an in-product AI agent (ClickStack AI notebooks) that can query logs/traces/metrics on the user's behalf, and a separate AI Functions/Inference Service is also in private preview — but both are waitlist-only, not generally available built-in assistants. Missing for 10: GA availability of the assistant, first-party documentation beyond waitlist pages, and independent/hands-on evidence of it actually delegating tasks.

   • [claimed-docs] “You can describe an issue in plain language, and the AI agent will query logs, traces, and metrics on your behalf — surfacing relevant data,…”
   • [claimed-docs] “Sign up for private preview access to AI Functions and the AI Inference Service in ClickHouse Cloud. Use AI functions in si”
   • [claimed-docs] “Sign up for private preview access to ClickStack Cloud, a fully turnkey observability platform built on ClickHouse. Send OpenTelemetry logs,…”

   proof ↗⚑ flag

   CockroachDB—none0/10

   Evidence only shows CockroachDB Cloud's MCP server, which lets external AI agents connect to and query CockroachDB using natural language — this is CockroachDB acting as a tool for outside AI agents, not a built-in assistant inside the product to which a user delegates tasks. No evidence of an in-console AI assistant/copilot feature exists in the pack.

   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”

   proof ↗⚑ flag

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

   weight 2 · round to CockroachDB
   ClickHouse~partialprobed5/10

   ClickHouse supports natural-language operation indirectly via its official MCP server and agent skills, which let external AI assistants translate NL into SQL/actions against ClickHouse, and a waitlisted AI-notebooks feature lets users 'describe an issue in plain language' to get results. However, this relies on third-party AI clients/MCP frameworks rather than a built-in NL interface, and the most direct plain-language feature is still in private preview/waitlist, not GA. Missing for 10: a generally-available first-party NL command interface (not waitlist-only), and independent hands-on evidence of NL command reliability.

   • [claimed-docs] “Install the official ClickHouse agent skills into supported coding agents”
   • [claimed-docs] “Choose an MCP client or framework to connect an AI assistant to ClickHouse.”
   • [claimed-docs] “Connect ClickHouse to your AI assistants.”
   • [claimed-docs] “You can describe an issue in plain language, and the AI agent will query logs, traces, and metrics on your behalf — surfacing relevant data,…”
   • [probe] “official MCP server documented at https://github.com/ClickHouse/mcp-clickhouse”

   proof ↗⚑ flag

   CockroachDB✓fullprobed7/10

   CockroachDB Cloud ships an official MCP server that explicitly lets users issue natural-language prompts to list tables, execute statements, and insert rows, and a runtime probe confirms the documented MCP endpoint is live and OAuth-gated exactly as described. This is a direct, first-party natural-language interface to database operations rather than just NL-to-SQL translation elsewhere. Missing for 10: independent/hands-on evidence of an actual successful NL command being executed end-to-end (beyond auth handshake), and confirmation that this capability extends to self-hosted (non-Cloud) CockroachDB deployments.

   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [probe] “official MCP server documented at https://docs.cockroachlabs.com/docs/cockroachcloud/connect-to-the-cockroachdb-cloud-mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   ClickHouse—none0/10

   The only relevant evidence is that an OpenAPI spec file exists at clickhouse.com/openapi.json (clickhouse-probe-3), but there is no evidence of an actual interactive API reference UI (e.g., Swagger/Redoc-style browser) or runnable code examples tied to it. Missing for 10: an interactive docs page, 'try it out' functionality, and runnable example snippets tied to the API reference.

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

   proof ↗⚑ flag

   CockroachDB—none0/10

   CockroachDB documents SQL reference, quickstarts, and an interactive `cockroach demo` shell, but there is no evidence of an interactive API reference (e.g., an OpenAPI/Swagger-style explorer with runnable examples) — the openapi probe explicitly found all candidate spec paths returning 404. This axis is plausible for a database's developer docs site, so the absence of evidence yields 'none' rather than 'na'.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cockroachlabs.com/openapi.json, https://docs.cockroachlabs.com/swagger.json, https://do…”

   proof ↗⚑ flag

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

   weight 2 · round to ClickHouse
   ClickHouse✓fullprobed9/10

   A probe confirms a live, machine-readable OpenAPI spec at https://clickhouse.com/openapi.json returning HTTP 200 with an 'openapi' key, and ClickHouse also publishes an llms.txt for AI-native discovery. Missing for 10: no independent/community corroboration of the OpenAPI spec's completeness or usage.

   • [probe] “PROBE openapi: HTTP 200 at https://clickhouse.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://clickhouse.com/llms.txt # ClickHouse > ClickHouse is a fast open-source column-oriented database manage…”

   proof ↗⚑ flag

   CockroachDB—none0/10

   CockroachDB Cloud does offer a management API/CLI, but the evidence pack shows an explicit probe for a machine-readable API spec (openapi.json, swagger.json, etc.) at the docs domain returning 404 on every candidate path, and no other citation surfaces an OpenAPI or equivalent spec anywhere in the docs or cloud console.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cockroachlabs.com/openapi.json, https://docs.cockroachlabs.com/swagger.json, https://do…”

   proof ↗⚑ flag

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

   weight 1 · round to CockroachDB
   ClickHouse~partialprobed6/10

   ClickHouse offers clickhouse-local and clickhousectl for spinning up local/ephemeral ClickHouse instances for testing without touching a production cluster, and chdb for in-process experimentation, which functionally serve as sandbox environments. However, there's no explicit 'sandbox mode' or dedicated test-data isolation feature marketed for AI agents specifically, and no evidence of built-in safeguards preventing accidental production writes. Missing for 10: explicit sandbox/test-environment product feature, documentation tying local instances to safe AI-agent testing workflows, and independent verification that local/dev setups are isolated from production by design.

   • [claimed-docs] “developers can use SQL commands ... directly from the command line, providing a simple and efficient way to access ClickHouse features witho…”
   • [claimed-docs] “clickhouse-local is an easy-to-use version of ClickHouse that is ideal for developers who need to perform fast processing on local and remot…”
   • [claimed-docs] “With clickhousectl you can: * Install and manage local ClickHouse versions * Launch and manage local ClickHouse servers”
   • [claimed-docs] “clickhousectl works as a version manager for ClickHouse, inspired by tools like uv and pnpm.”
   • [claimed-docs] “Experience the power of ClickHouse, in-process. With unparalleled performance, reliability, and scalability for any data-intensive applicati…”
   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment.”
   • [probe] “official CLI documented at https://clickhouse.com/docs/concepts/features/interfaces/cli”

   proof ↗⚑ flag

   CockroachDB✓fullprobed8/10

   `cockroach demo` spins up a temporary, in-memory, single-node/multi-node cluster with a real interactive SQL shell that runs entirely offline with no cloud account, letting an AI-native user run test queries/CRUD without touching production data — confirmed by both docs and a hands-on runtime probe showing a full CREATE/INSERT/SELECT roundtrip. missing for 10: independent third-party corroboration beyond vendor docs/probe, and explicit documentation tying this sandbox workflow specifically to AI-agent/MCP-driven testing rather than manual SQL shell use.

   • [claimed-docs] “The `cockroach demo` starts a temporary, in-memory CockroachDB cluster of one or more nodes, with or without a preloaded dataset, and opens …”
   • [claimed-docs] “A single-node cluster is appropriate for quick SQL testing or app development.”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   ClickHouse—none0/10

   The evidence shows changelog entries documenting breaking behavior changes (e.g., default value and HTTP header changes) and an OpenAPI spec exists, but there is no documented API versioning scheme or formal deprecation policy anywhere in the pack.

   • [claimed-docs] “The default value of max_insert_threads changed from 1 to auto, which resolves to the number of CPU cores available to the server. This para…”
   • [claimed-docs] “The X-ClickHouse-Format HTTP request header now explicitly selects the format of the response”
   • [claimed-docs] “The X-ClickHouse-Format HTTP request header now explicitly selects the format of the response: it is an alias for the output_format setting,…”
   • [probe] “PROBE openapi: HTTP 200 at https://clickhouse.com/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   CockroachDB—none0/10

   The evidence pack contains no documentation of API versioning schemes or a deprecation policy for CockroachDB's SQL/client APIs, MCP server, or Cloud APIs. While such a policy is plausible for a database product (SQL compatibility, wire protocol versions, Cloud API), nothing in the provided evidence addresses it, so it cannot be credited.

   ⚑ flag

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

   weight 2 · round to ClickHouse
   ClickHouse✓fullprobed7/10

   ClickHouse's SQL engine natively supports bulk operations across massive row counts — documented bulk/async insert strategies, parallelized INSERT SELECT by default, and materialized views that batch-process computation at insert time — and this is corroborated by independent users ingesting billions of rows/day with fast bulk queries. AI-native access to this bulk capability is enabled via the official CLI and MCP server, letting an AI agent issue such bulk SQL operations directly. Missing for 10: no evidence of an AI-agent-specific batch/bulk API (e.g., a dedicated bulk-operation endpoint for the MCP tool) beyond general SQL bulk insert/query support.

   • [claimed-docs] “How to choose an insert strategy, including bulk and asynchronous inserts.”
   • [claimed-docs] “The default value of max_insert_threads changed from 1 to auto, which resolves to the number of CPU cores available to the server. This para…”
   • [claimed-docs] “Incremental Materialized Views (Materialized Views) allow you to shift the cost of computation from query time to insert time, resulting in …”
   • [community] “I'm using Clickhouse to dump 1-5 billion rows per day from my company's traffic data, with 60 days retained, onto a single i5 desktop. Compl…”
   • [community] “Overall positive experience: 3-node cluster up quickly with official Docker images, ingested billions of rows fast, great compression. Downs…”
   • [probe] “official MCP server documented at https://github.com/ClickHouse/mcp-clickhouse”
   • [probe] “official CLI documented at https://clickhouse.com/docs/concepts/features/interfaces/cli”

   proof ↗⚑ flag

   CockroachDB~partialclaimed5/10

   CockroachDB is a distributed SQL database and standard SQL/Postgres-compatible clients naturally support batch INSERTs, transactions, and bulk import/export via backup-restore, but the evidence pack has no explicit documentation of bulk/batch operations (e.g., IMPORT, multi-row INSERT, bulk API) and the MCP server docs only mention inserting single rows via natural language rather than bulk multi-item operations. Missing for 10: explicit bulk-insert/IMPORT documentation, evidence of the MCP or CLI performing multi-item bulk operations in one call, and independent confirmation of bulk-operation performance at scale.

   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [claimed-docs] “You can create full or incremental backups of a , , or . Taking regular backups of your data is an operational best practice.”
   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”

   proof ↗⚑ flag

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

   weight 3 · round to ClickHouse
   ClickHouse~partialclaimed4/10

   ClickHouse's incremental materialized views automatically trigger computation when new data (events/inserts) arrive, shifting cost from query time to insert time — a limited form of 'rule triggers on event' behavior, but this is scoped to SQL transformation, not a general action/automation rules engine (e.g. alerts, webhooks, external actions). Missing for 10: evidence of a broader rule/alerting/action framework, triggers tied to arbitrary conditions beyond inserts, or integration with external action systems (notifications, workflows).

   • [claimed-docs] “allow you to shift the cost of computation from query time to insert time, resulting in faster SELECT queries”
   • [claimed-docs] “Incremental Materialized Views (Materialized Views) allow you to shift the cost of computation from query time to insert time, resulting in …”

   proof ↗⚑ flag

   CockroachDB~partialclaimed3/10

   CockroachDB offers changefeeds (CDC) that emit ordered, at-least-once delivery events to external systems, which can be used to build event-driven automation outside the database, but there is no evidence of a native rule/trigger engine that itself defines conditions and executes actions in response to events. missing for 10: native trigger/rule syntax, conditional action execution inside CockroachDB, documented automation examples beyond raw change-event streaming.

   • [claimed-docs] “CockroachDB changefeeds have an at-least-once delivery guarantee as well as message ordering guarantees.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   ClickHouse—none0/10

   ClickHouse is a database with CLI, cloud, MCP, and materialized view features, but there is no evidence of a job scheduler or workflow orchestration capability for recurring tasks; this is an applicable axis (databases can offer scheduled queries/cron jobs) but no such feature is documented.

   ⚑ flag

   CockroachDB—none0/10

   The evidence pack covers backups, restore, changefeeds, MCP connectivity, and cluster management, but nothing describes a scheduling mechanism for recurring jobs or workflows (e.g., cron-like scheduled SQL/backup jobs) that an AI-native user could invoke. Since database products plausibly could offer such scheduling (e.g., scheduled backups), the axis applies, but no evidence documents it here.

   ⚑ flag

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

   weight 1 · round drawn
   ClickHouse—none0/10

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

   ⚑ flag

   CockroachDB—none0/10

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

   ⚑ flag

Branching

1. developerReset a branch from its parent or restore it to an earlier state without rebuilding from a dump

   weight 1 · round drawn
   ClickHouse—none0/10

   The evidence pack contains no mention of database branching, parent/child branch resets, or restoring branch state without rebuilding from a dump — this is a database branching feature (as seen in products like PlanetScale/Neon) that ClickHouse's docs never reference. Nothing in the docs, changelogs, or community discussion addresses branch lifecycle management.

   ⚑ flag

   CockroachDB—none0/10

   The evidence pack covers CockroachDB's backup/restore and point-in-time restore features but contains no mention of a 'branch' concept, branch creation, or resetting a branch from its parent — capabilities central to this story. Since database branching is a reasonable feature category for a modern SQL database to offer, its total absence here means the story is unmet rather than out-of-category.

   • [claimed-docs] “You can create full or incremental backups of a , , or . Taking regular backups of your data is an operational best practice.”
   • [claimed-docs] “A restore from an arbitrary point in time within the revision history of a backup.”

   proof ↗⚑ flag

2. platform-engineerCreate and tear down per-pull-request database branches automatically from CI or my deploy platform

   weight 2 · round drawn
   ClickHouse—none0/10

   No evidence of any database-branching feature (e.g., copy-on-write branches per PR) or CI/deploy-platform integration for creating/tearing down ephemeral database branches; ClickHouse's evidence covers local/cloud CLI setup, scaling, and pricing but nothing about branch-per-PR workflows.

   ⚑ flag

   CockroachDB—none0/10

   No evidence of a branching feature (e.g., copy-on-write database branches per PR) or CI/deploy-platform integration for automated branch creation/teardown; only unrelated capabilities like `cockroach demo` (ephemeral in-memory instance) and ccloud cluster creation are documented, neither of which supports per-PR branch lifecycle automation.

   • [claimed-docs] “The `cockroach demo` starts a temporary, in-memory CockroachDB cluster of one or more nodes, with or without a preloaded dataset, and opens …”
   • [claimed-docs] “The `ccloud` tool is a command-line interface (CLI) tool that allows you to create, manage, and connect to CockroachDB Cloud clusters.”
   • [claimed-docs] “install `ccloud` and use the `ccloud quickstart` command to interactively log in and create a new CockroachDB Serverless cluster.”

   proof ↗⚑ flag

3. developerCreate an instant copy-on-write branch of my database — schema and data — to develop and test against production-shaped data

   weight 3 · round drawn
   ClickHouse—none0/10

   No evidence of a copy-on-write branching feature for schema+data in ClickHouse; the docs describe local dev servers, cloud clusters, CLI tooling, materialized views, and pricing, but nothing about instant branch/fork of a database for testing against production-shaped data.

   ⚑ flag

   CockroachDB—none0/10

   No evidence of a copy-on-write branching feature for schema+data in CockroachDB; the pack only shows backups/restores, demo clusters, and single-node dev instances, none of which provide instant branchable copies of production data.

   ⚑ flag

Drivers

1. developerQuery over HTTP or WebSockets from serverless and edge functions with an official driver built for short-lived connections

   weight 2 · round drawn
   ClickHouse—none0/10

   Evidence shows ClickHouse has a generic HTTP interface (format headers) but no mention of an official driver purpose-built for serverless/edge functions, no WebSocket support, and no discussion of short-lived-connection optimizations for edge runtimes.

   ⚑ flag

   CockroachDB—none0/10

   CockroachDB supports the standard PostgreSQL wire protocol via TCP connections and any Postgres driver, but there is no evidence of an official HTTP/WebSocket driver designed for stateless, short-lived serverless/edge function connections (unlike e.g. Neon's serverless driver). No documentation or product mentions this capability.

   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”
   • [community] “The wire protocol is compatible with Postgres, which allows re-using battle-tested Postgres clients. However it's a non-starter for my use c…”

   proof ↗⚑ flag

Latency

1. developerPlace data or replicas in regions close to my users to keep read latency low worldwide

   weight 2 · round to CockroachDB
   ClickHouse—none0/10

   The evidence pack covers CLI tools, MCP integration, materialized views, vector search, pricing/autoscaling, and community sentiment on performance/compression, but contains no mention of multi-region deployment, region selection for ClickHouse Cloud services, or geo-distributed replica placement to reduce latency for global users. This is a fair question for a distributed database, so the axis applies, but there is no supporting evidence, yielding 'none'.

   ⚑ flag

   CockroachDB✓fullcommunity8/10

   CockroachDB's docs describe explicit multi-region primitives—survival goals and table locality—for placing data/replicas close to users to reduce latency, plus survives datacenter failures with minimal latency disruption, directly matching the story. Missing for 10: independent latency benchmarks confirming real-world regional read-latency improvements, and community comments (comm-2) note multi-region can be restricted under certain licensing tiers, which is a real-world caveat on availability of the feature.

   • [claimed-docs] “_Survival goal_ dictates how many simultaneous failure(s) a database can survive.”
   • [claimed-docs] “_Table locality_ determines how CockroachDB optimizes access to a table's data.”
   • [claimed-docs] “_Table locality_ determines how CockroachDB optimizes access to a table’s data.”
   • [claimed-docs] “survives** disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention”
   • [claimed-docs] “survives disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention; supports strongly-con…”
   • [community] “For me it was the multiple regions. It's like.. with that disabled why are we even here? Data residency is the whole point...”

   proof ↗⚑ flag

Pooling

1. platform-engineerA built-in connection pooler handles thousands of concurrent connections without me operating my own pgbouncer or proxy

   weight 2 · round drawn
   ClickHouse—none0/10

   No evidence pack item mentions a built-in connection pooler, pgbouncer replacement, or handling of concurrent connection scaling within ClickHouse itself; evidence covers CLI, MCP, pricing autoscaling of compute, and general performance but not connection pooling.

   ⚑ flag

   CockroachDB—none0/10

   The evidence pack shows CockroachDB supports the Postgres wire protocol and various client drivers, but nowhere documents a built-in connection pooler (equivalent to pgbouncer) that manages thousands of concurrent client connections. No mention of connection pooling, session multiplexing, or proxy-replacement architecture appears in any docs, community, or probe items.

   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”
   • [claimed-docs] “CockroachDB is a cloud-agnostic, PostgreSQL compatible database built for modern applications”

   proof ↗⚑ flag

Ai data

1. developerStore embeddings and run vector similarity search natively without adding a separate vector database

   weight 2 · round drawn
   ClickHouse✓fullclaimed7/10

   ClickHouse's docs explicitly document native exact and approximate vector similarity search written directly in SQL via ANN indexes, with tunable accuracy/speed trade-offs, meaning embeddings can be stored and searched without a separate vector DB. Missing for 10: independent/hands-on community validation of vector search performance and concrete embedding-storage usage examples beyond first-party docs.

   • [claimed-docs] “A vector search (exact or approximate) can be written in SQL as follows”
   • [claimed-docs] “A vector search (exact or approximate) can be written in SQL”
   • [claimed-docs] “Many approximate techniques provide parameters to tune the trade-off between the result accuracy and the search time.”
   • [claimed-docs] “Documentation for Exact and Approximate Vector Search”

   proof ↗⚑ flag

   CockroachDB✓fullclaimed7/10

   CockroachDB documents a native VECTOR type and vector indexes supporting efficient approximate nearest neighbor (ANN) search on high-dimensional columns, compatible with the pgvector extension, meaning developers can store embeddings and run similarity search directly in CockroachDB without a separate vector DB. Missing for 10: hands-on/independent corroboration of vector search performance or real-world usage reports, and no community discussion validating this feature in practice.

   • [claimed-docs] “A _vector index_ enables efficient approximate nearest neighbor (ANN) search on high-dimensional columns.”
   • [claimed-docs] “`VECTOR` functionality is compatible with the [`pgvector`](https://github.com/pgvector/pgvector) extension for PostgreSQL.”

   proof ↗⚑ flag

Analytics

1. developerRun heavy analytical aggregations over large tables fast enough for dashboards without exporting to a separate warehouse

   weight 2 · round to ClickHouse
   ClickHouse✓fullcommunity8/10

   ClickHouse's core design (columnar, MergeTree, incremental materialized views to precompute aggregations) is documented for fast analytical queries, and this is strongly corroborated by independent community reports of real-time aggregation over hundreds of millions/billions of rows at low cost, replacing Elasticsearch/Druid at scale, and use as a single-node BI backend without a separate warehouse (clickhouse-comm-18, -20, -12, -13, -15, -11, clickhouse-docs-9/18/12). Missing for 10: a documented head-to-head dashboard-latency benchmark, and mention of caveats like limited JOIN performance (clickhouse-comm-19) that could affect some aggregation workloads.

   • [claimed-docs] “allow you to shift the cost of computation from query time to insert time, resulting in faster SELECT queries”
   • [claimed-docs] “Incremental Materialized Views (Materialized Views) allow you to shift the cost of computation from query time to insert time, resulting in …”
   • [claimed-docs] “Powering agentic systems with millisecond queries at petabyte scale.”
   • [community] “I'm using Clickhouse to dump 1-5 billion rows per day from my company's traffic data, with 60 days retained, onto a single i5 desktop. Compl…”
   • [community] “I've used it in production for a year and a half - no other database gives real-time aggregation over hundreds of millions of rows inserted …”
   • [community] “ClickHouse is incredible. It has replaced a large, expensive and slow Elasticsearch cluster at Contentsquare - 300 Elastic nodes vs 12 Click…”
   • [community] “Druid got blown away by ClickHouse at eBay: Druid needed 700+ servers versus a 2-region fully replicated ClickHouse system of 40 nodes.”
   • [community] “Compared to Postgres, Clickhouse was a couple orders of magnitude faster for our query pattern, and easier to set up a single-node config th…”
   • [community] “People often think ClickHouse is useful only for TBs of data. That's wrong! It perfectly works on a single-server as a data source for self-…”
   • [community] “Overall positive experience: 3-node cluster up quickly with official Docker images, ingested billions of rows fast, great compression. Downs…”

   proof ↗⚑ flag

   CockroachDB—none0/10

   The evidence pack covers CockroachDB's OLTP features (ACID transactions, backups, changefeeds, multi-region, vector indexes) but contains no mention of analytical/OLAP acceleration, columnar execution, materialized views, or benchmarks showing fast large-table aggregation performance suitable for dashboards. Nothing addresses avoiding a separate warehouse for analytics. missing for 10: any documentation of analytical query performance, columnar/vectorized execution engine, dashboard-scale aggregation benchmarks, or HTAP-specific tooling.

   ⚑ flag

Compatibility

1. developerI get real engine compatibility — the Postgres, MySQL, or SQLite dialect and extensions my existing code expects — not a lookalike subset

   weight 3 · round to CockroachDB
   ClickHouse—none0/10

   ClickHouse uses its own SQL dialect; there is no evidence of genuine Postgres/MySQL/SQLite wire- or dialect-level compatibility for existing application code. Evidence instead points to the CLI managing separate Postgres instances/services (unrelated to ClickHouse's own SQL engine) and community feedback explicitly notes 'not-quite-standard SQL syntax' compared to standard dialects.

   • [claimed-docs] “Set up ClickHouse Cloud and create cloud-managed ClickHouse clusters * Create and manage ClickHouse Cloud Postgres services * Manage ClickHo…”
   • [claimed-docs] “Run and manage local Postgres instances * Execute queries against ClickHouse servers * Set up ClickHouse Cloud and create cloud-managed Clic…”
   • [community] “Overall positive experience: 3-node cluster up quickly with official Docker images, ingested billions of rows fast, great compression. Downs…”

   proof ↗⚑ flag

   CockroachDB!disputedcontradicted5/10

   CockroachDB documents and demonstrates real PostgreSQL wire-protocol compatibility (standard pg drivers work, `cockroach demo` runs actual SQL round-trips) rather than a toy subset, but hands-on community reports concretely contradict 'full' Postgres compatibility — e.g. missing array columns ('it lacks array columns, which Postgres supports') and, historically, missing change-notification/CDC — meaning code written against real Postgres dialect features can break. There is no MySQL or SQLite dialect compatibility at all, only Postgres. Missing for 10: MySQL/SQLite compatibility, resolution of the array-column and other documented Postgres feature gaps, and independent verification that these gaps are now closed.

   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”
   • [claimed-docs] “CockroachDB is a cloud-agnostic, PostgreSQL compatible database built for modern applications”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”
   • [community] “The wire protocol is compatible with Postgres, which allows re-using battle-tested Postgres clients. However it's a non-starter for my use c…”
   • [community] “It looks like there is still no mechanism for change notification, which in our particular case is the only missing feature that prevents us…”

   proof ↗⚑ flag

Local loop

1. developerThe official CLI covers my daily loop — create, connect, shell into, and inspect databases — without opening the dashboard

   weight 2 · round drawn
   ClickHouse✓fullprobed8/10

   ClickHouse ships an official clickhousectl CLI documented to install/manage local versions, launch/manage local servers, execute queries against servers, connect to Postgres, and push local dev to cloud, covering the create/connect/shell/inspect loop without a dashboard; clickhouse-local and single-binary install further support local dev workflows. Missing for 10: independent hands-on developer accounts specifically praising/critiquing the clickhousectl CLI daily loop (community evidence covers ClickHouse server usage generally, not the CLI tool itself), and detail on 'inspect' commands like schema browsing beyond query execution.

   • [claimed-docs] “With clickhousectl you can: * Install and manage local ClickHouse versions * Launch and manage local ClickHouse servers”
   • [claimed-docs] “clickhousectl works as a version manager for ClickHouse, inspired by tools like uv and pnpm.”
   • [claimed-docs] “Run and manage local Postgres instances * Execute queries against ClickHouse servers * Set up ClickHouse Cloud and create cloud-managed Clic…”
   • [claimed-docs] “Install and manage local ClickHouse versions * Launch and manage local ClickHouse servers”
   • [claimed-docs] “Push your local ClickHouse development to cloud”
   • [claimed-docs] “curl https://clickhouse.com/cli | sh”
   • [probe] “official CLI documented at https://clickhouse.com/docs/concepts/features/interfaces/cli”
   • [claimed-docs] “clickhouse-local is an easy-to-use version of ClickHouse that is ideal for developers who need to perform fast processing on local and remot…”
   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment. Quick install gets you a single binary fast”

   proof ↗⚑ flag

   CockroachDB✓fullprobed8/10

   The `cockroach` CLI covers the daily loop: `cockroach demo`/`cockroach start-single-node` create and connect to a cluster with an interactive SQL shell, verified hands-on via runtime probes showing a keyless install and real SQL roundtrip entirely offline. Docs and probes confirm install (brew), demo/shell, and Postgres-wire-protocol connectivity for inspection via any SQL client. Missing for 10: independent (non-vendor) third-party validation of the full CLI daily loop beyond the single runtime probe, and explicit CLI subcommand documentation for 'inspect' beyond SQL shell usage.

   • [claimed-docs] “The `cockroach demo` starts a temporary, in-memory CockroachDB cluster of one or more nodes, with or without a preloaded dataset, and opens …”
   • [claimed-docs] “A single-node cluster is appropriate for quick SQL testing or app development.”
   • [claimed-docs] “Instruct Homebrew to install CockroachDB: $ brew install cockroachdb/tap/cockroach”
   • [probe] “official CLI documented at https://docs.cockroachlabs.com/docs/stable/cockroach-demo”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach version` printed `Build Tag: v26.3.1` keylessly after `brew install cockroachdb/tap/cockroac…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”

   proof ↗⚑ flag

2. developerRun the same engine locally and keylessly — no account or cloud dependency — for offline development and CI tests

   weight 3 · round drawn
   ClickHouse✓fullcommunity9/10

   ClickHouse ships an open-source single binary and clickhouse-local that run entirely locally without any account or cloud dependency, explicitly marketed for building/testing/experimenting and fast local/CI file processing via SQL (clickhouse-docs-23, clickhouse-docs-27, clickhouse-docs-15, clickhouse-docs-1). Community corroboration confirms clickhouse-local's local, keyless utility for ad-hoc SQL processing (clickhouse-comm-4). Missing for 10: no explicit CI-pipeline example/tutorial demonstrating offline test usage in evidence.

   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment. Quick install gets you a single binary fast”
   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment.”
   • [claimed-docs] “clickhouse-local is an easy-to-use version of ClickHouse that is ideal for developers who need to perform fast processing on local and remot…”
   • [claimed-docs] “developers can use SQL commands ... directly from the command line, providing a simple and efficient way to access ClickHouse features witho…”
   • [github] “curl https://clickhouse.com/ | sh”
   • [community] “Clickhouse is criminally underused. It's common knowledge that 'postgres is all you need' - but if you reach the stage where postgres isn't …”

   proof ↗⚑ flag

   CockroachDB✓fullprobed9/10

   CockroachDB ships as a downloadable binary (brew install) and `cockroach demo`/single-node start modes that spin up a full in-memory or local cluster with an interactive SQL shell, requiring no account, license key entry, or cloud dependency; a runtime probe confirms a keyless offline SQL roundtrip actually executed. This directly satisfies local/offline dev and CI use since the same open-source engine runs identically to production. missing for 10: explicit first-party documentation or example of wiring `cockroach demo`/single-node mode into a CI pipeline, and independent (non-vendor) confirmation of CI usage.

   • [claimed-docs] “The `cockroach demo` starts a temporary, in-memory CockroachDB cluster of one or more nodes, with or without a preloaded dataset, and opens …”
   • [claimed-docs] “A single-node cluster is appropriate for quick SQL testing or app development.”
   • [claimed-docs] “Instruct Homebrew to install CockroachDB: $ brew install cockroachdb/tap/cockroach”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach version` printed `Build Tag: v26.3.1` keylessly after `brew install cockroachdb/tap/cockroac…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”

   proof ↗⚑ flag

Integrations

1. developerThe database works out of the box with my ORM and framework (Prisma, Drizzle, Django, Rails) with documented guides

   weight 2 · round to CockroachDB
   ClickHouse—none0/10

   No evidence pack items mention Prisma, Drizzle, Django, Rails, or any ORM/framework integration guides for ClickHouse; documentation focuses on CLI tools, cloud setup, MCP, and vector search instead.

   ⚑ flag

   CockroachDB~partialcommunity3/10

   CockroachDB advertises PostgreSQL wire-protocol compatibility, implying general compatibility with Postgres-based ORMs/drivers, but the evidence pack contains no documented, ORM-specific guides (Prisma, Drizzle, Django, Rails) and one community report notes incompatibilities (missing array columns) that break real-world Postgres-client usage. missing for 10: dedicated official guides for Prisma, Drizzle, Django, and Rails integration, and confirmation that ORM-specific features work without workarounds.

   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”
   • [community] “The wire protocol is compatible with Postgres, which allows re-using battle-tested Postgres clients. However it's a non-starter for my use c…”

   proof ↗⚑ flag

Migrations

1. developerImport an existing production database with minimal downtime using a documented migration path

   weight 1 · round to ClickHouse
   ClickHouse~partialclaimed5/10

   ClickHouse documents migration guides from various platforms and ClickPipes connectors for ingesting from Postgres, MySQL, MongoDB, BigQuery, Kafka, etc., which supports moving existing production data in with documented paths (clickhouse-docs-7, clickhouse-docs-28, clickhouse-docs-43). However, none of the evidence explicitly addresses minimal-downtime cutover strategies (e.g., dual-write, CDC replication, rollback plan) for a live production database migration. Missing for 10: explicit minimal-downtime/CDC migration guidance, a documented rollback/verification step, and independent hands-on confirmation that the migration path works with near-zero downtime.

   • [claimed-docs] “Migration guides from various platforms”
   • [claimed-docs] “Create and manage ClickPipes for data ingestion (S3, Kafka, Kinesis, Postgres, MySQL, MongoDB, BigQuery)”
   • [claimed-docs] “By migrating to ClickHouse from BigQuery, you can expect:”
   • [claimed-docs] “Run and manage local Postgres instances * Execute queries against ClickHouse servers * Set up ClickHouse Cloud and create cloud-managed Clic…”

   proof ↗⚑ flag

   CockroachDB~partialclaimed3/10

   The docs index references a dedicated 'Migrate' / migration-overview page (MOLT) suggesting a documented migration path exists, but the evidence pack contains no actual content describing minimal-downtime steps, replication/cutover tooling, or verified success stories. Missing for 10: detailed migration guide content, explanation of minimal-downtime mechanics (e.g., live migration/replication tooling), and independent/hands-on confirmation of a low-downtime cutover.

   • [claimed-docs] “Migrate ](/docs/molt/migration-overview)”

   proof ↗⚑ flag

2. developerShip schema changes safely — online DDL, deploy requests, or branch-and-merge workflows — without locking or breaking production

   weight 3 · round drawn
   ClickHouse—none0/10

   The evidence pack contains no documentation of online/non-locking DDL, deploy-request workflows, or branch-and-merge schema change tooling for ClickHouse; the only tangentially related community notes describe ClickHouse as 'rigid-schema + append-only' and having 'limited DELETE support' rather than confirming safe schema-change tooling. Since schema-migration safety is a legitimate axis for any database product, absence of supporting evidence yields 'none' rather than 'na'.

   • [community] “Clickhouse is rigid-schema + append-only - you can't simply dump semi-structured JSON into it without workarounds; the only integration I've…”
   • [community] “Overall positive experience: 3-node cluster up quickly with official Docker images, ingested billions of rows fast, great compression. Downs…”

   proof ↗⚑ flag

   CockroachDB—none0/10

   The evidence pack contains no mention of online DDL, schema-change safety, migration tooling, or branch/merge workflows for schema changes — topics like backups, changefeeds, multiregion survival, and MCP/CLI tools are covered but schema migration safety is entirely absent. Missing for 10: any documentation or community evidence of online/non-blocking schema changes, migration CLI/tooling, or safe rollout mechanisms for DDL.

   ⚑ flag

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

   weight 2 · round to ClickHouse
   ClickHouse~partialprobed6/10

   ClickHouse's CLI/API (clickhousectl, HTTP interface, SQL) documents broad coverage of Cloud console functions—creating and managing clusters, ClickPipes, Postgres services, and cloud resources—suggesting most UI actions have API/CLI equivalents (clickhouse-docs-16/17/20/28/31/32). However, there is no explicit vendor statement guaranteeing full UI/API parity, and some Cloud-only waitlist features (AI Functions, ClickStack Cloud, PromQL support) appear to be UI/console-first with no confirmed API equivalent yet. Missing for 10: an explicit parity statement, independent verification that all console actions have API equivalents, and clarity on whether newer preview features are API-accessible.

   • [claimed-docs] “With clickhousectl you can: * Install and manage local ClickHouse versions * Launch and manage local ClickHouse servers”
   • [claimed-docs] “Push your local ClickHouse development to cloud”
   • [claimed-docs] “Set up ClickHouse Cloud and create cloud-managed ClickHouse clusters * Create and manage ClickHouse Cloud Postgres services * Manage ClickHo…”
   • [claimed-docs] “Create and manage ClickPipes for data ingestion (S3, Kafka, Kinesis, Postgres, MySQL, MongoDB, BigQuery)”
   • [claimed-docs] “Run and manage local Postgres instances * Execute queries against ClickHouse servers * Set up ClickHouse Cloud and create cloud-managed Clic…”
   • [claimed-docs] “Install and manage local ClickHouse versions * Launch and manage local ClickHouse servers”
   • [claimed-docs] “The X-ClickHouse-Format HTTP request header now explicitly selects the format of the response”
   • [claimed-docs] “The X-ClickHouse-Format HTTP request header now explicitly selects the format of the response: it is an alias for the output_format setting,…”
   • [probe] “PROBE openapi: HTTP 200 at https://clickhouse.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Sign up for private preview access to AI Functions and the AI Inference Service in ClickHouse Cloud. Use AI functions in si”
   • [claimed-docs] “Sign up for private preview access to ClickStack Cloud, a fully turnkey observability platform built on ClickHouse. Send OpenTelemetry logs,…”

   proof ↗⚑ flag

   CockroachDB~partialprobed5/10

   CockroachDB exposes core capabilities via SQL (Postgres wire protocol), a CLI (`ccloud`) for cluster creation/management, and an MCP server for natural-language read/write operations, giving API-level parity for data operations and basic cluster admin. However the evidence pack shows Cloud Console-specific features (cost estimation, resource-usage dashboards, cluster overview page) documented only as UI pages with no confirmed API/CLI equivalent, and no general REST/OpenAPI surface was found (probe for openapi.json returned 404s). Missing for 10: documented Cloud API/REST parity for console-only features like billing/cost estimates and resource monitoring, and confirmation that all UI actions are scriptable via API.

   • [claimed-docs] “The `ccloud` tool is a command-line interface (CLI) tool that allows you to create, manage, and connect to CockroachDB Cloud clusters.”
   • [claimed-docs] “install `ccloud` and use the `ccloud quickstart` command to interactively log in and create a new CockroachDB Serverless cluster.”
   • [claimed-docs] “A user can interact with their clusters using natural language prompts to perform read and write operations such as listing tables, executin…”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the managed MCP server https://cockroachlabs.cloud/mcp returned HTT…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.cockroachlabs.com/openapi.json, https://docs.cockroachlabs.com/swagger.json, https://do…”
   • [claimed-docs] “The monthly cost estimate is calculated using simple extrapolation that assumes your workload during the selected time frame is an accurate …”
   • [claimed-docs] “The **Clusters** page provides a high-level view of your clusters.”

   proof ↗⚑ flag

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

   weight 3 · round to ClickHouse
   ClickHouse~partialclaimed5/10

   ClickHouse supports flexible output formats (e.g., the X-ClickHouse-Format header overriding query FORMAT) and offers 'Export backups to your own cloud account' plus migration guides and clickhouse-local for processing/exporting local and remote files via SQL, all pointing to open-format data portability. However, there is no explicit documentation enumerating full data export tooling (e.g., bulk export to CSV/Parquet/JSON at scale) or a stated commitment to avoiding lock-in, so the story is only partially evidenced. Missing for 10: explicit full-dataset export documentation/tutorial, an open-format export guarantee statement, and independent confirmation that a full migration-out is smooth.

   • [claimed-docs] “The X-ClickHouse-Format HTTP request header now explicitly selects the format of the response”
   • [claimed-docs] “The X-ClickHouse-Format HTTP request header now explicitly selects the format of the response: it is an alias for the output_format setting,…”
   • [claimed-docs] “Export backups to your own cloud account”
   • [claimed-docs] “Migration guides from various platforms”
   • [claimed-docs] “clickhouse-local is an easy-to-use version of ClickHouse that is ideal for developers who need to perform fast processing on local and remot…”
   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment.”

   proof ↗⚑ flag

   CockroachDB!disputedcontradicted4/10

   CockroachDB docs describe full/incremental backup and restore plus PostgreSQL wire-protocol compatibility, which could support exporting data in open, portable formats, but community hands-on reports state the backup/restore feature (needed to actually get data out) was 'locked behind their enterprise version' for non-paying users, directly undercutting a free, no-strings ability to export and leave. Additional community feedback notes real PostgreSQL-compatibility gaps (e.g., no array columns) limiting true open-format portability. Missing for 10: a documented open/standard export format (e.g., SQL dump, CSV) freely available without enterprise licensing, and confirmation that exports are usable outside CockroachDB without vendor lock-in.

   • [claimed-docs] “You can create full or incremental backups of a , , or . Taking regular backups of your data is an operational best practice.”
   • [claimed-docs] “A restore from an arbitrary point in time within the revision history of a backup.”
   • [community] “I love cockroachdb to death, but the key features that prevent me from using it in any real projects I'm doing are the backup/restore featur…”
   • [community] “The wire protocol is compatible with Postgres, which allows re-using battle-tested Postgres clients. However it's a non-starter for my use c…”
   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to ClickHouse
   ClickHouse✓fullprobed7/10

   ClickHouse's own site describes it as a 'fast open-source column-oriented database' and its source is hosted publicly on GitHub, confirming the codebase is openly readable/licensed. Missing for 10: an explicit citation of the license file/terms (e.g., Apache-2.0) rather than just the word 'open-source'.

   • [probe] “PROBE llms.txt: HTTP 200 at https://clickhouse.com/llms.txt # ClickHouse > ClickHouse is a fast open-source column-oriented database manage…”
   • [github] “curl https://clickhouse.com/ | sh”

   proof ↗⚑ flag

   CockroachDB!disputedcontradicted4/10

   CockroachDB's source is published on GitHub (cockroachdb-gh-1), which superficially satisfies 'read the source', but community evidence indicates the licensing model is restrictive rather than a clean open license — users report needing an annual license key even as free users and enterprise features gated behind licensing (cockroachdb-comm-4, cockroachdb-comm-1, cockroachdb-comm-8). This contradicts a straightforward 'open license' claim. Missing for 10: explicit license text/OSI-approval evidence, confirmation that ALL source (not just visible code) is under a recognized open-source license, and resolution of the license-key requirement contradiction.

   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”
   • [community] “I do love Cockroach, but the old licensing model was pretty brutal if you required any enterprise features (ex: incremental backup).”
   • [community] “I don't like the fact that even free users need an annual license key.”
   • [community] “I love cockroachdb to death, but the key features that prevent me from using it in any real projects I'm doing are the backup/restore featur…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to CockroachDB
   ClickHouse✓fullprobed8/10

   ClickHouse is a genuinely open-source, self-hostable database with a public GitHub repo, one-line install script, and docs explicitly instructing users to 'Run ClickHouse on your own machine to build, test, and experiment,' with community accounts confirming real self-hosted production deployments (Docker-based clusters, single-server setups, etc.). Some community reports note self-hosting has operational overhead (resource contention with Keeper, container privilege issues, ops burden vs managed cloud), but these are caveats about ease, not evidence the core product can't be self-hosted. Missing for 10: a first-party self-hosted deployment/ops guide (e.g., Kubernetes operator docs) cited directly and more independent large-scale self-host case studies.

   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment. Quick install gets you a single binary fast”
   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment.”
   • [github] “curl https://clickhouse.com/ | sh”
   • [probe] “PROBE llms.txt: HTTP 200 at https://clickhouse.com/llms.txt # ClickHouse > ClickHouse is a fast open-source column-oriented database manage…”
   • [community] “We're using Clickhouse to power our in-product analytics. It's awesome but would love a managed service - it definitely requires a bit of ma…”
   • [community] “I learned of Clickhouse in an unpleasant way. It is a dependency of Sentry. Installing self-hosted sentry on OpenShift failed because Clickh…”
   • [community] “Overall positive experience: 3-node cluster up quickly with official Docker images, ingested billions of rows fast, great compression. Downs…”

   proof ↗⚑ flag

   CockroachDB✓fullprobed9/10

   CockroachDB core is open-source and can be installed and run entirely locally without any cloud account, verified by runtime probes showing brew install and cockroach demo/single-node clusters running full SQL workloads offline and keylessly. Docs also describe single-node and multi-node self-hosted deployment options. missing for 10: independent third-party confirmation of full multi-node self-hosted cluster beyond demo mode, and clarity on which enterprise features require licensing when self-hosted (per community complaints about backup/CDC being enterprise-gated).

   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach version` printed `Build Tag: v26.3.1` keylessly after `brew install cockroachdb/tap/cockroac…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”
   • [claimed-docs] “A single-node cluster is appropriate for quick SQL testing or app development.”
   • [claimed-docs] “Instruct Homebrew to install CockroachDB: $ brew install cockroachdb/tap/cockroach”
   • [claimed-docs] “The `cockroach demo` starts a temporary, in-memory CockroachDB cluster of one or more nodes, with or without a preloaded dataset, and opens …”

   proof ↗⚑ flag

Cost controls

1. founderSet spend caps or usage alerts so a runaway query or traffic spike cannot produce a surprise bill

   weight 1 · round to ClickHouse
   ClickHouse~partialclaimed6/10

   ClickHouse Cloud's pricing docs explicitly state you can 'Set compute autoscaling limits to prevent runaway queries from unexpected bills' and that compute scales down to zero when idle, directly addressing the founder's concern about surprise bills. However, this is a single vendor pricing-page mention with no detail on configurable spend caps, budget alerts/notifications, or independent/hands-on corroboration of how this works in practice. Missing for 10: documented alerting/notification mechanism for usage thresholds, more detailed spend-cap configuration docs, and independent user confirmation that this prevents runaway bills in practice.

   • [claimed-docs] “Set compute autoscaling limits to prevent runaway queries from unexpected bills”
   • [claimed-docs] “We automatically scale unused resources down to zero so that you don't pay for idle services”
   • [claimed-docs] “We automatically scale up and down compute resources based on your workload”
   • [claimed-docs] “Usage-based pricing: pay only for the compute and storage you use, scaled separately and down to zero when idle.”

   proof ↗⚑ flag

   CockroachDB~partialclaimed3/10

   CockroachDB Cloud provides Request Unit usage monitoring and a monthly cost estimate/extrapolation tool, plus a 'diagnose and optimize resource consumption' guide, giving founders some visibility into spend before a bill arrives. However, there is no evidence of an actual configurable spend cap or proactive usage alert/notification mechanism (e.g., budget thresholds that trigger emails or auto-throttling) — the pack only shows passive dashboards and estimates. Missing for 10: documented spend-cap/budget-limit feature, documented usage-threshold alerting/notifications, and any hands-on confirmation these prevent runaway bills.

   • [claimed-docs] “The monthly cost estimate is calculated using simple extrapolation that assumes your workload during the selected time frame is an accurate …”
   • [claimed-docs] “Diagnose and optimize your resource consumption explains how to find and optimize queries and processes that may be consuming excessive reso…”
   • [claimed-docs] “You can review how many request units your cluster has used on the .”
   • [claimed-docs] “Request Unit consumption scales to zero when your cluster has no activity.”

   proof ↗⚑ flag

Insights

1. platform-engineerSee slow queries, index recommendations, and performance metrics in a built-in insights view

   weight 2 · round to CockroachDB
   ClickHouse~partialclaimed2/10

   The only tangentially relevant evidence is a private-preview waitlist feature (AI notebooks in ClickStack) where an AI agent can surface logs/traces/metrics as charts and summaries, which loosely touches 'performance metrics' but is not a shipped, built-in insights view and never mentions slow-query identification or index recommendations. Everything else in the pack is about CLI tooling, pricing, MCP/AI integrations, and general architecture, none of which address a query-performance insights dashboard. Missing for 10: a GA built-in query-performance/insights view, explicit slow-query surfacing, and any index-recommendation capability with documentation or hands-on evidence.

   • [claimed-docs] “You can describe an issue in plain language, and the AI agent will query logs, traces, and metrics on your behalf — surfacing relevant data,…”
   • [claimed-docs] “Sign up for private preview access to ClickStack Cloud, a fully turnkey observability platform built on ClickHouse. Send OpenTelemetry logs,…”

   proof ↗⚑ flag

   CockroachDB~partialclaimed3/10

   Docs reference a resource-usage page that helps 'find and optimize queries and processes that may be consuming excessive resources' and a Clusters overview page, hinting at some performance monitoring, but there's no evidence of a dedicated built-in insights view naming slow queries or explicit index recommendations. Missing for 10: documentation of a specific 'Insights' or performance-insights UI, evidence of index recommendation output, and independent/hands-on confirmation of these features actually surfacing in the console.

   • [claimed-docs] “Diagnose and optimize your resource consumption explains how to find and optimize queries and processes that may be consuming excessive reso…”
   • [claimed-docs] “The **Clusters** page provides a high-level view of your clusters.”

   proof ↗⚑ flag

Pricing

1. founderA genuinely usable free tier lets me run real prototypes before paying

   weight 2 · round to ClickHouse
   ClickHouse~partialclaimed6/10

   ClickHouse ships as fully free, open-source software that can be installed with a single binary or run via clickhouse-local/chDB for local prototyping without any paid tier (clickhouse-docs-23, clickhouse-docs-27, clickhouse-docs-35), and ClickHouse Cloud's usage-based pricing scales resources down to zero when idle so light prototyping incurs minimal cost (clickhouse-docs-25, clickhouse-docs-41, clickhouse-docs-11). However, there is no explicit documentation of a dedicated 'free tier' with trial credits for Cloud, and no community evidence describing hands-on prototyping experience on a genuinely free plan. Missing for 10: documented free-tier/trial credit details for ClickHouse Cloud, independent user accounts of prototyping for free before paying.

   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment. Quick install gets you a single binary fast”
   • [claimed-docs] “Run ClickHouse on your own machine to build, test, and experiment.”
   • [claimed-docs] “Experience the power of ClickHouse, in-process. With unparalleled performance, reliability, and scalability for any data-intensive applicati…”
   • [claimed-docs] “pay only for the compute and storage you use, scaled separately and down to zero when idle”
   • [claimed-docs] “Usage-based pricing: pay only for the compute and storage you use, scaled separately and down to zero when idle.”
   • [claimed-docs] “We automatically scale unused resources down to zero so that you don't pay for idle services”
   • [claimed-docs] “Start building instantly without having to size and scale your cluster.”

   proof ↗⚑ flag

   CockroachDB!disputedcontradicted5/10

   CockroachDB offers a genuinely free local path (open-source binary, `cockroach demo` running real SQL with no account per probe-rt-1/rt-2) plus a Cloud free trial with $400 credit and serverless scale-to-zero billing (docs-8, docs-25, docs-18), which supports real prototyping. However, community reports concretely contradict full 'free tier usability' — free/core users still need an annual license key, and key features prototypers would want (incremental backup/restore, CDC, follower-reads) are locked behind the paid Enterprise tier, pushing some users back to Postgres (comm-4, comm-8, comm-9). missing for 10: evidence that backup/restore, CDC, and other blocked features are truly available for free, and confirmation the license-key requirement doesn't undermine 'free' framing.

   • [claimed-docs] “This page shows you how to use free trial credits to deploy a CockroachDB cluster on CockroachDB Standard and use sample code to run your fi…”
   • [claimed-docs] “it will be credited with $400 in to get you started”
   • [claimed-docs] “Request Unit consumption scales to zero when your cluster has no activity.”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach version` printed `Build Tag: v26.3.1` keylessly after `brew install cockroachdb/tap/cockroac…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”
   • [community] “I don't like the fact that even free users need an annual license key.”
   • [community] “I love cockroachdb to death, but the key features that prevent me from using it in any real projects I'm doing are the backup/restore featur…”
   • [community] “I stopped using them when they released Follower-Reads as an enterprise feature. I'm back to Postgres for now.”

   proof ↗⚑ flag

2. founderPublished per-unit pricing for compute, storage, and traffic lets me predict my bill before committing

   weight 3 · round to ClickHouse
   ClickHouse~partialclaimed5/10

   ClickHouse's pricing page confirms a usage-based model—pay only for compute and storage used, scaled separately and down to zero when idle—plus autoscaling limits to cap bills, giving founders a general cost structure to reason about. However, the evidence never shows explicit published per-unit rates (e.g., $/vCPU-hour, $/GB-month storage, $/GB traffic) that would let someone precompute a bill precisely. Missing for 10: explicit per-unit dollar rates for compute, storage, and network egress, and any calculator/estimator evidence.

   • [claimed-docs] “We automatically scale unused resources down to zero so that you don't pay for idle services”
   • [claimed-docs] “Set compute autoscaling limits to prevent runaway queries from unexpected bills”
   • [claimed-docs] “pay only for the compute and storage you use, scaled separately and down to zero when idle”
   • [claimed-docs] “We automatically scale up and down compute resources based on your workload”
   • [claimed-docs] “Usage-based pricing: pay only for the compute and storage you use, scaled separately and down to zero when idle.”

   proof ↗⚑ flag

   CockroachDB—none0/10

   Evidence shows CockroachDB Cloud tracks Request Unit usage and provides a monthly cost *estimate* tool, plus free trial credits, but no evidence pack item publishes actual per-unit dollar rates for compute, storage, or traffic that a founder could use to predict a bill in advance. Community comments even highlight surprise/confusion about cost (e.g., being quoted 10x pricier than alternatives), suggesting pricing isn't transparently published upfront.

   • [claimed-docs] “The monthly cost estimate is calculated using simple extrapolation that assumes your workload during the selected time frame is an accurate …”
   • [claimed-docs] “Request Unit consumption scales to zero when your cluster has no activity.”
   • [claimed-docs] “You can review how many request units your cluster has used on the .”
   • [community] “Spanner is cheap in comparison depending on your storage requirements. I've seen CockroachDB quoted as 10x more, and for a product that is h…”

   proof ↗⚑ flag

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

   weight 2 · round to CockroachDB
   ClickHouse—none0/10

   The evidence pack documents ClickHouse Cloud setup, pricing, and CLI tooling but never mentions selecting a deployment region or data residency options for AI-native users. Absence of evidence for this applicable cloud-data-residency capability means it is not shown to deliver.

   ⚑ flag

   CockroachDB~partialcommunity6/10

   CockroachDB's multi-region docs (survival goals, table locality) explicitly let you place data by region, which is what data residency requires — but community reports (comm-2) note that region/residency-only features have at times been gated to enterprise/paid tiers, adding a real caveat that data residency 'is the whole point' but can be restricted depending on license/tier. Missing for 10: independent/hands-on confirmation of granular region pinning in practice, and clarity on which specific product tier includes full multi-region/residency controls.

   • [claimed-docs] “_Survival goal_ dictates how many simultaneous failure(s) a database can survive.”
   • [claimed-docs] “_Table locality_ determines how CockroachDB optimizes access to a table's data.”
   • [claimed-docs] “_Table locality_ determines how CockroachDB optimizes access to a table’s data.”
   • [community] “For me it was the multiple regions. It's like.. with that disabled why are we even here? Data residency is the whole point...”

   proof ↗⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round to CockroachDB
   ClickHouse—none0/10

   The evidence pack contains no vendor documentation on TTL policies, row-level deletion, or data retention controls; the only related community evidence (clickhouse-comm-19) notes 'limited DELETE support,' which does not establish that users can reliably control retention/deletion. Backup export (clickhouse-docs-22) is tangential and does not address retention/deletion policy.

   • [community] “Overall positive experience: 3-node cluster up quickly with official Docker images, ingested billions of rows fast, great compression. Downs…”
   • [claimed-docs] “Export backups to your own cloud account”

   proof ↗⚑ flag

   CockroachDB~partialclaimed4/10

   Evidence shows backup/restore and point-in-time restore capabilities (cockroachdb-docs-6, cockroachdb-docs-15), and standard SQL access via Postgres wire protocol implies DELETE/DROP support (cockroachdb-gh-1), but there is no explicit documentation in this pack of retention policies, row-level TTL, or data deletion/purge controls tailored for AI-native privacy needs. missing for 10: explicit TTL/retention-policy docs, GDPR-style delete-on-request tooling, data lifecycle management guidance.

   • [claimed-docs] “You can create full or incremental backups of a , , or . Taking regular backups of your data is an operational best practice.”
   • [claimed-docs] “A restore from an arbitrary point in time within the revision history of a backup.”
   • [github] “CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers to connect from various languages.”

   proof ↗⚑ flag

Availability

1. platform-engineerAdd read replicas and rely on documented high-availability and failover behavior

   weight 2 · round to CockroachDB
   ClickHouse~partialcommunity3/10

   Evidence only gestures at ClickHouse's replication/coordination layer (Keeper) and community anecdotes about running replicated clusters, but the pack contains no first-party documentation of adding read replicas, replica configuration, or documented failover behavior. missing for 10: dedicated HA/replication setup docs, explicit failover behavior documentation, read-replica configuration guide, quorum/consistency guarantees during failover.

   • [claimed-docs] “ClickHouse Keeper solves the well-known drawbacks of ZooKeeper and makes many additional improvements.”
   • [community] “IMO the only reason to not use ClickHouse is when you have 'small' data (<100GB) or small servers (<64GB RAM). Otherwise it's a better solut…”
   • [community] “Druid got blown away by ClickHouse at eBay: Druid needed 700+ servers versus a 2-region fully replicated ClickHouse system of 40 nodes.”

   proof ↗⚑ flag

   CockroachDB~partialcommunity6/10

   CockroachDB's docs clearly document automatic replication and failover: it 'survives disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention,' with configurable multi-region survival goals and table locality, which functions as its answer to read-replica/HA needs. However, CockroachDB is architecturally a distributed consensus database rather than a primary/read-replica system, and community reports note that follower-reads (the closest analog to 'read replicas' for read scaling) were moved behind an enterprise license, which a platform engineer would need to navigate. Missing for 10: explicit 'read replica' terminology/setup guide, independent verification of failover behavior in production, and clarity on which HA/read-scaling features require paid tiers.

   • [claimed-docs] “survives** disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention”
   • [claimed-docs] “survives disk, machine, rack, and even datacenter failures with minimal latency disruption and no manual intervention; supports strongly-con…”
   • [claimed-docs] “_Survival goal_ dictates how many simultaneous failure(s) a database can survive.”
   • [claimed-docs] “_Table locality_ determines how CockroachDB optimizes access to a table's data.”
   • [community] “I stopped using them when they released Follower-Reads as an enterprise feature. I'm back to Postgres for now.”

   proof ↗⚑ flag

Recovery

1. founderAutomatic backups run on a schedule I can see and configure, and restores are self-serve

   weight 2 · round to ClickHouse
   ClickHouse~partialclaimed3/10

   Evidence only shows ClickHouse Cloud can 'export backups to your own cloud account' (pricing page), implying some backup capability exists, but there is no documentation of a visible/configurable backup schedule or a self-serve restore workflow. missing for 10: schedule visibility/configuration UI, self-serve restore process, docs or hands-on confirmation of restore success.

   • [claimed-docs] “Export backups to your own cloud account”

   proof ↗⚑ flag

   CockroachDB!disputedcontradicted4/10

   Docs describe full/incremental backups and point-in-time restore as available features (cockroachdb-docs-6, cockroachdb-docs-15), but there's no evidence of a visible/configurable backup schedule UI or self-serve founder-facing controls, and community reports concretely contradict self-serve availability: 'backup/restore feature... is currently locked behind their enterprise version' and 'the old licensing model was pretty brutal if you required any enterprise features (ex: incremental backup)' — meaning for a founder on the free/core tier, backups may not be truly self-serve or automatic. Missing for 10: evidence of a schedule visibility/config UI, confirmation that free-tier founders get automatic scheduled backups without enterprise licensing, and independent hands-on confirmation of restore self-service.

   • [claimed-docs] “You can create full or incremental backups of a , , or . Taking regular backups of your data is an operational best practice.”
   • [claimed-docs] “A restore from an arbitrary point in time within the revision history of a backup.”
   • [community] “I love cockroachdb to death, but the key features that prevent me from using it in any real projects I'm doing are the backup/restore featur…”
   • [community] “I do love Cockroach, but the old licensing model was pretty brutal if you required any enterprise features (ex: incremental backup).”

   proof ↗⚑ flag

2. platform-engineerRestore or branch the database to any point in time within the retention window to recover from bad writes

   weight 3 · round to CockroachDB
   ClickHouse—none0/10

   No evidence pack item mentions point-in-time restore, backup/restore mechanisms tied to a retention window, or database branching/cloning; the only tangential reference is 'Export backups to your own cloud account' which does not describe PITR or branching functionality.

   ⚑ flag

   CockroachDB~partialcommunity6/10

   Docs confirm full/incremental backups with revision history enabling restore to an arbitrary point in time within the backup window (docs-6, docs-15), directly matching the 'restore to any point in time' part of the story. However, there is no evidence of a database-branching capability (e.g., cloning a live copy at a timestamp for testing), and community reports note that backup/restore (and other reliability features) are gated behind enterprise licensing, adding a real cost/access caveat (comm-8, comm-1). Missing for 10: evidence of branching/cloning functionality, and confirmation that PITR restore is available outside enterprise tier.

   • [claimed-docs] “You can create full or incremental backups of a , , or . Taking regular backups of your data is an operational best practice.”
   • [claimed-docs] “A restore from an arbitrary point in time within the revision history of a backup.”
   • [community] “I love cockroachdb to death, but the key features that prevent me from using it in any real projects I'm doing are the backup/restore featur…”
   • [community] “I do love Cockroach, but the old licensing model was pretty brutal if you required any enterprise features (ex: incremental backup).”

   proof ↗⚑ flag

Elasticity

1. platform-engineerCompute autoscales up and down with load automatically, without manual resizes or downtime

   weight 2 · round to ClickHouse
   ClickHouse✓fullcommunity7/10

   ClickHouse Cloud docs explicitly state automatic compute autoscaling up and down, including scale-to-zero when idle, and usage-based pricing tied to actual usage rather than manual resizing (clickhouse-docs-40, clickhouse-docs-11, clickhouse-docs-25/41, clickhouse-docs-26). Autoscaling limits can also be configured to control cost (clickhouse-docs-21), directly matching the platform-engineer's need for automatic, downtime-free scaling. missing for 10: independent/hands-on confirmation that Cloud autoscaling avoids downtime in practice, and clarification of applicability to self-managed ClickHouse (community feedback in clickhouse-comm-8/9 notes self-hosted clusters historically lack storage/compute separation and require manual ops).

   • [claimed-docs] “We automatically scale up and down compute resources based on your workload”
   • [claimed-docs] “We automatically scale unused resources down to zero so that you don't pay for idle services”
   • [claimed-docs] “pay only for the compute and storage you use, scaled separately and down to zero when idle”
   • [claimed-docs] “Usage-based pricing: pay only for the compute and storage you use, scaled separately and down to zero when idle.”
   • [claimed-docs] “Start building instantly without having to size and scale your cluster.”
   • [claimed-docs] “Set compute autoscaling limits to prevent runaway queries from unexpected bills”
   • [community] “We just did months of testing on a bunch of dbs for a time-series workload. Whilst we really liked the story and devs behind clickhouse, the…”
   • [community] “We're using Clickhouse to power our in-product analytics. It's awesome but would love a managed service - it definitely requires a bit of ma…”

   proof ↗⚑ flag

   CockroachDB~partialclaimed5/10

   CockroachDB Cloud's Serverless/Basic tier documents automatic request-unit scaling, including scale-to-zero on inactivity, which aligns with autoscaling compute without manual resizing. However, evidence is thin on how it scales up under load or guarantees against downtime, and CockroachDB's core distributed architecture (self-hosted) generally requires manual node provisioning for scaling, so this capability is specific to the managed cloud tier only. missing for 10: detailed scale-up mechanics/limits, evidence of zero-downtime during scale events, independent/hands-on confirmation of autoscaling behavior under real load.

   • [claimed-docs] “Request Unit consumption scales to zero when your cluster has no activity.”
   • [claimed-docs] “You can review how many request units your cluster has used on the .”
   • [claimed-docs] “The monthly cost estimate is calculated using simple extrapolation that assumes your workload during the selected time frame is an accurate …”
   • [claimed-docs] “The **Clusters** page provides a high-level view of your clusters.”

   proof ↗⚑ flag

2. founderIdle databases scale to zero so prototypes and side projects cost nothing while the data stays durable

   weight 3 · round to ClickHouse
   ClickHouse✓fullclaimed8/10

   ClickHouse Cloud explicitly advertises usage-based pricing that scales compute and storage down to zero when idle, so idle prototypes incur no compute cost while data remains stored durably in the cloud service, and users can start instantly without provisioning a cluster. Missing for 10: independent/hands-on confirmation of zero-cost idle behavior and durability guarantees specifically for long-dormant side projects (evidence is vendor-pricing-page only, no community corroboration of this exact scale-to-zero behavior).

   • [claimed-docs] “We automatically scale unused resources down to zero so that you don't pay for idle services”
   • [claimed-docs] “pay only for the compute and storage you use, scaled separately and down to zero when idle”
   • [claimed-docs] “We automatically scale up and down compute resources based on your workload”
   • [claimed-docs] “Usage-based pricing: pay only for the compute and storage you use, scaled separately and down to zero when idle.”
   • [claimed-docs] “Start building instantly without having to size and scale your cluster.”

   proof ↗⚑ flag

   CockroachDB✓fullclaimed7/10

   CockroachDB Cloud's Serverless/Basic tier explicitly scales Request Unit consumption to zero when idle, while data remains durably stored and billed only for storage, directly matching the story of a free-when-idle prototype database. Docs also show a $400 free trial credit and cluster management dashboards for tracking usage, reinforcing the cost-to-zero model for founders/side projects. Missing for 10: independent/hands-on confirmation of actual $0 billing behavior during idle periods, and no community reports validating the scale-to-zero claim in practice (only docs-level evidence).

   • [claimed-docs] “Request Unit consumption scales to zero when your cluster has no activity.”
   • [claimed-docs] “You can review how many request units your cluster has used on the .”
   • [claimed-docs] “This page shows you how to use free trial credits to deploy a CockroachDB cluster on CockroachDB Standard and use sample code to run your fi…”
   • [claimed-docs] “it will be credited with $400 in to get you started”
   • [claimed-docs] “The monthly cost estimate is calculated using simple extrapolation that assumes your workload during the selected time frame is an accurate …”

   proof ↗⚑ flag

Provisioning

1. developerCreate a ready-to-connect database in seconds through the CLI or API without capacity planning

   weight 3 · round to ClickHouse
   ClickHouse✓fullclaimed8/10

   ClickHouse Cloud can be provisioned via the CLI (clickhousectl) without manual capacity planning — docs explicitly state you can 'Set up ClickHouse Cloud and create cloud-managed ClickHouse clusters' from the CLI and 'Start building instantly without having to size and scale your cluster,' backed by usage-based, scale-to-zero autoscaling pricing so no upfront sizing is needed. Missing for 10: independent/hands-on corroboration of actual provisioning speed ('seconds'), and clearer standalone API (non-CLI) creation flow documentation.

   • [claimed-docs] “Set up ClickHouse Cloud and create cloud-managed ClickHouse clusters”
   • [claimed-docs] “Push your local ClickHouse development to cloud”
   • [claimed-docs] “Set up ClickHouse Cloud and create cloud-managed ClickHouse clusters * Create and manage ClickHouse Cloud Postgres services * Manage ClickHo…”
   • [claimed-docs] “Start building instantly without having to size and scale your cluster.”
   • [claimed-docs] “We automatically scale up and down compute resources based on your workload”
   • [claimed-docs] “Usage-based pricing: pay only for the compute and storage you use, scaled separately and down to zero when idle.”
   • [claimed-docs] “We automatically scale unused resources down to zero so that you don't pay for idle services”

   proof ↗⚑ flag

   CockroachDB✓fullprobed7/10

   CockroachDB ships both `cockroach demo` (verified live in a runtime probe to instantly spin up a keyless in-memory cluster with real SQL roundtrip) and the `ccloud quickstart` CLI which interactively creates a CockroachDB Serverless/Basic cluster with request-unit billing that scales to zero, removing the need for capacity planning. Docs also describe a free-trial quickstart flow for going from zero to a connected cluster in seconds via CLI. missing for 10: no runtime probe verifying the cloud `ccloud quickstart` actually provisions a ready-to-connect serverless cluster (only local `cockroach demo` was runtime-tested), and no first-class REST/API path for cluster creation beyond the CLI is evidenced.

   • [claimed-docs] “install `ccloud` and use the `ccloud quickstart` command to interactively log in and create a new CockroachDB Serverless cluster.”
   • [claimed-docs] “Request Unit consumption scales to zero when your cluster has no activity.”
   • [claimed-docs] “The `ccloud` tool is a command-line interface (CLI) tool that allows you to create, manage, and connect to CockroachDB Cloud clusters.”
   • [claimed-docs] “This page shows you how to use free trial credits to deploy a CockroachDB cluster on CockroachDB Standard and use sample code to run your fi…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `cockroach demo --no-example-database --insecure=true -e ...` booted a keyless in-memory single-node cl…”
   • [claimed-docs] “A single-node cluster is appropriate for quick SQL testing or app development.”

   proof ↗⚑ flag