2. Generate your own product

Start from a working template

Sign in to ioy.ai and get the template. Your verified account can create a read-only clone credential valid for one hour. No GitHub account or repository invitation is required. Clone the sanitized release into your own directory, then finish local setup. Install the public ioy SaaS Skill with Node.js 22.20+ and Git:

npx --yes skills@1.7.0 add lvyinchao/ioy-saas-skill -s ioy-saas -a codex -g -y

Reopen Codex, then use $ioy-saas and supply your cloned template path and a separate empty project directory. The public Skill supplies instructions and a generator bridge; your ioy.ai account supplies the private template release through authenticated, read-only access. Its GitHub README covers first-time setup and bridge parameters. Keep all service keys in environment variables or Secrets. Never paste a clone credential into Codex chat.

Alternatively, install the bundled skill from a terminal in the mother template directory:

npm run skill:install -- saas-launch

The default destination is ~/.codex/skills/saas-launch, or CODEX_HOME/skills/saas-launch when configured. Reopen Codex so the skill is discovered. If it already exists, inspect its version instead of overwriting it blindly.

Tell Codex eight things

1. Who the product serves and what problem it solves.
2. The main workflow from input to a useful result.
3. Supported input and output formats.
4. Model provider and required model capabilities, without the key.
5. Free allowance, subscriptions or credit packs, and payment provider.
6. Whether customers need an API and a product skill.
7. Brand, tone and visual preferences.
8. Actual domain, official support email and data retention policy.

Example request:

Use $ioy-saas to create my independent SaaS in /absolute/path/my-saas.
My authorized template is at /absolute/path/ioy-template.
Build a writing assistant for independent creators.
The workflow is brief → draft → review → download.
Use the text reference module and an OpenAI-compatible model.
Provide monthly/yearly subscriptions, credit packs, and an API.
Use an English interface. Collect missing business facts before generation.
I will configure all secrets outside the conversation.

If using the bundled installation instead, invoke $saas-launch.

Generate an empty-directory project

Codex writes a requirements JSON. You can also copy and edit examples/requirements.json, then run:

npm run ioy -- create --config /absolute/path/my-requirements.json --out /absolute/path/my-saas
cd /absolute/path/my-saas
npm ci
npm run db:local
npm run dev

Use a separate empty directory outside the mother template. The generator creates an independent Git repository, source, migrations, random local secrets and template-manifest.json. It does not create a GitHub repository or Cloudflare resources.

Check the result

The generated site's homepage and initial guides address your product's users. Template operator pages are replaced with the starter's end-user content. Review the product name, enabled modules and links before continuing. The new app does not depend on the mother template at runtime.

The workflow, model and dataPolicy intake text records requirements; it does not automatically implement a custom workflow, enable a provider, or apply a legal policy. Continue to step 3: customize.

What should you see next?

The empty destination becomes an independent project with its own app/core/product.ts, content, environment examples and launch choices. Standard SaaS and One-page requirements examples are in examples/; choose the layout before generation. Build with Node.js 24+. Run npm ci, npm run ioy -- doctor, and follow the launch checklist.

If validation fails, correct the named requirements field and retry into the same still-empty destination. The generator refuses to overwrite a populated directory. GitHub creation is optional; --github OWNER/NAME creates a private repository using your authenticated GitHub CLI. Without that flag, generation stays local.