Most SaaS boilerplates force you into a specific stack. Postgres or nothing. Clerk or roll your own. Stripe or bust. We think that's the wrong approach.
LaunchKit lets you choose your database (Neon, Supabase, or Firebase), your auth provider (Clerk, NextAuth, or Firebase Auth), and your payment processor (Stripe or Lemon Squeezy). Everything is swappable from the CLI at project creation time.
Under the hood, this works through adapter patterns. Each integration — billing, auth, database — has a clean interface. The Stripe adapter and the Lemon Squeezy adapter implement the same contract. Swapping one for the other doesn't touch your application code.
The benefit isn't just choice — it's future-proofing. When a new payment processor gains traction, we add an adapter. When a new auth provider launches, we add an adapter. Your application code stays the same. That's the power of designing for configurability from day one.