Neon 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 Neon
   Neon✓fullprobed8/10

   Neon documents a full API (openapi.json, Neon API docs), an official CLI (neon-docs-11/34, confirmed runnable keylessly via npx per probe), and an official MCP server (neon-docs-12/33, confirmed live and functioning with OAuth per probe), covering project/database creation, connection string retrieval, and SQL execution — enabling end-to-end agent-driven provisioning without the dashboard. Missing for 10: no hands-on independent third-party account of a full agent-driven create→connect→schema→query workflow end-to-end via MCP/CLI, only first-party docs and isolated runtime probes.

   • [claimed-docs] “Neon CLI”
   • [claimed-docs] “Neon MCP Server overview”
   • [claimed-docs] “Neon API”
   • [probe] “PROBE openapi: HTTP 200 at https://neon.com/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://neon.com/docs/ai/neon-mcp-server”
   • [probe] “official CLI documented at https://neon.com/docs/cli”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official Neon CLI ran keylessly from npm — `npx -y neon@latest --version` printed `4.14.1` with no …”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.neon.tech/mcp returned HTTP 401 w…”

   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 Neon
   Neon~partialprobed6/10

   Neon ships an official MCP Server (docs + live runtime probe confirming the hosted endpoint) and CLI that let agents run SQL/schema operations against Neon Postgres, and the MCP server docs likely expose scoped tools (e.g., run_sql, list_projects, migrations) though the evidence pack doesn't detail a read-only vs destructive tool permission split. missing for 10: explicit documentation of separate read-only vs destructive tool scopes/permissions within the MCP server, independent hands-on confirmation of safe-delegation behavior, and evidence of confirmation/guardrails for destructive actions.

   • [claimed-docs] “Neon MCP Server overview”
   • [claimed-docs] “Neon MCP Server overview - Neon Docs”
   • [probe] “official MCP server documented at https://neon.com/docs/ai/neon-mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.neon.tech/mcp returned HTTP 401 w…”
   • [claimed-docs] “Neon CLI”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official Neon CLI ran keylessly from npm — `npx -y neon@latest --version` printed `4.14.1` with no …”

   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 to Neon
   Neon~partialcommunity6/10

   Neon documents programmatic fleet management via its API/CLI and instant, cheap branching (branch-per-tenant/agent pattern), plus a 'claimable database integration' workflow for spinning up isolated DBs on demand, and scale-to-zero to keep idle databases cheap. However, the pricing page caps at '100 projects' (neon-docs-6), and there is no direct evidence of managing 'thousands' of isolated databases or of per-agent isolation specifically validated at that scale — missing for 10: documented support/pricing for thousands of projects/branches, hands-on evidence of bulk automated provisioning at scale, and confirmation that the 100-project cap doesn't bottleneck a thousands-scale fleet.

   • [claimed-docs] “Branching - Neon Docs”
   • [claimed-docs] “Claimable database integration guide”
   • [claimed-docs] “Neon API”
   • [claimed-docs] “Neon CLI”
   • [claimed-docs] “Scale to Zero”
   • [claimed-docs] “100 projects”
   • [community] “Nice work Neon! I've used it a number of times and am impressed at how quickly databases become available. Leaps and bounds faster than RDS.…”
   • [community] “We use NeonDB in production and I the use of the term "branching" intuitive. We can branch off the main database to test things out, and per…”

   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 Neon
   Neon✓fullprobed9/10

   Neon has a live llms.txt (HTTP 200, structured markdown index) and a machine-readable docs.md summary page, both directly verified via probes, confirming agent-oriented documentation an AI agent can consume. Missing for 10: no independent/community confirmation of an agent actually using llms.txt successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://neon.com/llms.txt # Neon Postgres > Neon is a complete set of cloud backend primitives built around Lak…”
   • [probe] “PROBE docs-md: HTTP 200 at https://neon.com/docs/introduction.md > Full Neon documentation index: https://neon.com/docs/llms.txt > Summary:…”

   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
   Neon✓fullprobed7/10

   Neon ships a documented CLI and REST API usable non-interactively (API-key auth), plus a GitHub Actions integration for branch-per-PR workflows, and a runtime probe confirms the CLI can be invoked keylessly via npx (`npx -y neon@latest --version`), supporting scripted/CI use. Missing for 10: explicit CI/GitHub Actions workflow YAML examples in the evidence pack and a probe showing authenticated (API-key) command execution in a pipeline context.

   • [claimed-docs] “Neon CLI”
   • [claimed-docs] “Neon CLI - Neon Docs”
   • [claimed-docs] “Neon API”
   • [claimed-docs] “Neon API - Neon Docs”
   • [claimed-docs] “The Neon GitHub integration”
   • [claimed-docs] “The Neon GitHub integration - Neon Docs”
   • [probe] “official CLI documented at https://neon.com/docs/cli”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official Neon CLI ran keylessly from npm — `npx -y neon@latest --version` printed `4.14.1` with no …”

   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
   Neon✓fullprobed8/10

   Neon publishes an official MCP server, documented at neon.com/docs/ai/neon-mcp-server, and a runtime probe confirms the hosted endpoint (mcp.neon.tech/mcp) is live and correctly implements the MCP OAuth handshake. Missing for 10: independent/community hands-on reports of an agent successfully using the MCP server in production workflows.

   • [claimed-docs] “Neon MCP Server overview”
   • [claimed-docs] “Neon MCP Server overview - Neon Docs”
   • [probe] “official MCP server documented at https://neon.com/docs/ai/neon-mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.neon.tech/mcp returned HTTP 401 w…”

   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 to Neon
   Neon✓fullprobed9/10

   Neon documents and ships an official CLI (neon/neonctl), confirmed both in docs and a hands-on runtime probe showing `npx neon@latest --version` working keylessly. Missing for 10: independent community commentary specifically evaluating the CLI's AI-native workflows/UX.

   • [claimed-docs] “Neon CLI”
   • [claimed-docs] “Neon CLI - Neon Docs”
   • [probe] “official CLI documented at https://neon.com/docs/cli”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official Neon CLI ran keylessly from npm — `npx -y neon@latest --version` printed `4.14.1` with no …”

   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 Neon
   Neon✓fullprobed9/10

   Neon publishes a documented public REST API (neon-docs-20/38) backed by a live OpenAPI spec (neon-probe-3), plus an llms.txt and docs.md tailored for AI agents (neon-probe-1, neon-probe-2), enabling programmatic control of projects, branches, etc. Missing for 10: independent hands-on verification of API usage beyond probes and richer coverage of API scopes/rate limits.

   • [claimed-docs] “Neon API”
   • [claimed-docs] “Neon API - Neon Docs”
   • [probe] “PROBE openapi: HTTP 200 at https://neon.com/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://neon.com/llms.txt # Neon Postgres > Neon is a complete set of cloud backend primitives built around Lak…”
   • [probe] “PROBE docs-md: HTTP 200 at https://neon.com/docs/introduction.md > Full Neon documentation index: https://neon.com/docs/llms.txt > Summary:…”

   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 to Neon
   Neon~partialprobed4/10

   Neon's hosted MCP server enforces an OAuth-protected-resource flow (401 + WWW-Authenticate + resource_metadata) rather than handing over a full-account API key, and the 'Claimable database integration' guide suggests a mechanism for issuing scoped, per-project credentials to external/agent consumers. However, there is no explicit documentation of configurable least-privilege scopes (e.g., read-only, project-limited API keys) for general API/agent use beyond the MCP OAuth flow. Missing for 10: explicit docs on granular API-key scoping/roles, examples of issuing a restricted key specifically for an agent, and independent confirmation that the MCP OAuth tokens are least-privilege rather than full-account.

   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.neon.tech/mcp returned HTTP 401 w…”
   • [claimed-docs] “Claimable database integration guide”
   • [claimed-docs] “Neon API”
   • [claimed-docs] “Neon MCP Server overview - Neon Docs”

   proof ↗⚑ 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 Neon
   Neon~partialprobed6/10

   Neon documents an official serverless driver (JS/TS) and a full REST API with a published OpenAPI spec, plus a CLI and MCP server for programmatic/agentic access, giving AI-native builders official tooling to integrate against. Missing for 10: multi-language official SDKs beyond the JS serverless driver, and independent/hands-on validation of SDK ergonomics or completeness.

   • [claimed-docs] “Neon serverless driver”
   • [claimed-docs] “Neon API”
   • [probe] “PROBE openapi: HTTP 200 at https://neon.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Neon CLI”
   • [claimed-docs] “Neon MCP Server overview”

   proof ↗⚑ 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
   Neon—none0/10

   No evidence of a webhooks subscription feature for Neon events (e.g., project/branch/compute state changes); Neon's API, CLI, and MCP server are documented but no webhook/event-subscription mechanism appears anywhere in the pack.

   ⚑ 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 to CockroachDB
   Neon—none0/10

   Evidence shows Neon provides AI infrastructure (AI Gateway, pgvector, MCP server for agent access) but nothing about Neon itself analyzing a user's data and surfacing AI-generated insights or suggestions (e.g., query optimization tips, anomaly detection, usage recommendations). These are tools for building AI apps on top of Neon, not an in-product insight/suggestion feature.

   • [claimed-docs] “AI Gateway. All models, one API, one bill. Powered by Databricks.”
   • [claimed-docs] “The pgvector extension”
   • [claimed-docs] “Neon MCP Server overview - Neon Docs”

   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 drawn
   Neon—none0/10

   Neon's evidence covers database infrastructure (branching, autoscaling, functions, MCP server, CLI) but nothing describes a scheduling/trigger/automation mechanism that lets an AI-native user configure work to run autonomously in the background without a live agent invoking it. Neon Functions and the MCP server enable agent-driven interactions, but no cron/trigger/webhook automation feature is documented.

   • [claimed-docs] “Functions. Long-running, without timeouts, and closer to your database.”
   • [claimed-docs] “Neon MCP Server overview”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.neon.tech/mcp returned HTTP 401 w…”

   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 drawn
   Neon—none0/10

   Evidence shows Neon offers an AI Gateway for routing to external AI models and an MCP server so external AI agents can control Neon, but there is no evidence of a built-in AI assistant inside the Neon console/product itself that users can delegate tasks to.

   • [claimed-docs] “AI Gateway. All models, one API, one bill. Powered by Databricks.”
   • [claimed-docs] “AI Gateway. All models, one API, one bill.”
   • [claimed-docs] “Neon MCP Server overview”
   • [claimed-docs] “Neon MCP Server overview - Neon Docs”

   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
   Neon~partialprobed6/10

   Neon ships an official MCP server (hosted, live per runtime probe with OAuth flow) and a CLI, both of which let AI agents/natural-language tools operate the database (create branches, run queries, manage projects) via MCP tool calls rather than requiring raw SQL/API calls. This supports agentic/natural-language operation but the evidence doesn't show a first-party conversational NL interface (e.g., a chat UI translating plain English to SQL) beyond MCP-mediated tool use. missing for 10: no evidence of a native NL-to-SQL/chat interface distinct from MCP tool-calling, no independent/hands-on account of an agent successfully operating Neon end-to-end via natural language.

   • [claimed-docs] “Neon MCP Server overview - Neon Docs”
   • [claimed-docs] “Neon CLI - Neon Docs”
   • [probe] “official MCP server documented at https://neon.com/docs/ai/neon-mcp-server”
   • [probe] “official CLI documented at https://neon.com/docs/cli”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official Neon CLI ran keylessly from npm — `npx -y neon@latest --version` printed `4.14.1` with no …”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.neon.tech/mcp returned HTTP 401 w…”

   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
   Neon—none0/10

   Neon has an API reference and OpenAPI spec (neon-docs-20/38, neon-probe-3), but no evidence describes an interactive, runnable-example experience (e.g., in-browser 'try it' consoles) for that API reference.

   • [claimed-docs] “Neon API”
   • [claimed-docs] “Neon API - Neon Docs”
   • [probe] “PROBE openapi: HTTP 200 at https://neon.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 Neon
   Neon✓fullprobed9/10

   Neon publishes a live OpenAPI spec at https://neon.com/openapi.json (confirmed by probe returning HTTP 200 with an 'openapi' key), plus a documented reference API page, satisfying a machine-readable API spec download for AI-native tooling. Missing for 10: no independent/community corroboration of third-party consumption of the spec.

   • [probe] “PROBE openapi: HTTP 200 at https://neon.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Neon API”
   • [claimed-docs] “Neon API - Neon Docs”

   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 drawn
   Neon✓fullcommunity8/10

   Neon's branching feature (instant copy-on-write branches of a Postgres database) is explicitly designed to let users spin up isolated environments to test changes without touching production data, and community users corroborate this exact workflow ('We can branch off the main database to test things out, and periodically reset the branch to its parent'). Docs on branching, instant restore, and claimable database integration further support safe, disposable test environments. missing for 10: independent hands-on verification of data isolation guarantees at scale, and explicit documentation of a dedicated 'sandbox' mode distinct from branching terminology.

   • [claimed-docs] “Branching - Neon Docs”
   • [community] “We use NeonDB in production and I the use of the term "branching" intuitive. We can branch off the main database to test things out, and per…”
   • [claimed-docs] “Instant restore”
   • [claimed-docs] “Claimable database integration guide”
   • [claimed-docs] “Lakebase Postgres. Serverless database that scales and branches with your app.”

   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
   Neon—none0/10

   Evidence shows Neon has a documented REST API and OpenAPI spec (neon-docs-20, neon-probe-3), but nothing in the pack mentions API versioning scheme or a documented deprecation policy for breaking changes.

   • [claimed-docs] “Neon API”
   • [claimed-docs] “Neon API - Neon Docs”
   • [probe] “PROBE openapi: HTTP 200 at https://neon.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 CockroachDB
   Neon—none0/10

   Neon offers an API, CLI, and MCP server (neon-docs-20/34/33) that could in principle be scripted for bulk actions, but no evidence pack item documents batch/bulk endpoints, bulk branch/project creation, or any explicit bulk-operation capability across many items at once.

   ⚑ 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 CockroachDB
   Neon—none0/10

   No evidence of Neon supporting event-driven rule/action automation (e.g., webhooks, triggers-as-a-service, or rule engines) is present; the evidence pack covers branching, scaling, Functions, storage, and MCP/CLI tooling but nothing about defining automatic rule-based triggers on events.

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

   No evidence that Neon offers scheduled/recurring job or workflow capabilities (e.g., pg_cron support, cron-like triggers, or workflow scheduling); the evidence pack covers branching, scaling, storage, and connectivity but nothing about job scheduling.

   ⚑ 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
   Neon—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 to Neon
   Neon✓fullcommunity9/10

   Neon's docs explicitly document 'Instant restore' for branches (branch-restore) and 'Branching' overview, and a community user confirms real-world usage: 'we branch off the main database to test things out, and periodically reset the branch to its parent.' This directly matches the story of resetting/restoring a branch without dump-based rebuilds. Missing for 10: no first-party CLI/API example walkthrough of the exact reset-to-parent command cited directly in the pack.

   • [claimed-docs] “Instant restore”
   • [claimed-docs] “Instant restore - Neon Docs”
   • [claimed-docs] “Branching - Neon Docs”
   • [community] “We use NeonDB in production and I the use of the term "branching" intuitive. We can branch off the main database to test things out, and per…”

   proof ↗⚑ 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 to Neon
   Neon✓fullcommunity8/10

   Neon's branching is a first-class feature with docs, API, CLI, and GitHub integration explicitly designed for automated branch creation/teardown per PR (Neon API, Neon CLI, GitHub integration docs), and community evidence confirms real-world use of branching to test changes and reset to parent. Missing for 10: a concrete third-party CI/CD platform (e.g., Vercel preview or GitHub Actions) walkthrough or hands-on confirmation of automated PR-triggered teardown beyond docs/API existence.

   • [claimed-docs] “Branching - Neon Docs”
   • [claimed-docs] “The Neon GitHub integration”
   • [claimed-docs] “Neon API”
   • [claimed-docs] “Neon CLI”
   • [community] “We use NeonDB in production and I the use of the term "branching" intuitive. We can branch off the main database to test things out, and per…”

   proof ↗⚑ 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 to Neon
   Neon✓fullcommunity9/10

   Neon's core product feature is instant copy-on-write branching of Postgres databases including schema and data, documented explicitly in the branching docs, and corroborated by independent community usage describing branching off main to test and reset ('We can branch off the main database to test things out, and periodically reset the branch to its parent'). Instant restore and branch-based workflows are further documented, reinforcing the copy-on-write branch model used for dev/test against production-shaped data. Missing for 10: deeper hands-on verification of 'production-shaped data' fidelity at scale beyond a single community quote.

   • [claimed-docs] “Branching - Neon Docs”
   • [claimed-docs] “Instant restore”
   • [claimed-docs] “Lakebase Postgres. Serverless database that scales and branches with your app.”
   • [community] “We use NeonDB in production and I the use of the term "branching" intuitive. We can branch off the main database to test things out, and per…”

   proof ↗⚑ 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 to Neon
   Neon✓fullclaimed9/10

   Neon documents an official serverless driver ([neon-docs-14]/[neon-docs-31]) purpose-built for querying over HTTP or WebSockets, designed for serverless/edge environments with short-lived connections, and complements it with documented connection pooling ([neon-docs-13]/[neon-docs-30]) and scale-to-zero behavior. missing for 10: independent hands-on benchmarking or third-party validation of the HTTP/WebSocket driver specifically (community evidence covers general Neon experience but not this driver directly).

   • [claimed-docs] “Neon serverless driver”
   • [claimed-docs] “Neon serverless driver - Neon Docs”
   • [claimed-docs] “Connection pooling”
   • [claimed-docs] “Connection pooling - Neon Docs”
   • [claimed-docs] “Scale to Zero”

   proof ↗⚑ 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
   Neon~partialcommunity3/10

   Neon documents a 'Read Replicas' feature (neon-docs-16/28) which could in principle be used to place read copies closer to users, but the evidence pack contains no documentation of explicit region selection, multi-region deployment, or replica placement guidance, and community comments raise concerns about storage/compute separation adding latency (neon-comm-2, neon-comm-3). missing for 10: explicit docs on choosing/creating replicas in specific regions, guidance on multi-region latency optimization, and independent confirmation that cross-region replicas actually reduce latency.

   • [claimed-docs] “Neon Read Replicas”
   • [claimed-docs] “Neon Read Replicas - Neon Docs”
   • [community] “"We separated storage and compute" No. just no. Compute where the data lives, else you incur traffic cost and latency. A lesson learned in l…”
   • [community] “I am trying to understand how it works... the disk-backed storage here uses S3 which would introduce some severe latency... why would I run …”

   proof ↗⚑ 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 to Neon
   Neon✓fullclaimed8/10

   Neon documents a built-in connection pooler (PgBouncer-based) enabled via a dedicated pooled connection endpoint, described in official docs as a first-class feature (neon-docs-13/30), eliminating the need to operate a separate pgbouncer/proxy. missing for 10: independent hands-on benchmarks proving thousands-of-connections scale, and no community corroboration specifically about pooler behavior under load (community comments focus on branching/pricing/storage, not pooling).

   • [claimed-docs] “Connection pooling”
   • [claimed-docs] “Connection pooling - Neon Docs”

   proof ↗⚑ 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 to Neon
   Neon✓fullclaimed8/10

   Neon documents native pgvector extension support, allowing embeddings storage and vector similarity search directly in Postgres without a separate vector DB (neon-docs-15/32). This is first-party docs only, without independent hands-on benchmarks of vector search performance. Missing for 10: independent/community validation of pgvector performance at scale on Neon, and details on index types (HNSW/IVFFlat) support depth.

   • [claimed-docs] “The pgvector extension”
   • [claimed-docs] “The pgvector extension - Neon Docs”

   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 drawn
   Neon—none0/10

   Neon is positioned as serverless Postgres with branching, autoscaling, read replicas, and connection pooling, but the evidence pack contains no mention of columnar storage, OLAP-optimized query engine, materialized views, or any benchmark showing fast large-table aggregation performance suitable for dashboards. Community commentary even raises concerns about storage/compute separation introducing latency, but this doesn't rise to a concrete contradiction of a specific claim—there's simply no claim to contradict.

   • [claimed-docs] “Neon Read Replicas”
   • [claimed-docs] “Autoscaling”
   • [claimed-docs] “Connection pooling”
   • [community] “"We separated storage and compute" No. just no. Compute where the data lives, else you incur traffic cost and latency. A lesson learned in l…”
   • [community] “I am trying to understand how it works... the disk-backed storage here uses S3 which would introduce some severe latency... why would I run …”

   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 Neon
   Neon~partialcommunity6/10

   Neon is real Postgres (not a lookalike), evidenced by connecting via standard psql/dbeaver clients, support for extensions like pgvector, and community confirmation it's genuinely Postgres under the hood (used by Vercel). However, Neon only supports Postgres — no MySQL or SQLite dialect compatibility is offered or claimed, and some architectural differences (storage/compute separation, S3-backed storage) draw community pushback on whether behavior fully matches traditional Postgres performance expectations. missing for 10: MySQL/SQLite dialect support, exhaustive extension-compatibility list, independent verification that all Postgres extensions/behaviors work identically at scale.

   • [github] “connect to it with your preferred Postgres client (psql, dbeaver, etc) or use the online SQL Editor”
   • [github] “Neon is an open-source serverless Postgres database platform. It separates storage and compute”
   • [claimed-docs] “The pgvector extension”
   • [community] “I tried using supabase to back a vercel project. It was far too slow so we switched back to postgresql included with vercel. Turns out that …”
   • [community] “"We separated storage and compute" No. just no. Compute where the data lives, else you incur traffic cost and latency. A lesson learned in l…”
   • [community] “I am trying to understand how it works... the disk-backed storage here uses S3 which would introduce some severe latency... why would I run …”

   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
   Neon✓fullprobed8/10

   Neon CLI is documented and runtime-verified to run keylessly, and Neon's docs describe CLI-based project/branch creation, connection strings, and SQL/psql-based inspection (neon-docs-11/34, neon-probe-5, neon-probe-rt-1, neon-gh-1). This covers create/connect/shell/inspect without the dashboard, though evidence doesn't show a single first-party walkthrough of the full daily loop end-to-end or independent hands-on review of CLI ergonomics. missing for 10: a documented end-to-end CLI workflow example combining create+connect+shell+inspect in one place, and independent/community validation of CLI usability.

   • [claimed-docs] “Neon CLI”
   • [claimed-docs] “Neon CLI - Neon Docs”
   • [probe] “official CLI documented at https://neon.com/docs/cli”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official Neon CLI ran keylessly from npm — `npx -y neon@latest --version` printed `4.14.1` with no …”
   • [github] “connect to it with your preferred Postgres client (psql, dbeaver, etc) or use the online SQL Editor”

   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 to CockroachDB
   Neon~partialclaimed6/10

   GitHub docs explicitly state Neon can be compiled and run locally/on a workstation for small experiments and to test code changes, supporting offline/CI use without cloud dependency, and the project is open-source so no account is inherently required. However, the flagship 'Neon Local' feature is documented as a local proxy that typically still connects to a cloud-hosted Neon project/branch rather than a fully standalone keyless engine, creating ambiguity about true offline independence. Missing for 10: independent/hands-on confirmation that a locally compiled Neon instance works fully offline in CI without any cloud account, and clarification that Neon Local is not itself cloud-dependent.

   • [github] “Neon can be run on a workstation for small experiments and to test code changes”
   • [github] “Alternatively, compile and run the project locally.”
   • [github] “Alternatively, compile and run the project locally (#running-local-installation).”
   • [github] “Neon is an open-source serverless Postgres database platform. It separates storage and compute”
   • [claimed-docs] “Neon Local”
   • [claimed-docs] “Neon Local - Neon Docs”

   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
   Neon—none0/10

   The evidence pack documents general Postgres compatibility features (connection pooling, serverless driver, branching, CLI, API) but contains no citation mentioning Prisma, Drizzle, Django, or Rails integration guides specifically. Without documented framework/ORM-specific guides in the evidence, this axis cannot be credited as delivered.

   ⚑ 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 CockroachDB
   Neon—none0/10

   The evidence pack covers Neon's branching, autoscaling, CLI, MCP server, and other features, but contains no documentation or reference to a migration path for importing an existing production database (e.g., pg_dump/restore, logical replication, minimal-downtime cutover guide). No citation addresses this specific story.

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

   Neon's branching (copy-on-write branches, instant restore) supports a branch-based workflow for testing schema changes before applying to production, and community confirms this pattern works well in practice (branch off main, test, reset). However there is no documented 'merge back' or schema-diff/merge tooling, no deploy-request workflow, and no explicit online-DDL/zero-downtime-migration guidance in the evidence. Missing for 10: explicit branch-merge or schema-diff tooling, deploy-request/approval workflow, documented online DDL or lock-free migration guarantees, and independent verification of safe production rollout beyond generic branching praise.

   • [claimed-docs] “Branching - Neon Docs”
   • [claimed-docs] “Instant restore”
   • [claimed-docs] “Instant restore - Neon Docs”
   • [community] “We use NeonDB in production and I the use of the term "branching" intuitive. We can branch off the main database to test things out, and per…”

   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 Neon
   Neon✓fullprobed8/10

   Neon publishes a full public API (openapi.json), an official CLI wrapping it, and a documented MCP server, covering project/branch/database management, auth, and most operations available in the UI (branching, autoscaling, connection pooling, restore, etc.). missing for 10: no explicit independent confirmation that every single UI action (e.g. billing/team management nuances) maps 1:1 to API endpoints, and no third-party audit of API completeness vs UI.

   • [claimed-docs] “Neon API”
   • [claimed-docs] “Neon API - Neon Docs”
   • [probe] “PROBE openapi: HTTP 200 at https://neon.com/openapi.json — contains "openapi" key”
   • [claimed-docs] “Neon CLI”
   • [claimed-docs] “Neon CLI - Neon Docs”
   • [probe] “official CLI documented at https://neon.com/docs/cli”
   • [claimed-docs] “Neon MCP Server overview”
   • [claimed-docs] “Neon MCP Server overview - Neon Docs”
   • [probe] “official MCP server documented at https://neon.com/docs/ai/neon-mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-06): the official Neon CLI ran keylessly from npm — `npx -y neon@latest --version` printed `4.14.1` with no …”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.neon.tech/mcp returned HTTP 401 w…”

   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 Neon
   Neon~partialclaimed5/10

   Neon is standard, open-source Postgres and can be accessed with any Postgres client (psql, dbeaver) or the Neon CLI/API, which implies standard export tooling like pg_dump works, and the open-source codebase (neon-gh-5/6) means self-hosting/leaving is possible in principle. However, there is no explicit vendor documentation of a one-click 'export all data' or full account/data-export feature, or specific pg_dump/backup-portability guide. Missing for 10: an explicit data-export/portability doc, evidence of exporting non-relational assets (e.g. object storage, auth records) in open formats, and confirmation of a smooth full account migration path.

   • [github] “connect to it with your preferred Postgres client (psql, dbeaver, etc) or use the online SQL Editor”
   • [github] “Neon is an open-source serverless Postgres database platform. It separates storage and compute”
   • [github] “Neon is an open-source serverless Postgres database platform.”
   • [claimed-docs] “Object Storage. S3-compatible blob storage that branches with your projects.”
   • [claimed-docs] “Managed Better Auth. Authentication with users and sessions stored in Postgres.”

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

   The official GitHub repo is explicitly described as 'an open-source serverless Postgres database platform,' and instructions exist for compiling/running it locally, confirming the source is publicly available under an open license. Missing for 10: explicit citation of the specific license name (e.g., Apache-2.0) and independent confirmation of license terms beyond the repo's self-description.

   • [github] “Neon is an open-source serverless Postgres database platform. It separates storage and compute”
   • [github] “Neon is an open-source serverless Postgres database platform.”
   • [github] “Alternatively, compile and run the project locally.”
   • [github] “Alternatively, compile and run the project locally (#running-local-installation).”
   • [github] “Neon can be run on a workstation for small experiments and to test code changes”

   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
   Neon~partialcommunity6/10

   Neon's GitHub repo is explicitly open-source and documents that you can compile and run it locally, and that 'Neon can be run on a workstation for small experiments and to test code changes,' with a community comment confirming some users self-host the storage/compute architecture in production. However, the official docs and framing position self-hosting as workstation-scale testing rather than a fully supported production self-host path (no HA/scaling guide for self-hosted deployments). Missing for 10: production-grade self-hosting documentation, official support/guides for scaling a self-hosted cluster, and independent confirmation of large-scale self-hosted production use.

   • [github] “Neon can be run on a workstation for small experiments and to test code changes”
   • [github] “Alternatively, compile and run the project locally.”
   • [github] “Neon is an open-source serverless Postgres database platform. It separates storage and compute”
   • [github] “Alternatively, compile and run the project locally (#running-local-installation).”
   • [community] “For us that self-host, the architecture of building cold storage on top of Object Storage and warm storage on top of NVMEs is unbeatable. It…”

   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 CockroachDB
   Neon—none0/10

   No evidence pack item mentions spend caps, budget alerts, usage-based billing alerts, or any mechanism to cap or notify on cost overruns; pricing complaints in community citations discuss cost surprises but do not show Neon offering a cap/alert feature. This is a fair axis for a usage-billed cloud database service, so absence of evidence yields none rather than na.

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

   No evidence in the pack references a built-in insights view, slow query logging, index recommendations, or performance dashboards; documentation focuses on branching, scaling, connection pooling, and integrations instead. Neon does offer monitoring features per general knowledge, but this evidence pack contains no citation supporting the specific story.

   ⚑ 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 Neon
   Neon✓fullcommunity8/10

   Neon's pricing docs explicitly promote a free tier with 'no time limits and no credit card required' and 100 projects allowed, and community comments corroborate quick provisioning for hobby/prototype use ('game-changer' for pay-per-call relational DB, fast to spin up databases). Missing for 10: independent evidence specifically confirming free-tier limits are sufficient for a 'real prototype' (e.g., storage/compute caps) and any hands-on account of hitting free-tier ceilings.

   • [claimed-docs] “Build and learn free with no time limits and no credit card required.”
   • [claimed-docs] “100 projects”
   • [community] “Having a relational database where you're charged purely for the calls you make is a game-changer. All of the relational databases I looked …”
   • [community] “Nice work Neon! I've used it a number of times and am impressed at how quickly databases become available. Leaps and bounds faster than RDS.…”

   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 Neon
   Neon!disputedcontradicted4/10

   Neon does publish a pricing page (docs-6,7,24) referencing tiers, projects, and team members, but the evidence pack contains no published per-unit rates for compute/storage/traffic that would let a founder predict a bill in advance. Community feedback directly contradicts predictability: users note pricing is based on 'CPU' that is 'never defined' (neon-comm-13), report surprise jumps to $69+/month after a pricing change (neon-comm-8), and question egress cost predictability for non-AWS clouds (neon-comm-12). Missing for 10: explicit per-unit $/compute-hour, $/GB-storage, $/GB-egress figures and independent confirmation that bills match expectations.

   • [claimed-docs] “100 projects”
   • [claimed-docs] “Unlimited team members”
   • [claimed-docs] “Build and learn free with no time limits and no credit card required.”
   • [community] “Is 5 a reference to how you naked the prices so Neon doesn't work for light-workload, moderate storage databases anymore? $69+ a month for a…”
   • [community] “Is it feasible to use Neon connecting from smaller clouds, such as Hetzner, DO, Linode, etc?... For small workloads egress cost doesn't matt…”
   • [community] “What is a CPU? If it's AWS hosted for example it can range from a t2 (low end) to c7a (high end) and have huge performance impacts... It's w…”

   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
   Neon—none0/10

   No evidence pack items mention region selection, data residency, or geographic deployment options for Neon projects; nothing addresses where data is physically stored.

   ⚑ 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 userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Neon—none0/10

   The evidence pack contains no mention of any AI-training opt-out, data-use policy for model training, or privacy controls governing whether customer data is used to train AI models; all evidence covers unrelated product features (branching, autoscaling, MCP server, CLI, pricing). Since Neon stores and processes user data and could plausibly offer such a privacy guarantee, the axis applies but is unaddressed. missing for 10: any documentation of an AI-training opt-out policy, data-processing/privacy terms addressing model training, or statements that customer data is excluded from AI training.

   ⚑ flag

   CockroachDB—none0/10

   The evidence pack contains no mention of any AI-model-training opt-out, data-usage policy, or privacy commitment regarding customer data being used to train AI models. CockroachDB Cloud does handle customer data and has AI-adjacent features (natural-language MCP interface), so the axis is a fair question for the product, but no documentation or community evidence addresses this specific privacy control. missing for 10: any documented policy on AI-training data usage, opt-out mechanism, or explicit privacy statement about model training.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to CockroachDB
   Neon—none0/10

   The evidence pack shows Neon's general Postgres/branching/API/CLI capabilities but contains no documentation on data retention policies, deletion guarantees, or privacy-oriented data lifecycle controls (e.g., project/branch purge SLAs, GDPR-style deletion assurances). Missing for 10: any retention-policy docs, explicit deletion/purge guarantees, or compliance statements addressing data retention.

   ⚑ 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

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

   weight 2 · round drawn
   Neon—none0/10

   No evidence in the pack addresses telemetry collection or an opt-out mechanism for Neon's CLI, MCP server, or platform usage tracking; privacy/telemetry policy is simply not documented here.

   ⚑ flag

   CockroachDB—none0/10

   No evidence in the pack shows a documented telemetry opt-out mechanism; instead, community feedback explicitly states the telemetry is mandatory ('the only thing I don't like is the mandatory telemetry'), indicating no user-facing opt-out exists.

   • [community] “The only thing I don't like is the mandatory telemetry.”

   proof ↗⚑ flag

Availability

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

   weight 2 · round to CockroachDB
   Neon~partialclaimed5/10

   Neon documents Read Replicas as a first-class feature (neon-docs-16/28), and its storage/compute separation architecture is described (neon-gh-5/6), but the evidence pack contains no explicit documentation of automated failover behavior or HA guarantees tied to replicas. Missing for 10: documented failover/HA SLAs, promotion-of-replica-to-primary process, and independent confirmation of failover behavior in production.

   • [claimed-docs] “Neon Read Replicas”
   • [claimed-docs] “Neon Read Replicas - Neon Docs”
   • [github] “Neon is an open-source serverless Postgres database platform. It separates storage and compute”
   • [github] “Neon is an open-source serverless Postgres database platform.”

   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 Neon
   Neon~partialclaimed5/10

   Neon documents self-serve 'Instant restore' via branch/restore, which lets founders roll back a database without vendor support, satisfying the restore half of the story. However, there is no evidence of a traditional scheduled-backup mechanism with a visible/configurable schedule (Neon's architecture is continuous storage/branching rather than periodic backup jobs), so the 'schedule I can see and configure' part is unaddressed. Missing for 10: documentation of backup schedule visibility/configuration, retention policy controls, or backup frequency settings.

   • [claimed-docs] “Instant restore”
   • [claimed-docs] “Instant restore - Neon Docs”
   • [claimed-docs] “Branching - Neon Docs”

   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 Neon
   Neon✓fullcommunity8/10

   Neon documents Instant restore (point-in-time recovery within retention window) and Branching, and community evidence corroborates branch-and-reset workflows in production use. This directly matches the story of restoring/branching to a point in time to recover from bad writes. missing for 10: independent hands-on verification of exact restore-to-timestamp mechanics and retention-window limits beyond docs, and confirmation of behavior at scale/edge cases.

   • [claimed-docs] “Instant restore”
   • [claimed-docs] “Instant restore - Neon Docs”
   • [claimed-docs] “Branching - Neon Docs”
   • [community] “We use NeonDB in production and I the use of the term "branching" intuitive. We can branch off the main database to test things out, and per…”

   proof ↗⚑ 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 Neon
   Neon✓fullcommunity8/10

   Neon's docs explicitly document Autoscaling (compute scales with load automatically) and Scale to Zero (idle compute suspends), both core to serverless compute management without manual resizing, and community evidence corroborates fast/serverless provisioning behavior. Missing for 10: independent hands-on benchmarks proving no downtime during autoscale transitions and details on scaling limits/latency during scale-up events.

   • [claimed-docs] “Scale to Zero”
   • [claimed-docs] “Autoscaling”
   • [claimed-docs] “Autoscaling - Neon Docs”
   • [claimed-docs] “Scale to Zero - Neon Docs”
   • [community] “Nice work Neon! I've used it a number of times and am impressed at how quickly databases become available. Leaps and bounds faster than RDS.…”
   • [community] “Having a relational database where you're charged purely for the calls you make is a game-changer. All of the relational databases I looked …”

   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 Neon
   Neon✓fullcommunity9/10

   Neon's docs explicitly document Scale to Zero (idle compute suspends) alongside durable storage separation (compute/storage split), and free tier/pricing pages confirm no-cost prototyping with no credit card required; community comments corroborate pay-per-use idle cost savings for hobby projects. missing for 10: independent verification of data durability specifically across scale-to-zero cycles (only vendor docs, no third-party confirmation of zero data loss).

   • [claimed-docs] “Scale to Zero”
   • [claimed-docs] “Scale to Zero - Neon Docs”
   • [claimed-docs] “Build and learn free with no time limits and no credit card required.”
   • [github] “Neon is an open-source serverless Postgres database platform. It separates storage and compute”
   • [community] “Having a relational database where you're charged purely for the calls you make is a game-changer. All of the relational databases I looked …”

   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 Neon
   Neon✓fullprobed9/10

   Neon provides an official CLI and REST API (neon-docs-11, neon-docs-20, neon-probe-5, neon-probe-3), a free tier with instant serverless Postgres provisioning (neon-gh-2), and community testimony that databases become available very quickly without infra planning (neon-comm-6). Autoscaling and scale-to-zero eliminate manual capacity planning (neon-docs-9, neon-docs-10, neon-docs-26). Missing for 10: no independent benchmark timing the exact provisioning speed in seconds via CLI/API.

   • [claimed-docs] “Neon CLI”
   • [claimed-docs] “Neon API”
   • [github] “Try the Neon Free Tier to create a serverless Postgres instance.”
   • [community] “Nice work Neon! I've used it a number of times and am impressed at how quickly databases become available. Leaps and bounds faster than RDS.…”
   • [claimed-docs] “Scale to Zero”
   • [claimed-docs] “Autoscaling”
   • [probe] “official CLI documented at https://neon.com/docs/cli”
   • [probe] “PROBE openapi: HTTP 200 at https://neon.com/openapi.json — contains "openapi" key”

   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