Cookbooks
ShipVeryFast ships with Supabase, Stripe and Mailgun wired in, but none of them are load-bearing. Every provider sits behind a thin seam, so swapping one is a contained change to a handful of files, not a rewrite. These cookbooks walk each swap end to end.
Why the swaps stay small
libs/pricingPlans.ts. Email goes through one send helper. Auth providers are registered in a single NextAuth config. Database access runs through the Supabase clients and the typed models in models/. Change the seam, not the app.Payments
Stripe is the default. If you want a merchant of record to handle sales tax and VAT for you, swap it for Paddle or Lemon Squeezy. Read the billing model first: whichever provider you pick, the webhook stays the source of truth.
Transactional email ships on Mailgun. Moving to Resend is mostly a change of client and credentials, the templates and call sites stay as they are.
Authentication
Google OAuth and magic links are wired out of the box. Adding a provider such as GitHub is a few lines of config; the same guide covers replacing NextAuth with Clerk or Auth0 if you would rather buy that layer.
Database
Supabase gives you Postgres with Row Level Security and auth in one place. Swapping the database covers moving to another Postgres host such as Neon, and adding Drizzle if you prefer an ORM over the Supabase client.
All cookbooks
Looking to build on top of what ships rather than replace it? The recipes add features the house way.