PlanetScale through Squiid

What PlanetScale is

PlanetScale is managed MySQL built on Vitess, the sharding layer that grew out of running MySQL at very large scale. Its signature workflow is schema changes as pull requests: you branch the database, apply the change on the branch, open a deploy request, and PlanetScale applies it to production without locking tables. Insights shows the slowest and most frequent queries, and sharding is available when one database stops being enough. Connections are pooled at the edge of the platform, so a serverless app that opens hundreds of short-lived connections does not exhaust the database.

For an AI-coded project the appeal is safety around migrations. Generated schema changes are the most common way an agent breaks production, and a workflow that reviews and applies them without downtime removes most of that risk. PlanetScale is also the natural choice when the code already assumes MySQL, for example an app that started on a PHP or Rails codebase, or a team with existing MySQL experience that does not want to relearn Postgres operational habits. Vitess also means the path from one database to many shards is a platform feature rather than a rewrite, which is a real consideration for anything that stores events or logs at volume.

Why connect it through Squiid

PlanetScale is on the Squiid roadmap. When it is connected, Squiid will provision the database, hold the connection credentials and expose the database and management API through https://api.squiid.io/v1/planetscale/... with Authorization: Bearer $SQUIID_API_KEY, with drivers working by base URL swap (gateway convention). Plan cost will pass through at the provider's listed price on your monthly Squiid invoice, usage will meter against prepaid credits, and connection strings will stop living in .env files where an agent can copy them into a log line.

• One account, one key, one bill, one dashboard. PlanetScale sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the PlanetScale credentials. Your code carries SQUIID_API_KEY, so DATABASE_URL, PLANETSCALE_TOKEN, PLANETSCALE_ORG, PSCALE_DB never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what PlanetScale costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned MySQL database on Vitess
• Branching and non-blocking deploy requests
• Query insights without a separate tool
• Provider pricing passed through on one invoice
• Credentials held by Squiid, not your repo

How to connect PlanetScale

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces DATABASE_URL, PLANETSCALE_TOKEN, PLANETSCALE_ORG, PSCALE_DB
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/planetscale/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

PlanetScale charges a monthly plan fee based on cluster size plus storage and additional usage, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of PlanetScale usage, with no markup and no per-request margin.

PlanetScale has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so PlanetScale usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: dump the database and restore it into a project in your own PlanetScale account; PlanetScale has no project transfer we are confident of. Squiid never owns your code, your schema or your domain, and the gateway speaks PlanetScale's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

PlanetScale through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on PlanetScale usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.