--- title: "How Mindvalley Minimizes Time-To-Launch With Neon Branches" url: https://daily.dev/posts/how-mindvalley-minimizes-time-to-launch-with-neon-branches-qsi1fxmme source_url: https://neon.com/blog/how-mindvalley-minimizes-time-to-launch-with-neon-branches type: article source: "Neon" published: 2026-07-09T06:58:06.870Z updated: 2026-07-09T07:01:32.498Z tags: ["cicd", "postgresql"] reading_time: 6 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How Mindvalley Minimizes Time-To-Launch With Neon Branches **[Neon](https://daily.dev/sources/neontech)** · 6 min read · 0 upvotes · 0 comments ## Summary 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. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#cicd](https://daily.dev/tags/cicd), [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/how-mindvalley-minimizes-time-to-launch-with-neon-branches-qsi1fxmme)