SYSTEM Cited by 1 source

PlanetScale¶

What it is¶

PlanetScale (planetscale.com) is a managed relational database vendor offering:

PlanetScale MySQL — their original product, built on Vitess (MySQL-protocol sharding layer originally from YouTube).
PlanetScale Postgres — a newer Postgres-compatible offering, positioned for "developers who need a powerful, flexible, and scalable database to power their applications", with explicit call-outs of extensions like pgvector for AI-driven workloads (Source: sources/2026-04-16-cloudflare-deploy-postgres-and-mysql-databases-with-planetscale-workers).

Differentiators called out on the Cloudflare blog:

Query insights — per-query performance telemetry for finding slow SQL.
Agent-driven tooling for improving SQL query performance.
Database branching — schema / data branches for deploying code safely, including database changes alongside application changes.

Starting price anchored at $5/month for a single Postgres node.

Why it shows up on this wiki¶

PlanetScale is the canonical wiki instance of the patterns/partner-managed-service-as-native-binding pattern on Cloudflare's developer platform:

Customer provisions a PlanetScale database from the Cloudflare dashboard / API.
Database is billed to the Cloudflare account (self-serve or enterprise), with Cloudflare credits (startup programme, committed spend) redeemable against PlanetScale usage — an instance of patterns/unified-billing-across-providers applied to the storage tier (companion to the AI-tier instance from 2026-04-16's AI Platform unification post).
Customer code in Workers talks to the database through a Hyperdrive binding — same shape as Cloudflare-native bindings, no separate SDK.
Underlying cluster / pricing / feature set is standard PlanetScale — Cloudflare is a provisioning + billing aggregator, not a repackager.

(Source: sources/2026-04-16-cloudflare-deploy-postgres-and-mysql-databases-with-planetscale-workers.)

The Cloudflare integration is plumbed so the customer "get[s] the exact same PlanetScale database developer experience" — access to the same PlanetScale SKUs, pricing, and all PlanetScale features including query insights, AI tooling, and branching.

Timeline on this wiki¶

September 2025 — Cloudflare × PlanetScale partnership initially announced (referenced but not separately ingested).
2026-04-16 — Cloudflare dashboard provisioning + Cloudflare-billed rollout announced; "next month" ship target for Cloudflare-billed flow; auto-placement via DB-region-aware placement hints named as forward-looking.

Seen in¶

sources/2026-04-16-cloudflare-deploy-postgres-and-mysql-databases-with-planetscale-workers — primary introduction. Canonical instance of a partner managed-database integration behind Hyperdrive on Workers.

Caveats / gaps¶

No internal architecture disclosed. PlanetScale's own storage engine, MVCC semantics, replication topology, failover behaviour, regional availability, and Postgres- compatibility caveats (vs vanilla Postgres) are not covered by the Cloudflare-integration post; they live in PlanetScale's own docs.
Starter price is pass-through. The $5/month figure is PlanetScale's pricing, not a Cloudflare-subsidised rate.
MySQL side less-illustrated on the Cloudflare post. Both engines are named co-equal, but every code snippet in the Cloudflare post is Postgres.

systems/vitess — sharding substrate under PlanetScale MySQL.
systems/postgresql / systems/mysql — the two engines PlanetScale hosts.
systems/hyperdrive — connectivity vehicle between Workers and PlanetScale.
systems/cloudflare-workers — consumer of the integration.
patterns/partner-managed-service-as-native-binding
patterns/unified-billing-across-providers
companies/cloudflare