Profiles
Profiles are named setup configurations for common product shapes. They select the initial modules and providers; the generated project remains a normal Codapult source repository.
| Profile | Use it for |
|---|---|
saas | A general-purpose SaaS with the standard Codapult foundation |
ai-saas | An AI product with chat, agents, batch processing, playground, and RAG |
b2b-saas | A team product with organizations, SSO, branding, audit, and operational features |
ai-chatbot | A focused AI chat product with tenant context, quotas, and audit-ready events |
marketplace | A marketplace with organizations, Stripe Connect, webhooks, audit, and branding |
internal-tool | An internal product with organizations, workflows, analytics, audit, and reports |
content-saas | A content/productivity product with blog, workflows, onboarding, and analytics |
marketing | A marketing site without authentication or dashboard modules |
demo | A configured demo environment |
Apply a profile during setup:
npx @codapult/cli setup --preset ai-saas
The setup command writes .env.local, applies the selected module configuration, and creates .cursor/mcp.json.
Recipes
Recipes describe the short workflow after a profile is selected:
npx @codapult/cli recipe list
npx @codapult/cli recipe show b2b-saas
Apply a recipe to the current project:
npx @codapult/cli recipe apply ai-saas
pnpm install
pnpm db:push
pnpm dev
Recipes cover the general profiles and product shapes above. Use setup --preset for custom combinations such as:
npx @codapult/cli setup --preset 'ai-saas;enableRAG=false;enablePlayground=false'
Choosing a profile
- Start with
saaswhen the product shape is not decided yet. - Use
ai-saaswhen AI is part of the product surface from the beginning. - Use
b2b-saaswhen organizations, enterprise identity, and account-level operations are core requirements. - Use
marketingfor a public site that does not need the application shell.
Profiles are a starting point. After setup, review the generated configuration, environment values, migrations, and module dependencies before deploying.
For the product-oriented workflow and first feature to build in each shape, see Product Recipes.