Mindvalley, a global personal growth platform with 11 million users, uses Neon's database branching to speed up their non-production workflows while keeping production on Google CloudSQL. Their setup involves nightly data syncs from CloudSQL to a main Neon branch via GitHub Actions (Neon Twin), from which hundreds of ephemeral child branches are instantly created per PR. This eliminated pain points like shared database concurrency issues, multi-hour E2E test setup times, and manual seed file maintenance. They chose Neon over Supabase because Neon branches replicate actual data instantly, avoiding seed file dependency. The Neon Twin workflow is outlined step-by-step for teams wanting to replicate this approach.

6m read timeFrom neon.com
Post cover image
Table of contents
How Mindvalley uses NeonTheir database branching workflowThe problem with dev/test on other managed databases: A closer lookBuild your own Neon Twin for dev/test