Neon vs PlanetScale

Agent ops

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

   weight 3 · round to Neon
   Neon✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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

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

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Neon
   Neon~partialcommunity6/10

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

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

   proof ↗⚑ flag

   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

Agent access

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

   weight 2 · round drawn
   Neon✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to PlanetScale
   Neon✓fullprobed7/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to PlanetScale
   Neon✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Neon✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Neon
   Neon✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to PlanetScale
   Neon~partialprobed4/10

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

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

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

   weight 2 · round to Neon
   Neon~partialprobed6/10

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

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

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to PlanetScale
   Neon—none0/10

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

   ⚑ flag

   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

Agentic features

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

   weight 2 · round to PlanetScale
   Neon—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to PlanetScale
   Neon—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to PlanetScale
   Neon—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Neon~partialprobed6/10

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

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

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Neon—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Neon
   Neon✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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

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

   weight 1 · round to PlanetScale
   Neon✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Neon—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to PlanetScale
   Neon—none0/10

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

   ⚑ flag

   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

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

   weight 3 · round to PlanetScale
   Neon—none0/10

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

   ⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to PlanetScale
   Neon—none0/10

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

   ⚑ flag

   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

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

   weight 1 · round to PlanetScale
   Neon—none0/10

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

   ⚑ flag

   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

Branching

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

   weight 1 · round to Neon
   Neon✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Neon
   Neon✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Neon✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   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

Drivers

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

   weight 2 · round to Neon
   Neon✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   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

Latency

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

   weight 2 · round to PlanetScale
   Neon~partialcommunity3/10

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

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

   proof ↗⚑ flag

   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

Pooling

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

   weight 2 · round to Neon
   Neon✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

Ai data

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

   weight 2 · round to Neon
   Neon✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

Analytics

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

   weight 2 · round drawn
   Neon—none0/10

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

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

   proof ↗⚑ flag

   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

Compatibility

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

   weight 3 · round to Neon
   Neon~partialcommunity6/10

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

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

   proof ↗⚑ flag

   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

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

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Neon
   Neon~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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

Integrations

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

   weight 2 · round drawn
   Neon—none0/10

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

   ⚑ flag

   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

Migrations

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

   weight 1 · round to PlanetScale
   Neon—none0/10

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

   ⚑ flag

   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

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

   weight 3 · round to PlanetScale
   Neon~partialcommunity5/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Neon
   Neon✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Neon
   Neon~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Neon
   Neon✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

4. ai-native userSelf-host the core product

   weight 3 · round to Neon
   Neon~partialcommunity6/10

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

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

   proof ↗⚑ flag

   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

Cost controls

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

   weight 1 · round drawn
   Neon—none0/10

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

   ⚑ flag

   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

Insights

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

   weight 2 · round to PlanetScale
   Neon—none0/10

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

   ⚑ flag

   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

Pricing

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

   weight 2 · round to Neon
   Neon✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to PlanetScale
   Neon!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to PlanetScale
   Neon—none0/10

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

   ⚑ flag

   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

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Neon—none0/10

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

   ⚑ flag

   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

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

   weight 2 · round drawn
   Neon—none0/10

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

   ⚑ flag

   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

Availability

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

   weight 2 · round to PlanetScale
   Neon~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

Recovery

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

   weight 2 · round to PlanetScale
   Neon~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Neon✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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

Elasticity

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

   weight 2 · round to Neon
   Neon✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Neon
   Neon✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   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

Provisioning

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

   weight 3 · round to Neon
   Neon✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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