SaaS Starter with Auth + Billing
Ready-to-ship Next.js B2B SaaS blueprint with org auth, feature flags, metering, and Stripe billing.
Original user prompt
Create a B2B SaaS starter with organization auth, role-based permissions, usage metering, Stripe subscriptions, and admin audit trails.
Advanced outputs (CLAUDE.md, .cursorrules, Master Prompt)
Recommended Tech Stack
Core stack: - Next.js App Router + TypeScript strict. - Auth: Clerk organizations or Auth.js + custom org tables. - DB: Postgres + Prisma. - Billing: Stripe Billing + customer portal. - Jobs: Upstash QStash for metering aggregation. - Caching: Redis for usage dashboards. Reasoning: - Mature auth and billing primitives reduce launch risk. - Prisma + Postgres provides clear migration path as product evolves. Alternatives: - Polar billing if Stripe is not available in target market. - Drizzle instead of Prisma for SQL-first teams.
🚀 Submit this blueprint to the Community Gallery
Your submissions are protected: anti-bot reCAPTCHA, daily anti-flood limits, data deleted after 14 days, zero account required. Only title + JSON are used for the gallery. Privacy policy: vibemeta.app/privacy
Why this prompt works
Developers searching for a practical Next.js blueprint usually need concrete SaaS scaffolding, not theory. This prompt forces RBAC, billing, and metering details that are typically missed, reducing expensive rework after launch.
How to use it in your project
- Replace metric names and quota logic with your domain metrics.
- Keep webhook idempotency design unchanged.
- Start from MVP scope; add addons only after stable billing reconciliation.
- Use the policy helper pattern for every new protected route.
Share this page or copy the full JSON to reuse the blueprint quickly.