PlanetScale 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 drawn
   PlanetScale~partialprobed7/10

   PlanetScale ships a CLI (pscale) explicitly designed for agent workflows—non-interactive `pscale sql`, a baked-in `--skill` guide, and `--format json` output for agents—plus a hosted MCP server for Claude/Cursor that exposes Insights and query execution, and docs on branching/schema deploy requests that agents could drive without the dashboard. However, the evidence never shows an explicit 'create database' or 'fetch connection string' CLI/API command, and the MCP server's insights-only variant explicitly excludes query execution, leaving a gap in the fully automated create→connect→schema→query chain. Missing for 10: explicit documented commands/API calls for database creation and connection-string retrieval, and confirmation that the primary MCP variant (not just insights-only) supports full query execution end-to-end.

   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Open a secure MySQL or PostgreSQL shell instance”
   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”
   • [claimed-docs] “Database branching, coupled with deploy requests, allows you to deploy non-blocking schema changes to your production database with zero dow…”
   • [claimed-docs] “Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights”
   • [probe] “official MCP server documented at https://planetscale.com/docs/mcp-server”
   • [probe] “official CLI documented at https://planetscale.com/docs/cli”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --version` printed `pscale version 0.329.0` keylessly after `brew install planetscale/tap/pscal…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --skill` printed a complete vendor-shipped agent guide keylessly — Markdown frontmatter `name: …”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.pscale.dev/mcp/planetscale return…”

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

   PlanetScale ships an official hosted MCP server (verified live via OAuth handshake) plus a vendor-shipped CLI skill (`pscale --skill`) explicitly designed for agent consumption, and docs describe a separate insights-only MCP variant that excludes query execution — a concrete read/analysis-vs-execute scoping distinction. Agents can run non-interactive SQL (`pscale sql`) and review Insights to open PRs, showing real delegated database work. Missing for 10: explicit documentation of granular tool-level permissions distinguishing read-only SELECT/Insights tools from destructive DDL/DML tools within the full MCP server itself, and no independent hands-on report confirming an agent safely blocked from destructive actions.

   • [claimed-docs] “Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights”
   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Open a secure MySQL or PostgreSQL shell instance”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --skill` printed a complete vendor-shipped agent guide keylessly — Markdown frontmatter `name: …”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.pscale.dev/mcp/planetscale return…”

   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 PlanetScale
   PlanetScale~partialprobed5/10

   PlanetScale's branching model (docs-9,10,32) and CLI (docs-17,24; probe-5) let you programmatically create and manage isolated database/branch instances, which maps to the 'agent workflows' isolation story, and the CLI is explicitly designed for scripted/agent use (pscale sql, --skill). However, PlanetScale's product is architected around branches-per-database rather than truly independent databases, and community pricing feedback ($1.25/10GB storage, $15/100M rows) plus lack of a free tier (planetscale-comm-5, planetscale-comm-11) and a report of database creation being halted under load (planetscale-comm-12) undercut the 'cheaply create thousands' framing. Missing for 10: explicit documentation of per-tenant/per-agent database creation at scale, confirmed low/no-cost pricing for thousands of isolated instances, and evidence of fleet-level programmatic provisioning (bulk create/delete) beyond single branch/database CLI commands.

   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”
   • [claimed-docs] “Branches on PlanetScale Postgres are isolated database deployments that provide you with separate environments for development and testing, …”
   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Open a secure MySQL or PostgreSQL shell instance”
   • [probe] “official CLI documented at https://planetscale.com/docs/cli”
   • [community] “I really wish that the hobby tier hadn't gone but I also understand that planetscale is a b2b... I hope that planetscale's team doesn't get …”
   • [community] “The pricing gives me anxiety. $1.25/mo per 10GB storage, $15/mo per 100 Million rows read, $15/mo per 10 Million rows written. But I won't l…”
   • [community] “The site is experiencing higher than normal traffic and we have temporarily halted database creation. Ironic coming from the infinitely scal…”

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

   PlanetScale ships a live llms.txt (HTTP 200, confirmed by direct probe) plus extensive agent-oriented documentation: a dedicated ai-tooling doc, an MCP server doc, and a CLI --skill command that prints a vendor-authored agent guide baked into the binary. This goes beyond the minimal story requirement of just having llms.txt or agent docs. Missing for 10: independent/community confirmation that agents actually consume and act correctly on llms.txt in the wild (only vendor-side probes exist).

   • [probe] “PROBE llms.txt: HTTP 200 at https://planetscale.com/llms.txt # PlanetScale > PlanetScale is a relational database platform for MySQL and Po…”
   • [claimed-docs] “Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --skill` printed a complete vendor-shipped agent guide keylessly — Markdown frontmatter `name: …”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --version` printed `pscale version 0.329.0` keylessly after `brew install planetscale/tap/pscal…”

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

   PlanetScale's CLI explicitly supports non-interactive, scriptable SQL execution and JSON-formatted output designed for agents/automation, and runtime probes confirm `pscale --skill` ships a vendor-authored agent/CI guide plus `--format json` flags for headless use, alongside service-token auth (docs-7) enabling non-interactive authentication in CI. missing for 10: explicit CI/CD pipeline examples (e.g., GitHub Actions workflow), and independent community confirmation of headless CI usage.

   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “You can now show a single service token by ID.”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --version` printed `pscale version 0.329.0` keylessly after `brew install planetscale/tap/pscal…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --skill` printed a complete vendor-shipped agent guide keylessly — Markdown frontmatter `name: …”
   • [probe] “official CLI documented at https://planetscale.com/docs/cli”

   proof ↗⚑ flag

   CockroachDB✓fullprobed8/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to PlanetScale
   PlanetScale✓fullprobed9/10

   PlanetScale documents and hosts an official MCP server (mcp.pscale.dev) that connects Claude, Cursor, Notion, and other MCP-compatible tools to PlanetScale databases and Insights, and a runtime probe confirms the endpoint is live and correctly speaks the MCP OAuth handshake. Missing for 10: independent hands-on user reports of using the MCP server in practice beyond the vendor docs/probe.

   • [claimed-docs] “Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights”
   • [probe] “official MCP server documented at https://planetscale.com/docs/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.pscale.dev/mcp/planetscale return…”

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

   PlanetScale ships an official CLI (`pscale`) with explicit AI-agent affordances: non-interactive SQL execution, JSON output, an `--skill` subcommand that prints a vendor-authored agent prompt, and insights/analytics commands — all confirmed via live runtime probes, not just docs. Missing for 10: independent (non-vendor) hands-on community commentary specifically about CLI agentic usage beyond the runtime probes.

   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Open a secure MySQL or PostgreSQL shell instance”
   • [probe] “official CLI documented at https://planetscale.com/docs/cli”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --version` printed `pscale version 0.329.0` keylessly after `brew install planetscale/tap/pscal…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --skill` printed a complete vendor-shipped agent guide keylessly — Markdown frontmatter `name: …”

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

   PlanetScale ships a scriptable CLI (`pscale sql`, `--format json`, `--skill` agent guide) and a hosted MCP server for AI tools, which lets AI-native users drive the product programmatically, and docs explicitly target 'agents and scripts.' However, probes show no discoverable REST/GraphQL public API spec (openapi.json/swagger.json all 404, docs.md 404), so there's no traditional documented public API beyond the CLI/MCP surface. Missing for 10: a discoverable OpenAPI/REST API spec, independent confirmation that the CLI/MCP fully substitute for a public API in third-party integrations.

   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --version` printed `pscale version 0.329.0` keylessly after `brew install planetscale/tap/pscal…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --skill` printed a complete vendor-shipped agent guide keylessly — Markdown frontmatter `name: …”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.pscale.dev/mcp/planetscale return…”
   • [probe] “PROBE docs-md: HTTP 404 at https://planetscale.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://planetscale.com/openapi.json, https://planetscale.com/swagger.json, https://planetscale.com/…”

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

   PlanetScale supports scoped service tokens (shown/managed via CLI) for API access, and its hosted MCP server explicitly ships a separate insights-only variant that excludes query execution, speaking full OAuth Bearer scoping for agent connections — direct evidence of least-privilege credentialing for AI agents. However, there's no first-party doc enumerating granular permission scopes for service tokens or explicit guidance on issuing agent-specific restricted tokens beyond the MCP insights/query split. Missing for 10: documented granular service-token scope/role list, explicit agent-token creation workflow docs, independent/hands-on confirmation of scope enforcement.

   • [claimed-docs] “You can now show a single service token by ID.”
   • [claimed-docs] “Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.pscale.dev/mcp/planetscale return…”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”

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

   The evidence pack contains no mention of official SDKs or client libraries for building applications against PlanetScale programmatically—only CLI (pscale), MCP server, and webhook/API changelog items are documented. Since language SDKs are a fair and plausible offering for a database platform, the absence of any first-party SDK docs means this axis is unmet, not inapplicable. Missing for 10: any documentation of official SDKs/client libraries (Node, Go, Python, etc.), API reference tied to those SDKs, or independent confirmation of their existence.

   ⚑ 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 to PlanetScale
   PlanetScale✓fullclaimed8/10

   PlanetScale documents webhook events (including backup.succeeded/backup.failed) with configurable Authorization headers, giving AI-native users a way to subscribe to and consume platform events programmatically. missing for 10: broader catalog of event types beyond backups, independent hands-on confirmation of webhook reliability from community sources.

   • [claimed-docs] “You can now set an Authorization header on webhooks. Pass the full value, scheme included, like Bearer <token>.”
   • [claimed-docs] “We've added backup.succeeded and backup.failed webhook events. You'll get notified when a backup finishes, whether it worked or not.”

   proof ↗⚑ 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 PlanetScale
   PlanetScale✓fullprobed8/10

   PlanetScale's Insights feature provides server-side analysis of production traffic—aggregated query stats, failing query patterns, resource anomalies, and schema recommendations—directly inside the product (CLI/dashboard), and community evidence corroborates Insights surfacing actionable suggestions like missing indexes. This goes further into agentic territory with self-improving-database agents that review Insights and open PRs automatically, and MCP integration to expose Insights to AI tools. Missing for 10: independent verification of the self-improving-database agent's real-world accuracy/quality beyond vendor docs, and no direct hands-on user account of the AI-generated schema recommendations specifically (only the Insights index-suggestion anecdote).

   • [claimed-docs] “Surface PlanetScale's server-side analysis of a database: aggregated query statistics, failing query patterns, resource anomalies, and schem…”
   • [claimed-docs] “Surface PlanetScale’s server-side analysis of a database: aggregated query statistics, failing query patterns, resource anomalies, and schem…”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [claimed-docs] “an agent identifies the highest-impact performance issues, finds the relevant code, makes improvements, and opens a pull request”
   • [community] “We just migrated to PlanetScale Postgres Metal over the weekend. We are already seeing major query improvements. The migration was pretty sm…”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.pscale.dev/mcp/planetscale return…”

   proof ↗⚑ flag

   CockroachDB~partialprobed4/10

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

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

   proof ↗⚑ flag

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

   weight 2 · round to PlanetScale
   PlanetScale✓fullclaimed7/10

   PlanetScale documents a 'self-improving database' feature where an agent autonomously reviews production Insights and schema recommendations on a recurring schedule, then opens pull requests with performance improvements, plus webhook events for automation triggers. This matches the story of autonomous background automation, but evidence is first-party only. missing for 10: independent/hands-on confirmation that the self-improving agent actually runs unattended in production, and details on configuring/scheduling the automation beyond the doc description.

   • [claimed-docs] “an agent identifies the highest-impact performance issues, finds the relevant code, makes improvements, and opens a pull request”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [claimed-docs] “We've added backup.succeeded and backup.failed webhook events. You'll get notified when a backup finishes, whether it worked or not.”

   proof ↗⚑ flag

   CockroachDB—none0/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to PlanetScale
   PlanetScale~partialprobed4/10

   PlanetScale's 'self-improving database' feature describes an agent that reviews production Insights/Schema Recommendations on a recurring schedule and opens pull requests with performance improvements, which resembles a delegated-task AI capability tied to the product. However, this appears to run through connected external agents (Claude, Cursor, etc.) via the MCP server rather than a distinct in-dashboard chat assistant, and there's no evidence of a UI-embedded assistant a user directly converses with inside the product. Missing for 10: a first-party in-app chat/assistant UI, independent hands-on confirmation of the self-improving-database feature actually running end-to-end, and clarity that it's not just MCP-enabled third-party agents.

   • [claimed-docs] “an agent identifies the highest-impact performance issues, finds the relevant code, makes improvements, and opens a pull request”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [claimed-docs] “Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.pscale.dev/mcp/planetscale return…”

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

   PlanetScale enables natural-language/agentic operation indirectly via MCP server integration (Claude, Cursor, etc.) and a CLI with an agent-oriented '--skill' guide and JSON output modes for scripts/agents, plus a self-improving-database agent that opens PRs from Insights data. However, this is not a native NL command interface within PlanetScale's own product surface — it relies on third-party AI tools (Claude, Cursor) interpreting natural language and calling MCP/CLI functions, and there's no evidence of a first-party natural-language console or chat within the PlanetScale dashboard itself. missing for 10: evidence of a native in-product NL interface, independent hands-on validation of the MCP/agent workflow beyond vendor docs and probes.

   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights”
   • [claimed-docs] “an agent identifies the highest-impact performance issues, finds the relevant code, makes improvements, and opens a pull request”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --version` printed `pscale version 0.329.0` keylessly after `brew install planetscale/tap/pscal…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --skill` printed a complete vendor-shipped agent guide keylessly — Markdown frontmatter `name: …”
   • [probe] “PROBE runtime (recorded 2026-09-06): keyless JSON-RPC initialize POST to the hosted MCP server https://mcp.pscale.dev/mcp/planetscale return…”

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

   Probes explicitly show no OpenAPI/interactive API reference exists (docs.md 404, all openapi.json candidate paths 404), and no evidence pack item describes a runnable-example API console; only static CLI/API docs and changelog entries are present.

   • [probe] “PROBE docs-md: HTTP 404 at https://planetscale.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://planetscale.com/openapi.json, https://planetscale.com/swagger.json, https://planetscale.com/…”

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

   The probe explicitly checked for an OpenAPI/Swagger spec at all standard candidate paths and found only 404s, with no other evidence of a published machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://planetscale.com/openapi.json, https://planetscale.com/swagger.json, https://planetscale.com/…”
   • [probe] “PROBE docs-md: HTTP 404 at https://planetscale.com/docs.md”

   proof ↗⚑ flag

   CockroachDB—none0/10

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

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

   proof ↗⚑ flag

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

   weight 1 · round to PlanetScale
   PlanetScale✓fullprobed9/10

   PlanetScale's core branching model explicitly provides isolated dev/test branches separate from production ('separate environments for development and testing'), with deploy-requests to safely promote schema changes without touching production data directly, and this is corroborated by community accounts of using branch-per-git-branch workflows for development/testing. The MCP server and CLI further enable AI agents to interact with branches programmatically rather than production. Missing for 10: no hands-on independent account specifically framing branch use as an 'AI agent sandbox test' scenario, though the underlying capability is well documented.

   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”
   • [claimed-docs] “Branches on PlanetScale Postgres are isolated database deployments that provide you with separate environments for development and testing, …”
   • [claimed-docs] “Database branching, coupled with deploy requests, allows you to deploy non-blocking schema changes to your production database with zero dow…”
   • [claimed-docs] “You can then create development branches that you can use for development before shipping schema changes to production.”
   • [community] “I have been using the beta version of PlanetScale for a while, and it is extremely cool... It will give you a database branch for each Git b…”
   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [probe] “official MCP server documented at https://planetscale.com/docs/mcp-server”

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

   No evidence pack items mention API versioning scheme or a documented deprecation policy; probes for OpenAPI specs return 404s and changelog entries are feature announcements, not API-version/deprecation documentation.

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

   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 drawn
   PlanetScale~partialprobed5/10

   PlanetScale's CLI explicitly supports non-interactive, scriptable operation (`pscale sql`) with a vendor-shipped agent skill and JSON output modes clearly aimed at automation across many items, and its AI-tooling docs describe agents that recurringly review Insights/Schema Recommendations across a database and open PRs. However, there's no explicit documentation of true bulk/batch operations (e.g., batch branch creation/deletion, bulk import across many databases, multi-item API calls) — the CLI and API appear built around single-resource commands invoked repeatedly rather than a dedicated bulk-operation primitive. Missing for 10: explicit bulk/batch API or CLI commands operating on many items in one call, and independent hands-on evidence of large-scale automated bulk operations succeeding.

   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --version` printed `pscale version 0.329.0` keylessly after `brew install planetscale/tap/pscal…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --skill` printed a complete vendor-shipped agent guide keylessly — Markdown frontmatter `name: …”
   • [claimed-docs] “Connect Claude, Cursor, Notion, and other MCP-compatible tools to your PlanetScale databases and Insights”

   proof ↗⚑ flag

   CockroachDB~partialclaimed5/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to PlanetScale
   PlanetScale~partialclaimed4/10

   PlanetScale supports webhook events (e.g., backup.succeeded/failed) with configurable authorization headers, letting users trigger external actions when specific system events occur, and its self-improving-database agent runs on a recurring schedule to open PRs based on Insights data. However, this is limited to a small set of predefined events (mainly backups) rather than a general-purpose rule engine for arbitrary triggers/actions. missing for 10: a documented rules/automation engine supporting custom trigger conditions across arbitrary event types, and evidence of user-defined conditional logic beyond fixed webhook events.

   • [claimed-docs] “We've added backup.succeeded and backup.failed webhook events. You'll get notified when a backup finishes, whether it worked or not.”
   • [claimed-docs] “You can now set an Authorization header on webhooks. Pass the full value, scheme included, like Bearer <token>.”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [claimed-docs] “an agent identifies the highest-impact performance issues, finds the relevant code, makes improvements, and opens a pull request”

   proof ↗⚑ flag

   CockroachDB~partialclaimed3/10

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

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to PlanetScale
   PlanetScale~partialclaimed5/10

   PlanetScale documents a specific recurring AI-driven workflow: agents reviewing Insights/Schema Recommendations and opening PRs 'on a recurring schedule' (docs-31, docs-20), plus daily scheduled backups (docs-12, docs-33). This is real recurring automation but narrow — it's tied to the self-improving-database feature, not a general-purpose job/workflow scheduler that AI-native users can configure for arbitrary tasks. Missing for 10: a documented mechanism for users to define/schedule arbitrary custom jobs or workflows (e.g., cron-style scheduling, workflow orchestration), and independent/community confirmation that the recurring-agent feature works in practice.

   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [claimed-docs] “an agent identifies the highest-impact performance issues, finds the relevant code, makes improvements, and opens a pull request”
   • [claimed-docs] “PlanetScale provides the ability to create, schedule, and restore backups for production and development database branches.”
   • [claimed-docs] “In addition to the daily default backups that PlanetScale schedules for your database branches, you can create additional manual backups.”

   proof ↗⚑ 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 to PlanetScale
   PlanetScale✓fullclaimed7/10

   PlanetScale's docs show agents opening pull requests for schema changes (docs-20, docs-31) that flow through deploy requests for review (docs-11, docs-27), with branching giving version isolation (docs-9, docs-10) and backups/point-in-time restore enabling rollback (docs-12, docs-5, docs-33). Together these cover the version/review/rollback lifecycle for AI-driven automations. missing for 10: independent/hands-on corroboration that agent-opened PRs are actually reviewed and rolled back in practice, and a dedicated audit/version history view specifically for automation runs rather than general schema branches.

   • [claimed-docs] “an agent identifies the highest-impact performance issues, finds the relevant code, makes improvements, and opens a pull request”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [claimed-docs] “Database branching, coupled with deploy requests, allows you to deploy non-blocking schema changes to your production database with zero dow…”
   • [claimed-docs] “deploy non-blocking schema changes to your production database with zero downtime”
   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”
   • [claimed-docs] “Branches on PlanetScale Postgres are isolated database deployments that provide you with separate environments for development and testing, …”
   • [claimed-docs] “PlanetScale provides the ability to create, schedule, and restore backups for production and development database branches.”
   • [claimed-docs] “You can now create a PostgreSQL branch restored to a point-in-time timestamp with --restore-point.”
   • [claimed-docs] “In addition to the daily default backups that PlanetScale schedules for your database branches, you can create additional manual backups.”
   • [claimed-docs] “After starting a switchover, you can now list switchovers for a branch and show one by ID.”

   proof ↗⚑ 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 PlanetScale
   PlanetScale~partialclaimed6/10

   Docs show branch restore capability via backups (create/schedule/restore backups for branches, docs-12/33) and Postgres branches support point-in-time restore with --restore-point (docs-5), plus branches described as providing 'restoring from backups' (docs-10). However, there's no explicit documentation of a 'reset branch to match parent' operation for the (MySQL/Vitess) branching model, and no independent/community confirmation of restoring a branch state without a full dump rebuild. Missing for 10: explicit 'reset to parent' semantics for MySQL branches, hands-on/community verification of restore workflow, and clarity on whether MySQL branches support point-in-time restore like Postgres.

   • [claimed-docs] “You can now create a PostgreSQL branch restored to a point-in-time timestamp with --restore-point.”
   • [claimed-docs] “Branches on PlanetScale Postgres are isolated database deployments that provide you with separate environments for development and testing, …”
   • [claimed-docs] “PlanetScale provides the ability to create, schedule, and restore backups for production and development database branches.”
   • [claimed-docs] “In addition to the daily default backups that PlanetScale schedules for your database branches, you can create additional manual backups.”
   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”

   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 PlanetScale
   PlanetScale~partialprobed7/10

   PlanetScale's core product is branch-based schema workflows (branch per git branch, dev/test isolation, restore-point branches) and the CLI/API supports creating and deleting branches non-interactively, which platform engineers can script into CI. However, the evidence pack has no explicit CI/CD integration example (e.g., GitHub Action, deploy-platform webhook triggering branch creation/teardown per PR) — only generic webhook/backup events and CLI docs are shown. Missing for 10: a documented CI/CD or GitHub Actions integration showing automatic branch creation on PR-open and deletion on PR-close, and evidence of platform (e.g., Vercel/Netlify) preview-environment wiring.

   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”
   • [claimed-docs] “You can then create development branches that you can use for development before shipping schema changes to production.”
   • [claimed-docs] “You can now create a PostgreSQL branch restored to a point-in-time timestamp with --restore-point.”
   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [community] “I have been using the beta version of PlanetScale for a while, and it is extremely cool... It will give you a database branch for each Git b…”
   • [probe] “official CLI documented at https://planetscale.com/docs/cli”

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

   PlanetScale's docs explicitly describe branching database schemas and data the same way as code branches, creating isolated dev/test environments from production-shaped branches (docs-9, docs-10, docs-32), corroborated by hands-on community use describing a database branch per git branch workflow (comm-9). Backups/restores and non-blocking schema deploys further support the workflow (docs-11, docs-12, docs-27). missing for 10: independent post-2021 hands-on confirmation of copy-on-write speed/isolation specifics, explicit copy-on-write terminology in docs.

   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”
   • [claimed-docs] “Branches on PlanetScale Postgres are isolated database deployments that provide you with separate environments for development and testing, …”
   • [claimed-docs] “Database branching, coupled with deploy requests, allows you to deploy non-blocking schema changes to your production database with zero dow…”
   • [claimed-docs] “You can then create development branches that you can use for development before shipping schema changes to production.”
   • [community] “I have been using the beta version of PlanetScale for a while, and it is extremely cool... It will give you a database branch for each Git b…”

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

   The evidence pack contains no mention of an HTTP- or WebSocket-based serverless/edge driver, connection pooling for short-lived connections, or any client library targeting edge runtimes; only CLI, MCP server, branching, backups, and general connectivity topics are covered. This axis clearly applies to a database platform aiming at modern app stacks, but no supporting evidence exists in the pack.

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

   PlanetScale docs mention listing available regions for a database and configured Vitess read-only regions, implying support for placing read replicas in specific geographic regions to reduce latency, and Postgres replicas can offload reads from the primary. However, this is a single thin mention with no detail on how region selection is configured, no explicit multi-region replica setup guide, and no independent/community confirmation of real-world latency improvements from region placement. Missing for 10: detailed region-selection/configuration docs, benchmarks or community reports of latency reduction from region placement, and confirmation this works consistently across both MySQL/Vitess and Postgres offerings.

   • [claimed-docs] “You can now list the regions available to a database, and list configured Vitess read-only regions for the database's default branch.”
   • [claimed-docs] “Append `|replica` to the end of your username for the branch you want to target”
   • [claimed-docs] “They provide a way to reduce load on your primary instance by allowing you to read from a replica.”
   • [claimed-docs] “Postgres replicas can be used to read data and reduce load on the primary.”

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

   Docs confirm PlanetScale Postgres ships with a managed PgBouncer instance (with its own dashboard/graphs), meaning the platform-engineer doesn't need to deploy or operate a separate pooler themselves. However, there's no explicit documentation quantifying concurrent-connection capacity ('thousands of connections') or describing pooler configuration/tuning options, and MySQL/Vitess-side pooling (vttablet) isn't mentioned at all in the pack. Missing for 10: explicit connection-capacity claims/benchmarks, pooler configuration docs, and confirmation this applies to the MySQL/Vitess product line as well as Postgres.

   • [claimed-docs] “Postgres instance, storage, and PgBouncer graphs now live on their own tabs with shareable URLs.”

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

   No evidence anywhere in the pack mentions vector data types, embeddings, or similarity search functionality in PlanetScale (MySQL or Postgres offerings); the pack covers branching, backups, scaling, MCP/CLI tooling, and pricing but nothing about vector storage/search.

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

   PlanetScale's evidence pack shows a MySQL/Postgres OLTP platform (branching, backups, replicas, sharding, Metal for IOPS, Insights for query monitoring) but nothing about columnar storage, OLAP query engines, or analytical aggregation performance for dashboard workloads over large tables. No documentation or community evidence addresses running heavy analytical aggregations fast without exporting to a warehouse.

   ⚑ flag

   CockroachDB—none0/10

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

   ⚑ flag

Compatibility

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

   weight 3 · round to CockroachDB
   PlanetScale!disputedcontradicted4/10

   PlanetScale markets itself as MySQL and Postgres compatible with branching, imports, and scaling docs, but hands-on community reports specifically state that PlanetScale's Vitess-based MySQL layer does not support foreign keys — a core MySQL feature many existing apps expect — making it a lookalike subset rather than full engine fidelity for that dialect. Missing for 10: any evidence resolving the FK limitation, independent confirmation of full Postgres extension/dialect parity, and SQLite compatibility is not addressed at all.

   • [community] “The referential integrity piece (otherwise known as Foreign Keys) will not be addressed and is a limitation - some might say feature - of Vi…”
   • [community] “To me, this means that planetscale (and vitess) immediately become less useful for a large class of applications: existing apps that use an …”
   • [community] “The boulder-sized caveat: PlanetScale's Non-Blocking Schema Changes' workflow doesn't support FOREIGN KEYs in users' databases.”
   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”
   • [claimed-docs] “PlanetScale provides an import tool in the dashboard that allows you to painlessly import an existing internet-accessible MySQL or MariaDB d…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://planetscale.com/llms.txt # PlanetScale > PlanetScale is a relational database platform for MySQL and Po…”

   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 to CockroachDB
   PlanetScale~partialprobed7/10

   Docs confirm core CLI daily-loop pieces: opening a secure MySQL/Postgres shell (pscale shell), running non-interactive SQL for scripts/agents (pscale sql), listing/showing service tokens, regions, and switchovers, and enabling org SSO from the CLI — and a runtime probe confirms the CLI installs and works keylessly with agent-oriented help (`--skill`). However, explicit CLI-driven 'create database' and full branch-lifecycle commands aren't directly cited (only branching/backup docs, which are Vitess/Postgres feature docs rather than CLI command references). Missing for 10: explicit CLI create-database/create-branch command docs, and independent hands-on confirmation that inspect/connect flows fully replace the dashboard.

   • [claimed-docs] “Open a secure MySQL or PostgreSQL shell instance”
   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Organization administrators can now enable and manage SSO from the CLI with pscale org sso.”
   • [claimed-docs] “You can now show a single service token by ID.”
   • [claimed-docs] “You can now list the regions available to a database, and list configured Vitess read-only regions for the database's default branch.”
   • [claimed-docs] “After starting a switchover, you can now list switchovers for a branch and show one by ID.”
   • [probe] “official CLI documented at https://planetscale.com/docs/cli”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --version` printed `pscale version 0.329.0` keylessly after `brew install planetscale/tap/pscal…”
   • [probe] “PROBE runtime (recorded 2026-09-06): `pscale --skill` printed a complete vendor-shipped agent guide keylessly — Markdown frontmatter `name: …”

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

   PlanetScale is a cloud-hosted database platform; there is no evidence of a downloadable/local engine that runs keylessly offline. Community evidence directly confirms this gap: a user explicitly asked whether PlanetScale can be installed locally, work offline, or is open source, and confirmed the answer to all three is no, calling it vendor lock-in.

   • [community] “Can I install this locally? Will it work without an internet connection? Is it fully open source? From what I can tell, the answer to all th…”

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

   The evidence pack contains extensive docs on branching, schema deploy requests, backups, imports, and CLI/MCP tooling, but nothing that specifically documents ORM or framework integration guides for Prisma, Drizzle, Django, or Rails. No citation mentions any of these named ORMs/frameworks or dedicated setup guides for them.

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

   PlanetScale's docs explicitly describe a dashboard import tool for existing internet-accessible MySQL/MariaDB databases with 'no downtime' (planetscale-docs-13, planetscale-docs-21), giving a documented migration path. Community evidence corroborates smooth production migrations (e.g., Metal migration over the weekend with major improvements), though one user notes friction migrating from Heroku due to logical replication restrictions. Missing for 10: independent hands-on verification specifically of the MySQL/MariaDB import tool (vs. Postgres/Metal migrations), and no mention of Postgres import path with equivalent zero-downtime guarantee.

   • [claimed-docs] “PlanetScale provides an import tool in the dashboard that allows you to painlessly import an existing internet-accessible MySQL or MariaDB d…”
   • [claimed-docs] “PlanetScale provides an import tool in the dashboard that allows you to painlessly import an existing internet-accessible MySQL or MariaDB d…”
   • [community] “We just migrated to PlanetScale Postgres Metal over the weekend. We are already seeing major query improvements. The migration was pretty sm…”
   • [community] “Just wish the migration path from Heroku was a tad easier (Heroku blocks logical replication on all instances) but pushing through anyway be…”

   proof ↗⚑ flag

   CockroachDB~partialclaimed3/10

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

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

   proof ↗⚑ flag

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

   weight 3 · round to PlanetScale
   PlanetScale~partialcommunity7/10

   PlanetScale's docs describe schema branching plus deploy requests as the core workflow for non-blocking, zero-downtime production schema changes, and community reports (e.g., smooth Metal migration, working Insights) corroborate real-world use. However, independent community reports flag a 'boulder-sized caveat' that the non-blocking schema-change workflow does not support foreign keys, which excludes many existing schemas from safe zero-downtime migrations. missing for 10: evidence of foreign-key support in the non-blocking DDL workflow, and independent verification of deploy-request behavior under load/failure scenarios.

   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”
   • [claimed-docs] “Database branching, coupled with deploy requests, allows you to deploy non-blocking schema changes to your production database with zero dow…”
   • [claimed-docs] “deploy non-blocking schema changes to your production database with zero downtime”
   • [claimed-docs] “You can then create development branches that you can use for development before shipping schema changes to production.”
   • [community] “The boulder-sized caveat: PlanetScale's Non-Blocking Schema Changes' workflow doesn't support FOREIGN KEYs in users' databases.”
   • [community] “The referential integrity piece (otherwise known as Foreign Keys) will not be addressed and is a limitation - some might say feature - of Vi…”
   • [community] “To me, this means that planetscale (and vitess) immediately become less useful for a large class of applications: existing apps that use an …”

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

   The CLI/API surface is broad — SSO management, service tokens, backups, webhooks, regions, switchovers, branching, insights, sql shell — mirroring most dashboard actions (planetscale-docs-3,4,6,7,8,17,24,26). However the import tool is explicitly described as living 'in the dashboard' (planetscale-docs-13/21), suggesting at least one UI-only capability, and probes show no discoverable OpenAPI/REST spec (planetscale-probe-3), only CLI-level parity documented. Missing for 10: confirmed feature-for-feature parity (e.g. import via CLI/API), a documented formal API spec, and independent hands-on confirmation that nothing requires the UI.

   • [claimed-docs] “Organization administrators can now enable and manage SSO from the CLI with pscale org sso.”
   • [claimed-docs] “We've added backup.succeeded and backup.failed webhook events. You'll get notified when a backup finishes, whether it worked or not.”
   • [claimed-docs] “After starting a switchover, you can now list switchovers for a branch and show one by ID.”
   • [claimed-docs] “You can now show a single service token by ID.”
   • [claimed-docs] “You can now list the regions available to a database, and list configured Vitess read-only regions for the database's default branch.”
   • [claimed-docs] “PlanetScale provides an import tool in the dashboard that allows you to painlessly import an existing internet-accessible MySQL or MariaDB d…”
   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Open a secure MySQL or PostgreSQL shell instance”
   • [probe] “PROBE openapi: all candidate paths 404 (https://planetscale.com/openapi.json, https://planetscale.com/swagger.json, https://planetscale.com/…”
   • [probe] “official CLI documented at https://planetscale.com/docs/cli”

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

   The evidence pack shows no vendor documentation of a bulk data-export feature or open-format dump/leave workflow (only an import tool for MySQL/MariaDB is documented). Community commentary directly states PlanetScale is not open source, can't run locally/offline, and is 'yet another example of vendor lock-in,' reinforcing the absence of a documented exit/export path.

   • [claimed-docs] “PlanetScale provides an import tool in the dashboard that allows you to painlessly import an existing internet-accessible MySQL or MariaDB d…”
   • [community] “Can I install this locally? Will it work without an internet connection? Is it fully open source? From what I can tell, the answer to all th…”

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

   PlanetScale is a closed, proprietary hosted database platform; no evidence pack item claims open-licensed source code, and community evidence explicitly states it is not open source ('Is it fully open source? ... the answer ... is no').

   • [community] “Can I install this locally? Will it work without an internet connection? Is it fully open source? From what I can tell, the answer to all th…”

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

   PlanetScale is a fully-hosted cloud database platform with no documented self-host/on-prem option; community evidence explicitly confirms it cannot be installed locally or run offline and is not open source ('Can I install this locally?... the answer to all three questions is no'), contradicting the self-hosting story entirely.

   • [community] “Can I install this locally? Will it work without an internet connection? Is it fully open source? From what I can tell, the answer to all th…”

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

   Docs show only that founders can view current/previous usage per database (planetscale-docs-25), not that they can set spend caps or configure usage alerts to prevent surprise bills. No evidence pack item describes budget limits, alert thresholds, or automatic throttling tied to spend.

   • [claimed-docs] “View your current and previous usage per database”

   proof ↗⚑ flag

   CockroachDB~partialclaimed3/10

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

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

   proof ↗⚑ flag

Insights

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

   weight 2 · round to PlanetScale
   PlanetScale✓fullcommunity9/10

   PlanetScale's Insights feature surfaces aggregated query statistics, failing query patterns, resource anomalies, and schema recommendations computed from production traffic, including ranking top queries by performance metric — directly matching the story's slow-query, index-recommendation, and performance-metrics asks. A hands-on HN report independently corroborates that the Insights tab surfaced missing indexes that sped up queries after migration. Missing for 10: broader independent corroboration beyond a single community post and more detail on the dashboard UI itself (docs focus mostly on CLI insights commands).

   • [claimed-docs] “Surface PlanetScale's server-side analysis of a database: aggregated query statistics, failing query patterns, resource anomalies, and schem…”
   • [claimed-docs] “Surface PlanetScale’s server-side analysis of a database: aggregated query statistics, failing query patterns, resource anomalies, and schem…”
   • [claimed-docs] “List top queries ranked by a performance metric”
   • [claimed-docs] “Agents can review production Insights data and Schema Recommendations, then open pull requests with performance improvements — on a recurrin…”
   • [community] “We just migrated to PlanetScale Postgres Metal over the weekend. We are already seeing major query improvements. The migration was pretty sm…”

   proof ↗⚑ flag

   CockroachDB~partialclaimed3/10

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

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

   proof ↗⚑ flag

Pricing

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

   weight 2 · round to CockroachDB
   PlanetScale—none0/10

   Community evidence explicitly states PlanetScale removed its free/hobby tier and users now face pay-as-you-go pricing with per-row and per-storage charges, with no vendor docs describing any current free tier for prototyping. No evidence contradicts this or shows a usable free option today.

   • [community] “I really wish that the hobby tier hadn't gone but I also understand that planetscale is a b2b... I hope that planetscale's team doesn't get …”
   • [community] “The pricing gives me anxiety. $1.25/mo per 10GB storage, $15/mo per 100 Million rows read, $15/mo per 10 Million rows written. But I won't l…”

   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 PlanetScale
   PlanetScale~partialcommunity4/10

   Community evidence cites specific per-unit rates (storage, rows read, rows written) suggesting granular usage-based pricing exists, and docs mention a usage dashboard for tracking consumption, but there is no first-party pricing page or rate card in the evidence pack confirming these figures are current or comprehensive across compute, storage, and traffic. missing for 10: an official pricing page with per-unit rates, confirmation the cited 2021 rates are current, and any breakdown of compute pricing specifically.

   • [community] “The pricing gives me anxiety. $1.25/mo per 10GB storage, $15/mo per 100 Million rows read, $15/mo per 10 Million rows written. But I won't l…”
   • [claimed-docs] “View your current and previous usage per database”
   • [community] “I really wish that the hobby tier hadn't gone but I also understand that planetscale is a b2b... I hope that planetscale's team doesn't get …”

   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
   PlanetScale~partialclaimed4/10

   Docs mention listing regions available to a database and configuring read-only regions (planetscale-docs-8), implying region selection is possible, but there's no explicit documentation of choosing a primary region at database creation, data residency guarantees, or compliance certifications. missing for 10: explicit region-selection-at-creation docs, data residency/compliance statements, independent confirmation of region choice.

   • [claimed-docs] “You can now list the regions available to a database, and list configured Vitess read-only regions for the database's default branch.”

   proof ↗⚑ flag

   CockroachDB~partialcommunity6/10

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

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

   proof ↗⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round to CockroachDB
   PlanetScale—none0/10

   The evidence pack covers backups, branching, replicas, and MCP/CLI tooling but contains no documentation of data-retention policies, backup-retention windows, or explicit data-deletion/purge controls (e.g., how long backups are kept, how to fully delete a database or purge branch data) that would let an AI-native user govern retention and deletion.

   ⚑ 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

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

   weight 2 · round drawn
   PlanetScale—none0/10

   No evidence pack item mentions telemetry, usage tracking, or an opt-out setting for PlanetScale's CLI, dashboard, or MCP server; the closest related item (usage billing view) concerns cost tracking, not telemetry.

   ⚑ 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 PlanetScale
   PlanetScale✓fullcommunity7/10

   PlanetScale documents read replicas (Postgres and Vitess read-only regions), branch switchovers with list/show by ID, scheduled/manual backups, and backup success/failure webhook events, covering the core reliability and failover lifecycle. Community evidence (comm-1, comm-2) corroborates responsive incident handling, though it's not a rigorous documented failover SLA or independent chaos-test report. Missing for 10: an explicit HA/failover SLA or uptime guarantee, and independent verification of automatic failover behavior under real outages.

   • [claimed-docs] “You can now list the regions available to a database, and list configured Vitess read-only regions for the database's default branch.”
   • [claimed-docs] “Append `|replica` to the end of your username for the branch you want to target”
   • [claimed-docs] “They provide a way to reduce load on your primary instance by allowing you to read from a replica.”
   • [claimed-docs] “Postgres replicas can be used to read data and reduce load on the primary.”
   • [claimed-docs] “After starting a switchover, you can now list switchovers for a branch and show one by ID.”
   • [claimed-docs] “PlanetScale provides the ability to create, schedule, and restore backups for production and development database branches.”
   • [claimed-docs] “In addition to the daily default backups that PlanetScale schedules for your database branches, you can create additional manual backups.”
   • [claimed-docs] “We've added backup.succeeded and backup.failed webhook events. You'll get notified when a backup finishes, whether it worked or not.”
   • [community] “We just migrated to PlanetScale Postgres Metal over the weekend. We are already seeing major query improvements. The migration was pretty sm…”
   • [community] “We were in the beta for this and they've been great... Had one incident during the beta which we believed we caused on our own but within 5 …”

   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 PlanetScale
   PlanetScale✓fullclaimed7/10

   Docs explicitly state PlanetScale lets users create, schedule, and restore backups for branches, with daily default backups plus manual backups, point-in-time restore for Postgres branches, and webhook notifications (backup.succeeded/failed) for visibility into backup status. This covers scheduled, visible, self-serve backup/restore workflows for both MySQL/Vitess and Postgres branches. Missing for 10: no independent/hands-on community confirmation of the backup/restore UX specifically, and no detail on how granular the schedule configuration UI is beyond 'daily default'.

   • [claimed-docs] “PlanetScale provides the ability to create, schedule, and restore backups for production and development database branches.”
   • [claimed-docs] “In addition to the daily default backups that PlanetScale schedules for your database branches, you can create additional manual backups.”
   • [claimed-docs] “You can now create a PostgreSQL branch restored to a point-in-time timestamp with --restore-point.”
   • [claimed-docs] “We've added backup.succeeded and backup.failed webhook events. You'll get notified when a backup finishes, whether it worked or not.”
   • [claimed-docs] “Branches on PlanetScale Postgres are isolated database deployments that provide you with separate environments for development and testing, …”

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

   PlanetScale docs explicitly support point-in-time restore branches for Postgres (--restore-point), scheduled/manual backups for Vitess branches, and branching that includes restoring from backups, directly matching the platform-engineer's recovery workflow. missing for 10: independent/hands-on verification of an actual PITR recovery from a bad write, and explicit documentation of the retention window length/limits.

   • [claimed-docs] “You can now create a PostgreSQL branch restored to a point-in-time timestamp with --restore-point.”
   • [claimed-docs] “Branches on PlanetScale Postgres are isolated database deployments that provide you with separate environments for development and testing, …”
   • [claimed-docs] “PlanetScale provides the ability to create, schedule, and restore backups for production and development database branches.”
   • [claimed-docs] “In addition to the daily default backups that PlanetScale schedules for your database branches, you can create additional manual backups.”
   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”

   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 CockroachDB
   PlanetScale~partialcommunity4/10

   A community comment describes the platform scaling an instance from zero to handling massive load automatically, but this is an old beta anecdote rather than current vendor documentation, and the docs pack mostly describes read replicas, sharding, and dedicated 'Metal' instances (which imply manual provisioning, not automatic compute autoscaling). Missing for 10: official docs describing automatic vertical/horizontal compute scaling triggers, confirmation of zero-downtime resizing for the current Postgres/Metal offering, and independent hands-on verification of autoscale behavior under load.

   • [community] “I have been using the beta version of PlanetScale for a while, and it is extremely cool... It will give you a database branch for each Git b…”
   • [claimed-docs] “Metal is an excellent choice for high-IOPS and other performance-critical workloads. With Metal, your database now has the ability to use mo…”
   • [claimed-docs] “You can now list the regions available to a database, and list configured Vitess read-only regions for the database's default branch.”
   • [claimed-docs] “They provide a way to reduce load on your primary instance by allowing you to read from a replica.”

   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 CockroachDB
   PlanetScale~partialcommunity3/10

   Only a single old community comment (from the 2020 beta) claims the database 'cost scale to 0, so it is perfect for small projects,' and no current vendor docs in the pack describe a scale-to-zero or free-tier mechanism; another community comment notes the hobby/free tier was later removed, casting doubt on whether idle prototypes truly cost nothing today. missing for 10: current first-party documentation describing scale-to-zero billing/behavior, confirmation that idle databases remain durable while scaled down, and evidence of an active free/hobby tier for side projects.

   • [community] “I have been using the beta version of PlanetScale for a while, and it is extremely cool... It will give you a database branch for each Git b…”
   • [community] “I really wish that the hobby tier hadn't gone but I also understand that planetscale is a b2b... I hope that planetscale's team doesn't get …”
   • [community] “The pricing gives me anxiety. $1.25/mo per 10GB storage, $15/mo per 100 Million rows read, $15/mo per 10 Million rows written. But I won't l…”

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

   Docs and community evidence support serverless, scale-to-zero database provisioning and branching (e.g., 'database branch for each Git branch... cost scale to 0... will scale to support massive load') and PlanetScale's CLI is documented for schema branching, SQL execution, and shell access, implying rapid setup without manual capacity planning. However, no evidence explicitly documents a 'create database' CLI/API command or confirms 'ready in seconds' timing, and one community report notes a past incident where database creation was temporarily halted due to traffic. missing for 10: explicit CLI/API docs for database creation command, quantified provisioning time, and independent verification of instant readiness.

   • [community] “I have been using the beta version of PlanetScale for a while, and it is extremely cool... It will give you a database branch for each Git b…”
   • [claimed-docs] “PlanetScale allows you to branch database schemas the same way you branch your code.”
   • [claimed-docs] “Run non-interactive SQL for agents and scripts (`pscale sql`)”
   • [claimed-docs] “Open a secure MySQL or PostgreSQL shell instance”
   • [community] “The site is experiencing higher than normal traffic and we have temporarily halted database creation. Ironic coming from the infinitely scal…”

   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