Ship a SaaS
A complete stack for a paid product with users, subscriptions, transactional email, analytics, and a polished UI. Every repo here is one we would actually ship with — the boring choices that compound.
A multi-tenant SaaS with paid signup, dashboard, billing, and email — all on one stack.
Framework + UI
3 repos
App router + server actions + ISR — the default for shipping fast in 2026.
The React framework. ~128k stars. App Router is the bet — server components, server actions, edge runtime. 2026 sentiment is mixed: people l…
Copy-paste components built on Radix. You own the code, you own the look.
The default for Next.js builders in 2026. Not a dependency — you copy components into your codebase and own them forever. Built on Radix pri…
Accessibility primitives under the hood. Use directly when shadcn is overkill.
The accessibility primitives shadcn/ui is built on. If shadcn is too opinionated drop down one level and use these directly. WAI-ARIA compli…
Auth
2 repos
The new default — replaces NextAuth in 2026. Type-safe, plugin-driven.
The most flexible modern auth library for TypeScript stacks in 2026. Plugin ecosystem for 2FA, phone OTP, organization roles, audit logs. Sa…
For when you want minimal magic — Lucia gives you raw building blocks.
Note: Lucia announced deprecation in 2024 — the maintainer is sunsetting it in favor of writing your own. Still useful as a learning referen…
Database + ORM
2 repos
Postgres + Auth + Storage + Edge Functions. The fastest path to a backend.
Postgres + Auth + Storage + Realtime + Edge Functions in one open-source platform. ~73k stars. The fastest way to ship a backend in 2026 for…
SQL-first ORM with codegen. Pairs cleanly with Supabase Postgres.
TypeScript-first ORM with SQL-like syntax. ~25k stars. Lighter than Prisma, zero codegen step, faster cold starts on serverless. Becoming th…
- Payments (India + global)2 repos
- Forms + Validation2 repos
- Email1 repo
- State + Data2 repos
- Analytics3 repos
- Animation + polish2 repos
- Scheduling + workflows2 repos
- Search inside your app2 repos
- CMS for editorial content1 repo
- Tooling5 repos
- Icons1 repo
Unlock with lifetime membership.
Pay once. Full directory unlocked forever. No renewals, no surprise charges.
See pricingThe 4-step AI workflow
The AI agents are good at code. They're bad at deciding what stack to use. This bundle does the second part. You bring the agent.
- 1Ideate with ChatGPT or Claude.ai (web)Paste your idea: “I'm building ship a saas. Help me sharpen the product spec — features, edge cases, MVP scope.” Iterate for 10-15 minutes until you have a clear one-page brief.
- 2Pick your coding agentFor this kind of bundle, we recommend Claude Code — Sonnet 4.6/4.7 handles full-stack multi-file reasoning best. See the install guide → Cursor and Codex are also great; pick the one you already pay for.
- 3Feed this bundle to the agentOpen Claude Code / Cursor / Codex in an empty folder, then paste:
I'm building ship a saas. Use this bundle as the source of truth for the stack: https://stackpicks.dev/build/ship-a-saas Brief from my product spec: [paste your brief from step 1] Follow the bundle order strictly: 1. Framework + UI 2. Auth 3. Database + ORM 4. Payments (India + global) ... Stop and confirm with me after each layer.
- 4Wire one layer at a time, commit between eachDon't let the agent install everything before the first
git commit. One layer = one commit. Catches drift early, easy rollback.
Beyond the bundle
- 1Ship the boring version first. The bundle above is the maximalist list. For an MVP, start with 60% of these and add the rest when real users ask.
- 2Deploy early. Push to Railway / Vercel after layer 02 (auth) — not after layer 09. Production breaks differently than localhost.
- 3Read CLAUDE.md / .cursor/rules in this repo for the project conventions your AI agent should follow.
- 4Iterate on the take. If a repo here doesn't fit your specific use case, tell us — contact — and we'll add a better one within 60 minutes.