A ready-to-use template for your next SaaS project. Built with React, Tailwind and Shadcn UI. With toggleable features and modular architecture.
Next.js 16
This repository is configured so you can jump in with your favorite coding agent and IDE and start shipping immediately.
Claude Code
Codex
Gemini
GitHub Copilot
Cursor IDE
Windsurf IDE
VS Code
Terminal / CLI
Antigravity IDE
Codex App
Each layer combines a concrete technical capability with the business outcome it unlocks for teams shipping SaaS products.
01
Routes are defined in `page.info.ts` files and generated into a centralized routing config, with typed params and search handling across links and route builders. Generated route helpers stay aligned with locale routing and menu metadata, so path updates propagate safely.
You reduce broken links and maintenance churn as the product grows, while coding agents can update navigation reliably without scanning the entire codebase.
02
Core platform switches are centralized in `src/config/app.ts` through a single `Config` object that controls ready-made modules like billing scopes, rate limiting, API key behavior, auth/session policies, UI layout variants, and cookie banner options.
You can quickly enable, disable, or tune built-in capabilities from one file instead of rewriting features, which accelerates launches and reduces risky code changes.
03
oRPC procedures stay type-safe end to end, can be exposed as REST routes with `.route(...)`, and support API key auth via `acceptApiKey` plus generated docs endpoints. The same contracts are reused across hooks, callers, and docs so integrations stay consistent.
Integrations ship faster with fewer frontend/backend mismatches, and partners can consume stable API surfaces without ad-hoc implementation work.
04
Protected flows use `authProcedure`, `requireRole`, session checks, and built-in unauthorized/forbidden interrupts for consistent access control behavior. Role enforcement is shared across layouts and procedures so security and UX responses stay aligned.
Security defaults are already in place, so teams can launch protected functionality without spending months building identity and permission infrastructure.
05
The `/onboarding` page is restricted to `USER` role, uses a two-step `StepperOnboarding` flow (profile + source feedback), and redirects completed users to dashboard when `onboardingCompleted` is true. Forms, validation, and completion updates are already wired through auth hooks and shared stepper components.
New users are guided through first-use setup in a structured flow, so activation starts fast and teams capture early profile and acquisition data without building custom onboarding logic.
06
Dashboard tours are built with Onborda using centralized step definitions in `src/config/tours.ts`, a `startTour` dashboard trigger, and optional cross-page navigation between highlighted screens. Welcome notifications can launch the guided flow right after signup or onboarding, so feature discovery is wired into the product instead of bolted on later.
After users sign up or finish onboarding, you can walk them through important features and pages in context, increasing activation without relying on separate docs, videos, or manual customer success follow-up.
07
The template includes organization switching, role-based member management, and invitation lifecycle flows for multi-tenant team collaboration. Membership, invitation, and active-organization session state are already handled by dedicated routers and hooks.
B2B collaboration works from day one, so customers can onboard teammates, assign access, and start operating inside shared workspaces immediately.
08
The calendar module ships with day/week/month views, event CRUD flows, participant metadata, and status-aware rendering backed by dedicated calendar routers, hooks, and UI components. It is already integrated with role-aware dashboard routes and reusable modal workflows.
Teams can plan work, coordinate meetings, and keep everyone aligned on upcoming activities without building a scheduling system from scratch.
09
User-scoped and organization-scoped subscriptions are separated (`USER_BILLING` and `ORGANIZATION_BILLING`) and can run independently or at the same time. Both billing paths are guarded and connected to shared plan and usage operations without coupling the two scopes.
You can monetize individuals and teams in parallel, enabling pricing experiments and packaging changes without reworking billing architecture.
010
Account flows include provider linking/unlinking, email updates, password changes, and account deletion with auth-safe handling. Profile procedures and settings forms are already wired with validation and mutation hooks for predictable behavior.
Customers can self-serve common account operations, lowering support load and improving trust in account security and control.
011
Settings include notification preferences and newsletter subscription controls, while public contact requests are captured and managed in admin tools. Preference updates, unsubscribe flows, and contact-request storage are already modeled end to end.
You get built-in communication loops for acquisition and retention instead of stitching forms and preference systems together later.
012
React Email templates are ready for transactional and campaign messaging, with provider transport support for both Resend and Nodemailer. Rendering and delivery switching are centralized so transactional and bulk workflows share the same infrastructure.
Operational messaging is launch-ready, so onboarding, product updates, and lifecycle communication can go live without rebuilding email infrastructure.
013
Admin modules include usage and page-view analytics plus user management screens for operational control across the application. Analytics queries, chart components, and admin routes are grouped in dedicated features and RPC routers.
Teams can monitor product traction and manage accounts from a single control surface, improving decision speed and reducing blind spots.
014
Locale-based routing and translation dictionary conventions are built in, making multilingual pages and validation messaging consistent. Typed translation keys and locale-aware navigation utilities keep links and content synchronized across languages.
Expanding to new markets is much easier because language support is part of the architecture, not a late-stage rewrite.
Two lifetime options built for different workflows: buy a direct code snapshot as guest, or unlock private repository access with all future updates.
That estimate comes from AI-agent leverage plus engineering expertise applied to an optimized code structure, best-practice patterns, and feature-ready modules you can build on immediately.
Optimized structure
Docs-first architecture, typed routes, and clear module boundaries reduce setup churn from day one.
Best-practice patterns
Billing, auth, RPC, i18n, and UI conventions are already organized in ways that scale cleanly.
Feature-ready foundation
You start from real product flows instead of a blank starter, which cuts time-to-shipping substantially.
One-time payment
Pay once and keep your ownership rights without recurring billing surprises.
Lifetime updates
Repository option includes every future release, fixes, and improvements.
Instant checkout
Go from checkout to working code in minutes, not days.
One-time payment, no subscription
Includes current template code snapshot
Guest checkout supported. Use any email to receive delivery and claim access later.
Clone the private repository anytime
All future releases included forever
Repository access requires sign in with a linked GitHub account for access management.
30% OFF for the first 30 customers with code LAUNCH
