LoginSign Up
← Back to all sparks
PlanetScale logo

PlanetScale

INFRA · APISDEVOPS
Velocity0.0

MySQL-compatible serverless database platform

planetscale.com ↗

PlanetScale is building out Postgres while making every control reachable without the dashboard.

databasepostgresapi-coverageterraformmcpobservability
◆Current state
The Postgres line carries the new capability: vectorscale extension support, storage configurable at database creation, out-of-memory alerts by both email and webhook, a customisable log line prefix, a Discovery Tool for evaluating existing databases, and updated pricing for private connection traffic. Database Traffic Control introduced resource budgets and has since gained warning thresholds and CLI management. The surface work is constant — API endpoints for backup policies, maintenance schedules, schema recommendations, deploy-request storage checks and invoice status, a Terraform provider at v1, and an Insights-only MCP server.
◆Where it's heading
PlanetScale is doing two things at once: closing the gap between its Postgres offering and its MySQL heritage, and making every operation scriptable. The API, Terraform and MCP work share a single goal — nothing should require the dashboard — and the schema-recommendations feature landing simultaneously as a REST endpoint and an MCP tool is the clearest statement of it. Traffic Control is the exception, launched as a named product surface and then immediately given the same CLI and threshold treatment.
◆Prediction
Expect the remaining Postgres parity items and more MCP tools mirroring existing REST endpoints, following the schema-recommendations pattern where both arrived together.

◆Recent moves

  1. 3mo ago

    Query Insights negated search terms

    Query Insights search accepts negated terms, so a prefix of ! excludes matches — !indexed:true surfaces unindexed queries directly. A small syntax addition that makes the diagnostic path much shorter, and it works across both Postgres and Vitess.

    View source ↗
  2. 3mo ago

    New GCP region: Eemshaven, Netherlands

    Postgres and Vitess databases can now be deployed in the Eemshaven GCP region. Routine footprint expansion, relevant mainly to teams with EU data residency requirements.

    View source ↗
  3. 3mo ago

    Introducing Database Traffic Control™: resource budgets for your Postgres query traffic.Learn more

    ⚡ SPARK

    Database Traffic Control introduces resource budgets for Postgres query traffic, later paired with warning thresholds ahead of enforcement. It gives the database a way to ration itself, which is the control large teams have historically had to build outside it.

    View source ↗
  4. 3mo ago

    Configure Postgres storage at database creation

    Storage can be configured when a Postgres database is created rather than adjusted afterwards. Part of the steady closing of gaps between the Postgres offering and the older Vitess one.

    View source ↗
  5. 4mo ago

    Sign-up page fragment (no release content)

    A two-word capture of the sign-up call to action. A crawl artifact rather than an entry.

    View source ↗
  6. 4mo ago

    Insights-only MCP server

    A variant of the MCP server that exposes Insights data and schema recommendations while withholding query execution. It is a deliberate scoping decision: agents get to read and advise without being handed the ability to run statements against the database.

    View source ↗