Why we generate instead of scaffold

Most of a SaaS is the same as every other: sign-in, an admin, an API, docs, a site and billing. A coding agent can write all of it in an afternoon. Then you maintain all of it: every bug in the sign-in flow, every dependency upgrade, every change to Stripe's API, every screen that drifts from the schema it was written against.

We built SaaS.Dev so you write only what is yours: the things your product keeps and what people do to them. Leaseclock, our sample, is three short files. A Lease has a unit, a renter, an end date and a status, and people can renew it or end it. Leaseclock Pro costs $29 a month. That is the whole definition.

What generation buys you

Everything else is generated from those files on each request and runs on your domain: the admin and the customer app, the API, the CLI, the MCP server, the SDK, the site, the docs and the blog, with Stripe checkout and subscriptions. Nothing generated lands in your repo, so nothing generated is yours to maintain.

When we improve checkout, the admin or the docs, every product has the improvement the day it ships. When you add a field, every screen, endpoint, type and docs page has it on the next request, and the changelog says so.

What it asks of you

A shape. A Noun is a name, its fields and its Verbs. Field keys are camelCase, and a Verb moves a record between named states. The rules are strict because every surface depends on them, and because a strict shape is one your agent gets right on the first try. When a file is wrong, the error names the line and the fix.

You can still override anything: a theme, a CSS rule, a field, a view, a page or a Verb's logic. You maintain only what you replace. The fewer defaults you replace, the more improvements you get for free.

Start with the Quickstart, or paste the prompt from the home page into your agent.