
LaunchSaas
Production code. Not tutorial code.
I've been building SaaS apps for the past 2 years. Every new project meant rewriting the same things: Stripe webhook handling, Supabase auth edge cases, RLS policies, CI/CD pipelines.
So I extracted those patterns into a boilerplate: LaunchSaaS (launchsaas.dev). It's live.
What it actually is:
14 packages of TypeScript code extracted from production apps I built — a creator analytics platform (~10K users), a productivity SaaS (~3K users), a prediction markets platform, an affiliate tracker, and a few others. The code in these packages was running in production before I pulled it out.
Packages included:
Auth (NextAuth + Supabase variants)
Stripe subscriptions + webhooks
Database patterns (PostgreSQL + RLS)
Multi-tenancy
Notifications (20+ channels)
Error handling + Sentry
Security setup (Semgrep, TruffleHog pre-commit hooks)
Testing helpers (Vitest + Playwright)
DevOps / GitHub Actions templates
File upload, frontend components
What it's not:
It's not a one-command starter app. You don't clone it and run npm dev and get a working app. It's patterns you copy into your project. The README for each package is thorough (900+ lines for testing alone), but you're integrating, not scaffolding.
What I want to know:
Is "patterns you copy into your project" useful or annoying? Do you want a runnable starter app instead?
$99 one-time - does that feel right, too high, too low?
If you looked at launchsaas.dev and left without buying, what was it?
Happy to answer anything. Roast welcome.
About
I got tired of rewriting the same Stripe webhook handler for the fourth time. Not because I didn't know how - because I kept starting from scratch instead of reusing what I'd already proven worked.

Comment