Vibekit

VibeKit Documentation

Learn how VibeKit works, how to run it locally, and how to build your SaaS.

Build your site with an AI coding agent and the skills included in this template. Start with Vibe code your site, then use the complete skill catalog for each change.

VibeKit is a complete Next.js foundation for building production web applications and SaaS products. It gives you a fully typed monorepo with authentication, database tools, payments, email, file storage, internationalization, and administrative controls.

The docs UI is Fumadocs. Use the official Fumadocs docs for Markdown, MDX components, layouts, and search. This site documents how VibeKit uses Fumadocs and how the rest of the template works.

Official Fumadocs

Do not copy those guides into this repo. Link to them, then document only VibeKit-specific paths and behavior.

What is included

VibeKit comes with preconfigured packages and applications that work together out of the box:

  • Next.js & React: Modern App Router setup with server components, TypeScript, and Tailwind CSS.
  • Better Auth: Fast, secure authentication with passwords, emailed one-time codes, and session management.
  • PostgreSQL & Prisma ORM: Type-safe database queries, schema validation with Zod, and migration workflows.
  • tRPC API Layer: End-to-end type safety between client components and backend procedures.
  • Multi-Tenancy & Teams: Team creation, member invitations, and role-based permissions (OWNER and MEMBER).
  • Payment Processing: Checkout, signed webhook verification, and mock payments for local development.
  • React Email: Transactional emails with console, Resend, Postmark, Cloudflare, Plunk, and Nodemailer.
  • S3 Storage: Upload avatars and files to AWS S3, Cloudflare R2, MinIO, or the built-in mock adapter.
  • Fumadocs: Fast, search-ready documentation powered by MDX.
  • Playwright Testing: Headless browser smoke tests for local development and CI.

Clean framework boundaries

VibeKit keeps core infrastructure in modular packages/* and application routes in apps/web. You can customize every feature without rewriting shared logic.

Next steps

  1. Quickstart Guide — create .env, apply the checked-in migration chain, and start the development server.
  2. Configuration — set environment variables and config.ts.
  3. How Fumadocs is wired — content folder, catch-all route, search, and LLM endpoints.

On this page