Codapult
DocsBlogPricingPluginsDemo
Get Codapult
Logo

Build your SaaS with AI. Keep the architecture under control.

Get Codapult

Product

  • Pricing
  • Architecture
  • Modules
  • AI platform
  • Plugins

Developers

  • MCP
  • CLI
  • Documentation
  • Launch your SaaS
  • Build a B2B SaaS

Resources

  • Blog
  • FAQ

Connect

  • Contact
  • GitHub

Compare

  • SaaS template comparison
  • Codapult vs Supastarter
  • Codapult vs Makerkit
  • Codapult vs ShipFast
  • Codapult vs SaaSBold
  • Codapult vs Gravity
  • Codapult vs Nextbase
  • Codapult vs BuilderKit

Featured on

Codapult on LaunchNestCodapult on LaunchNestbetterlaunch.cobetterlaunch.coFeatured on LaunchBuffFeatured on LaunchBuffCodapult on PeerPushCodapult on PeerPushFeatured on LaunchItFeatured on LaunchIt
© 2026 Codapult·All rights reserved·Privacy Policy·Terms of Service
Full source code · One-time purchase · Self-host anywhere
All articles

Getting Started

  • Introduction
  • Quick Start
  • Your First 30 Minutes
  • Project Structure
  • License and Permitted Use
  • Starter Profiles and Recipes
  • Product Recipes

Configuration

  • Environment Variables
  • App Configuration
  • Which Modules Should I Enable?
  • Provider Matrix
  • Capability Coverage

Database

  • Database and Provider Guide
  • Database
  • Migrations

Authentication

  • Authentication
  • OAuth Providers
  • Two-Factor & Passwordless
  • Enterprise SSO (SAML)

Ai

  • AI Runtime Architecture and Evals
  • AI Features
  • Streaming Chat
  • RAG and Semantic Search
  • Quotas and Memory

Teams

  • Teams & Organizations
  • Permissions & RBAC
  • SCIM Provisioning

Security

  • Data Retention Policy
  • Security

Deployment

  • Enterprise E2E Evidence
  • Enterprise Production Readiness
  • Deployment, Backup, and Restore Runbook
  • Deployment
  • Troubleshooting

Payments

  • Payments & Billing
  • Stripe Setup
  • LemonSqueezy Setup
  • Polar Setup
  • Payment Webhooks

Api

  • API Layer
  • tRPC
  • GraphQL

Email

  • Email
  • Email Templates

Infrastructure

  • Infrastructure
  • Self-Hosting
  • File Storage
  • Docker
  • Background Jobs
  • Terraform & Pulumi
  • Kubernetes

Ui

  • UI & Theming

I18n

  • Internationalization

Content Management

  • Content Management

Admin

  • Admin Panel

Monitoring

  • Analytics & Monitoring

Modules

  • Module Architecture
  • Waitlist
  • Audit Log
  • White-Labeling
  • Workflow Automation
  • A/B Testing
  • Welcome Page
  • Referrals
  • GDPR Export and Deletion
  • Promotions
  • Outgoing Webhooks

Plugins

  • Plugin System
  • CRM Plugin
  • Helpdesk Plugin
  • Email Marketing Plugin

Upgrading

  • Upgrading Codapult

Developer Tools

  • AI Agents & IDEs
  • MCP Server
  • Testing
  • Build Your First Feature with Codapult MCP
  • How Guard Blocks an Architectural Regression
Getting Started

Your First 30 Minutes

Go from a fresh Codapult project to a running, verified SaaS foundation.

This is the shortest path from the private template repository to a project you can start changing with confidence. The creator already runs the setup wizard; do not run setup a second time unless you cloned the template manually.

0–5 minutes: create the project

Use the access granted to your GitHub account:

npx @codapult/create my-app
cd my-app

The creator performs a history-free clone, runs the setup wizard, and installs dependencies. The result is an ordinary Git repository that you own and can customize.

5–10 minutes: configure the local environment

For a local development database, use SQLite through the default Turso/libSQL adapter:

cp .env.example .env.local

Set at least:

TURSO_DATABASE_URL=file:local.db
BETTER_AUTH_SECRET=replace-with-at-least-32-random-characters
STRIPE_SECRET_KEY=sk_test_replace_me

Generate a secret with openssl rand -base64 32. If you only want to inspect the public site, set APP_MODE=landing; the full app setup is not required for that mode.

10–15 minutes: create the schema and sample data

pnpm db:push
pnpm db:seed

The seed creates local demo accounts, organizations, subscriptions, activity entries, feature flags, and promotions. It is for development and demos, not production data.

15–20 minutes: run the app and checks

pnpm dev

Open http://localhost:3000, then run the project diagnostics in a second terminal:

npx @codapult/cli doctor
npx @codapult/cli env check

Use the seeded credentials printed by pnpm db:seed to inspect the dashboard. Run pnpm test before making the first broad change.

20–25 minutes: connect your AI coding client

The generated project contains .cursor/mcp.json. In Cursor, enable the codapult MCP server and ask it to inspect the project before generating code:

Inspect this Codapult project context, active providers, enabled modules, and database conventions. Then propose the smallest implementation for a saved reports feature.

The MCP server can inspect the project, run checks, generate pages/actions/API routes, and report schema or environment drift. Review mutation plans before applying them.

25–30 minutes: establish architecture control

Guard is included in the Codapult CLI workflow:

npx @codapult/cli guard init
npx @codapult/cli guard propose
npx @codapult/cli guard verify --json

Review proposed rules before approving them. Use TypeScript, ESLint, tests, and Guard together: Guard protects project-specific architecture while the rest of the toolchain verifies types, style, and behavior.

What to do next

  • Build your first feature with Codapult MCP
  • Choose modules
  • Starter profiles and recipes
  • Upgrading Codapult
Quick StartProject Structure