A page designer, in the box.
Landing pages, pricing pages and a blog your marketing team can edit visually, inside your own admin, rendering your own components. No Framer subscription, no Webflow, no hand-off.
8 section types, your own components
Engineered with
You know how to build it. You just shouldn’t have to.
Every SaaS demands the same plumbing: auth, billing, multi‑tenancy, an admin. Those first 300+ hours are not what makes your product valuable. That work is already written and already tested. What is left is the part only you can build.
Most starter kits ship every permutation at once and leave you deleting the parts you did not ask for. This one asks twelve questions and writes only the answers, so a single-tenant project never carries multi-tenant code and nothing in the repository is dead on arrival.
bunx saasyland@latest init my-app \--framework next \--arch monolith \--deploy vercel \--runtime node \--db postgres \--provider neon \--orm drizzle \--tenancy single \--auth better-auth \--email resend \--billing stripe \--content mdx10 modules wired · all tests green
cd my-appbun devhttp://localhost:3000Every answer rewrites the flags. Copy the command when it matches your architecture.
Run the CLI again with different answers. What changes is the stack. What remains is the test suite, the clean architecture, and the lifetime updates you already paid for.
Four things every SaaS needs on day one. Every one of them already runs, and every one of them is work you are not doing.
Better Auth runs on your own database instead of per-user pricing that scales against you. Your user table, your sessions, your margins. The bill at 50,000 monthly actives is the same as the bill at 50, and it is zero either way.
$0 per MAU, forever
Not vibe-coded on a weekend. 141 test files and 5 Playwright suites run on every pull request, and the coverage gate fails the build before anything broken can merge. Deploy on a Friday and actually take the weekend.
100% test coverage
Locale routing, translations, timezones and currency formatting are native to the codebase, not bolted on. A 54-locale catalog with 195 timezones and 156 currencies is configured before you write a line, and a parity check fails the build the moment a translation goes missing.
54 locales, 156 currencies
The CLI asks what you are building and scaffolds that, instead of handing you one opinionated shape to fight. Bun and Elysia underneath: instant HMR and strict types while you work, a runtime built for the edge once you ship.
Bun + Elysia, edge-native
If it merges, it works.
Every unit, integration and end-to-end path is covered before it merges. 141 test files, 5 Playwright suites in real Chromium and WebKit, and a coverage gate that runs on every pull request and every push to main.
Which is what makes an agent safe to run here. It can write as fast as it likes; nothing it breaks reaches main, and you find out at the pull request instead of in production.
$ bun run test:coverageTest Files 140 passed (140)Tests 1284 passed (1284)✓ % Stmts 100✓ % Branch 100✓ % Funcs 100✓ % Lines 100
Auth, billing, email, the admin and the test suite are the three months you do not get back, and not one of them is why a customer chooses you. They are written, tested and green. Start on the part that is actually yours.
Everything below is in the repository you clone. No add-ons, no paid modules, no second checkout. All of it typed, tested and readable enough that you or your agent can work in it on day one.
Two things, specifically. A marketing site your own team can edit without a second subscription, and the person who wrote the code explaining every decision in it — including the ones they would make differently now.
Landing pages, pricing pages and a blog your marketing team can edit visually, inside your own admin, rendering your own components. No Framer subscription, no Webflow, no hand-off.
8 section types, your own components
Two courses, both included with the Complete tier. One walks the codebase you receive so you know where everything is. The other builds the whole product again from an empty folder, the CLI included, so nothing in it is a black box.
Free preview
Lesson 01 — The module boundary, before any feature
Watch the first lesson before you decide. No account, no email.
The walkthrough
How the code you receive works, subsystem by subsystem.
The build
The same product again, from an empty folder, in order.
No testimonials, because there is nothing to verify in a quote. Every number on this page is generated by the repository you are buying, and here is where to find it.
Claim
Where to check it
There are no customer quotes on this page, because a quote proves nothing you can check. These are shipping products built on the CLI on this page, with the modules they use and a link to go and look.
LiveCourse platform
A React course platform with 6 advanced projects and over 60 hours of video, sold as one-time access with no subscription. Scaffolded with the CLI, then built out: auth, checkout, the content layer and the admin came from the modules on this page.
Modules
auth · billing · content · admin · email
Ships at launchJewellery store, Poland
A real shop selling real jewellery to Polish customers. It uses the commerce module with sample products stripped out, the admin for stock and orders, and the i18n layer for Polish copy and złoty formatting. Nothing about it is a demo.
Modules
commerce · admin · i18n · email · content
Shipped something on it? Send the URL and it goes on this list.
Get your product featuredThree ways to start a SaaS, and what each one leaves you owing.
A template gets you a folder. This gets you a codebase with the tests already green, the types already strict and every vendor decision already made in your favour. One payment, and nothing here bills you again.
One payment, lifetime core updates, no per-user fees. The same economics this codebase is built to give your own customers.
For the founder who ships alone and reads every line.
$249one-time
The CLI, the source and the tests.
For the engineer who wants the reasoning, not just the result.
$399one-time
The source, and everything that explains it.
For the shop that bills clients for what it builds.
$899one-time
The source, for every client you bill.
Read the documentation and the coverage report before you pay. Every number on this page is generated by the repository you are buying, so you can check the goods first and hold us to what you find.
Consulting
Architecture review, a scaling question, a migration you would rather not get wrong, or an hour walking through your own repository. Sixty minutes, one to one, with the person who wrote and maintains this codebase. Included once on Agency.
$149per hour
Book a callYou are not buying code. You are buying back the calendar.
Price it in your own hours. At $150 an hour, $249 is under two hours of your time. The work it replaces is not two hours. It is auth with two-factor and OAuth, a typed data layer, billing with webhooks, transactional email, ten admin sections, a 54-locale i18n layer and a test suite that actually gates the build. Every one of those is a solved problem you would solve again, and not one of them is the reason anybody will pay you.
The questions buyers actually ask, answered in full. If yours is not here, send it over.
Ask the engineer who built ithello@saasyland.com. One person reads it.
Technical comparisons against the alternatives, written the way a code review is written. Every claim about a competitor links to their own documentation, and every number about this one comes out of the test suite rather than a marketing file.
Aug 15, 2026 · 12 min read
A free CLI scaffolds a stack. A paid starter kit scaffolds a product. Those are different jobs, and confusing them is the most expensive mistake in this category. This is the bill, line by line, with an honest recommendation to use the free one.
Aug 15, 2026 · 16 min read
ShipFast is honest about what it saves you. Twenty-two hours, itemised on the homepage. The number nobody publishes is what you spend between launch and the second paying cohort, and that is where a boilerplate is actually judged.
Aug 15, 2026 · 14 min read
Supastarter is the strongest paid competitor in this category and deserves a fair hearing. The difference between the two products is a single architectural decision made before your first commit, and it decides what every update for the next two years feels like.
Auth, billing, email, the admin and the tests are done. What is left is the part nobody can build for you, and it is the part you have not started.
$249one time, lifetime updates
Pay once, run the CLI, own every line. No subscription, no per-user fees, and no vendor to migrate off in year two.