Overview
Fast Unicorn is a starter kit, not a finished SaaS. Auth, payments, email, i18n, marketing pages, and a dashboard shell are pre-wired so you spend days on your product—not weeks on boilerplate.
What you are buying
You get a type-safe Next.js foundation with env validation, sensible defaults, and clear extension points. Sample dashboard data is illustrative UI to delete or replace as you connect your own tRPC queries and Stripe data.
Key features
Everything you need to configure and launch your own SaaS—not a turnkey business in a box.
Authentication
Google OAuth and email/password (Credentials) via NextAuth v5, with protected routes and session helpers ready to extend.
Payments
Stripe checkout for subscriptions and one-time payments, webhook handler, and subscription state synced to your database.
UI Components
shadcn/ui primitives, marketing sections, and a dashboard shell you customize—not a locked theme.
SEO and i18n
next-intl (en, es, zh), per-route metadata helpers, sitemap, robots.txt, and JSON-LD foundations.
Email System
Resend + React Email with verification, password reset, and purchase templates—configure your sender in site.ts.
Developer experience
tRPC 11, Prisma 7, Zod env validation, and unicorn-mcp (npm) as an optional IDE copilot for the template.
Built-in integrations
These are included and configured through env + src/config/site.ts—not black-box magic:
- NextAuth v5: Google OAuth + Credentials (email/password).
- Stripe: checkout, webhooks, subscription tier in the database.
- Prisma + PostgreSQL: schema, migrations, type-safe client.
- Resend + React Email: transactional templates you own.
- next-intl: locale in the URL path (en, es, zh).
- unicorn-mcp (beta): optional MCP server for Cursor and other IDEs.
Analytics, file storage, and rate limiting are roadmap items—not part of v1.
What is configurable
Most customization happens without rewriting core routes:
- Brand identity:
src/config/site.ts(name, logos, Resend sender, social links). - Marketing copy:
messages/<locale>/landing.json(hero, pricing, FAQ, footer). - App UI strings:
messages/<locale>/auth.json,dashboard.json,navbar.json, etc. - Legal pages:
messages/<locale>/legal.json. - Dashboard sections:
src/app/[locale]/dashboard/_components/(replace sample data with your queries). - Environment:
src/env.js(validated with Zod).
A practical rule
Set env vars and site.ts, then swap copy in messages/, then extend dashboard and tRPC
routers. That order matches how the template is meant to be adopted.
Ready to continue?
Follow these guides to move through setup in the right order.
Installation
Clone the repository, install dependencies, and get the project running on your machine.
Environment setup
Configure the required variables so auth, email, payments, and app defaults can work correctly.
Project structure
Understand how the codebase is organized before you start editing deeper parts of the app.
First customization
Apply your branding, content, and assets so the template already feels like your product.
Useful links: