File
SMF·PLANETSCALE
Received on
31.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·PLANETSCALE

Can a prompt replace PlanetScale?

Hosting & deployment — application hosting and backend platforms

Not yet Verdict recorded on 28.09.2026 · Verified on 31.07.2026
Price
$39/moSource: planetscale.com · Checked on July 31, 2026
Per year
$468
Build time
One sitting
Votes
0 votes
YesAlmostNot yet (checked)

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: infrastructure scale, operations, and reliability
Exhibit Q Questions

Verdict

PlanetScale's actual signature capability, changing a live MySQL table's schema without locking it or causing downtime, is a genuinely hard distributed-systems problem PlanetScale solved by building on Vitess, YouTube's own MySQL-scaling layer. The honest DIY substitute uses gh-ost, an existing open-source tool built for exactly this (originally from GitHub), rather than reimplementing online schema change from scratch.

Exhibit B — What you lose

Exhibit A — The prompt

Received on31.07.2026
Build a workflow for running MySQL schema migrations without locking tables, using gh-ost, an existing, mature open-source tool originally built at GitHub for exactly this, rather than attempting to reimplement online schema change, which is genuinely hard distributed-systems work. Set up a self-hosted MySQL instance (Docker Compose is fine for personal use). Install gh-ost and write a small wrapper script that takes a migration SQL statement, runs it through gh-ost's triggerless copy-and-swap approach (it copies the table's data in the background, tracks changes with binlog streaming, then does a fast atomic swap), and reports progress. Track applied migrations in a metadata table so you know what's been run. Add a dry-run mode, which gh-ost supports natively, so a migration can be validated before actually running. Do not attempt to build Vitess-style horizontal sharding, a deploy-request review workflow, or managed automatic backups — those are out of scope; this wraps gh-ost for one database, not PlanetScale's actual multi-tenant infrastructure. Requires hosting for the MySQL instance; no other external service needed, since gh-ost itself is free and open source.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 Vitess-level horizontal sharding at massive scale
  • B.2 a polished branching and deploy-request workflow for schema changes
  • B.3 managed infrastructure and automatic backups
  • B.4 built-in query insights and performance analytics

Prior art

Exhibit C — Why people still pay: infrastructure scale, operations, and reliability

gh-ost solves the online-migration problem for one database; PlanetScale's actual product is running that reliably at scale across many customers' databases, plus the deploy-request workflow that makes schema changes reviewable like code.

Questions

Does this actually avoid locking the table during migration?

Yes — that's the whole point of using gh-ost, which is a mature, real tool built specifically for online schema changes, not a homemade approximation.

Do I get PlanetScale's branching and deploy-request workflow for schema changes?

No — that's real product design PlanetScale has built on top of Vitess. This build gives you a safe migration mechanism, not a reviewable branching workflow around it.

Does it scale the way PlanetScale (via Vitess) does?

No — this runs against a single MySQL instance. Vitess-style horizontal sharding across many database shards is genuinely enterprise-scale infrastructure this build doesn't attempt.

What does it cost to run?

Hosting for the MySQL instance — typically a few dollars a month, since gh-ost itself has no licensing cost.

Receipt

Already built this yourself?