Benefits

What It Does

Creatorem SaaS Kit gives you a production-ready monorepo baseline for web and mobile products with a unified data model, shared feature modules (kit/*), and repeatable setup workflows.

When To Use

• You want to ship a SaaS product quickly without rebuilding auth, settings, billing, i18n, and org primitives.
• You want a monorepo where product teams and AI coding agents can work from stable conventions.
• You want feature toggling through the CLI instead of manually pruning code.

Prerequisites

• Node.js >=20
• pnpm workspace workflow
• Docker Desktop (for local Supabase)

For which environments ?

Monorepo tools, paired with the React Native ecosystem, let you build web and native apps from one codebase.

For that reason, Creatorem SaaS Kit is designed for:

• Web applications powered by Next.js and React.
• Native applications powered by Expo and React Native.

Cross environment development

Why should I use a toolkit if AI can code for me ?

AI is a powerful tool and we are using it to improve our productivity. But we have to keep in mind that it useful only if a few use cases.

Long answer

An AI coding agent is trained on large datasets of code. During the training, the model will learn to generate code which will be the average of the code that have been used to train the model. So you won't get something perfect, but something close to the average.

With that in mind, it is easy to understand that AI should be used for simple and repetitive tasks only. If you need to build complex logic or design system, human is still the best.

Short answer

AI is nice to build simple MVPs, but it is impossible to build such easy to maintain, powerful and scalable applications with AI. People who say the opposite are fools.

Our mission

The goal is to deploy applications as fast as possible. This includes :

• you new projects
• existing applications

For that reason, all packages and the documentation are designed to easily implement features into new applications.

How To Use

Start from CLI scaffolding or from this repository, then keep your product-specific logic in apps while reusing kit/* as the shared capability layer.

pnpmnpmyarnbun
pnpm dlx @creatorem/cli create my-saas
Copy

MCP Context

Copy to Clipboardcapability: product_overview
entrypoints:
  - README.md
  - cli/src/cli.tsx
  - kit/
inputs:
  - selected_apps
  - selected_features
outputs:
  - monorepo_with_feature_set
constraints:
  - architecture centered on kit/* reusable modules
  - apps consume kit APIs rather than reimplementing core logic
side_effects:
  - creates or reshapes workspace structure

Agent Recipe

1. Read README.md and cli/src/cli.tsx to identify supported app and feature combinations.
2. Inspect apps/dashboard/config/* for real integration patterns.
3. Implement product changes by extending config and filters first, then pages/components.

Troubleshooting

• If features seem “missing”, verify what was selected through CLI manifests in .creatorem/.
• If behavior differs across apps, compare each app’s lib/init-*-filters.ts wiring.

Related

• Structure
• CLI
• Quickstart