LoginSign Up
← Back to all sparks
PlanetScale logo

PlanetScale

INFRA · APISDEVOPS
Velocity4.6

MySQL-compatible serverless database platform

planetscale.com ↗

PlanetScale ships Database Traffic Control to govern Postgres query loads — and a read-only MCP server for safe agent access.

postgrestraffic-controlmcp-servervitessresource-budgets
◆Current state
Recent PlanetScale releases cluster around three themes: a new resource-governance product called Database Traffic Control (with warning thresholds and CLI management), Postgres Postgres infrastructure work (storage configuration at creation, vectorscale extension support, deploy request storage check API), and AI integration plumbing (an Insights-only MCP server variant). The platform also added a GCP region in Eemshaven, Netherlands.
◆Where it's heading
PlanetScale's Postgres offering is moving past parity-with-Vitess functionality and into differentiated territory. Database Traffic Control is the standout — query-level resource budgeting addresses a long-standing operational pain point that no managed Postgres provider has framed quite this way. The Insights-only MCP server is a small but telling move: PlanetScale is shipping deliberately scoped agent endpoints rather than just exposing the full API to LLMs. Postgres feature breadth (vectorscale, storage controls) keeps closing the gap with Neon and Supabase.
◆Prediction
Expect Database Traffic Control to gain alerting and rollout-staged enforcement in the next quarter, plus deeper integration with Insights so customers can map costly queries directly to budget-violation events. More extensions on Postgres are likely (pgvector enhancements, tuning extensions). The MCP server pattern will probably grow into other scoped variants — schema-editing-only, ops-only — as PlanetScale formalizes how agents touch production databases.

◆Recent moves

  1. 1mo ago

    Query Insights negated search terms

    View source ↗
  2. 1mo ago

    New GCP region: Eemshaven, Netherlands

    Adds Eemshaven, Netherlands (gcp-europe-west4) as a new GCP region for both Postgres and Vitess databases. Continues PlanetScale's pattern of opportunistic regional expansion to follow customer footprints; useful for EU latency and data-residency cases.

    View source ↗
  3. 2mo ago

    Database Traffic Control: query-level resource budgets for Postgres

    ⚡ SPARK

    Database Traffic Control is now a real product — query-level resource budgets for Postgres traffic. It's the directional move in this slate, giving database operators per-query, burst, and concurrency limits as first-class governance primitives rather than ad-hoc connection pooling.

    View source ↗
  4. 2mo ago

    Configure Postgres storage at database creation

    PlanetScale Postgres now lets users configure storage at database creation rather than relying on defaults. Operationally welcome — sets the right baseline for capacity planning before workloads land — and a small parity bump versus the Vitess side.

    View source ↗
  5. 2mo ago

    Crawler captured navigation fragment (not a release)

    Crawler artifact — title is just '|Get started' with no body. Doesn't represent a release.

    View source ↗
  6. 2mo ago

    Insights-only MCP server

    An Insights-only variant of the PlanetScale MCP server is now available, exposing Insights and Schema Recommendations data without query-execution tools. The captured content also bundles several adjacent items — vectorscale support, Traffic Control warning thresholds, deploy-request storage check API, branch-deletion descendants, CLI traffic-control management, and Vitess maintenance APIs.

    View source ↗