GenerateSaaSCLI
The generatesaas CLI scaffolds a project from the licensed boilerplate and keeps it current - init, auth, status, update, verify, and eject, all gated by your API key.
The generatesaas CLI scaffolds projects from the boilerplate and keeps them in sync afterwards. The template is never bundled in the package: commands that touch it send your API key to the version index, then stream a versioned tarball from cli.generatesaas.com.
Commands
Run lifecycle commands from a generated project root. status and update also accept --cwd <path>; eject must run from the project root.
| Command | What it does |
|---|---|
init | Scaffold a new project: verify access, collect options, activate a license, download the template, run generators, install deps, init git. |
auth | Save or replace the API key (verified before saving). auth --clear removes it. |
status | Print version, deploy target, database, and cache from .generatesaas/manifest.json, then check for a newer release. |
update | Refresh the bundled AI skills and the license token; if a newer version exists, stage it into .generatesaas/staging/ with a changelog. Your AI assistant then applies it, unattended, stopping only where a change needs your decision. |
verify [url] | Check whether a deployed site is legitimately licensed: licensed, revoked, leaked, ejected, or no license history. --file <path> checks many URLs at once. |
eject | Irreversibly sever every GenerateSaaS tie - manifest, license route, heartbeat, and AI skills. |
Access and storage
| Aspect | Detail |
|---|---|
| Key storage | ~/.generatesaas, file mode 0600, so later commands run unattended. |
| Key required | init, auth, status, update. verify and eject need none. An invalid key (401) re-prompts, or aborts under --yes. |
| Endpoint | https://cli.generatesaas.com, overridable with the GENERATESAAS_API_URL env var. |
| Delivery | A versioned tarball, downloaded on demand - the template source is never bundled in the CLI package. |
| Version pinning | Not supported. init scaffolds the latest release and update stages it, so always invoke via npx generatesaas@latest. |
update never mutates your code. It stages the new version re-shaped for your exact configuration - same architecture, payment provider, database, and feature flags - so everything it stages already applies to your project. Applying the diff is delegated to your AI assistant.
Explore
init
Every prompt, flag, and the generate-and-install pipeline.
update
How staging works and how your AI assistant applies a new version.
Manifest
Every option your project recorded, and how new ones are adopted.
Agent context
AGENTS.md, the docs silo, and the bundled skills every project ships for AI agents.
Licensing & heartbeat
The manifest, the license JWT, and the daily heartbeat.
eject
The permanent opt-out: what gets deleted and what keeps working.