Talk about your next project
PlanetScale case study

The lesson

Make the risky operational path the story, not just the before-and-after result.

The move

The page opens with the title “Moving Vendora from Supabase to PlanetScale,” a Gordon MacMaster quote, and a sidebar naming the reasons: “Best cost and performance for their workload,” “Per-millisecond compute billing,” “Storage that autoscales with the data,” and “Previous database: Supabase.” It then explains “About Vendora,” “Why Vendora left Supabase,” and “Why PlanetScale” before getting into the migration sequence under “Getting the cutover order right.” The middle of the story walks through “Rehearsing on staging” and “The production migration,” including sequences and the Drizzle migration journal, then closes with “Working with the PlanetScale team,” “The results,” and a short “Get started” call to action.

Why it works

  • Our readThe page names the previous database at the top, so readers with the same migration question know the story is relevant immediately.
  • Our readThe cutover sequence makes the technical risk concrete and shows why the order mattered for offline sync.
  • Our readThe staging and production issues make the story more credible because the migration did not read like a perfect vendor script.

What not to copy

Don't copy Vendora's Supabase setup, offline sync architecture, Drizzle details, or Neki roadmap. Keep the structure of a named prior system, the operational risk, the rehearsal, the production problems, and the final state.

More from PlanetScale

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.