AI SaaS STARTER · BY UNCORNE

Ship your AI SaaS MVP in days, not months.

The 60% of every SaaS that's commodity — auth, billing, DB, admin — already built and production-grade. You focus on the 40% that's yours.

cloneable · reskinnable · launch-readyFree to try — no account needed

HONEST BOUNDARIES

What make1day.dev does — and what it won't pretend to

We lay it out plainly: the left column is what's stable today; the right is what we know we don't do. No hidden clauses.

Stable today

Production-grade scaffold

Next.js 15 App Router + TypeScript + Tailwind that runs out of the box — not a demo toy.

Row-level security on by default

Supabase data is isolated by user/org at the schema level. Boundaries are built in, not bolted on later.

License-code distribution

After buyout you get license codes — activate per code, revoke anytime, with a transparent distribution log.

RAG knowledge base & multi-tenancy ready

Document Q&A and org isolation scaffolding are ready; wire in your data and ship.

Known limits

Won't write your business logic

make1day.dev gives a production-ready skeleton. Your differentiation — domain model, core algorithm — is on you.

Won't pass merchant onboarding for you

An independent web SaaS has no app-store review, but payment providers do run merchant onboarding, KYC and compliance checks, and they alone decide the outcome. The starter ships legal-page templates and the webhook wiring — not legal advice or an approval.

Won't cover unlimited quotas

AI calls and build counts bill against your own keys and quotas. make1day.dev doesn't silently back infinite usage.

Won't auto-chase every framework major

Major upgrades arrive as drift-safe patches through the Care plan — not as real-time auto-upgrades.

REAL LAUNCH PITFALLS

The pits that actually sink launches — named upfront

Templates look great in demos. These are the holes make1day.dev helps you fill early — and where indie devs most often crash on launch.

Webhook

Payment webhook reconciliation

Stripe/Creem webhooks drop events, duplicate them, fail signature checks. make1day.dev ships idempotent handling and retry — your ledger stays correct.

RLS

Row-level security & permissions

The most overlooked breach: one bad policy lets user A read user B's data. We default to least privilege with auditable policy templates.

License

License distribution & activation

Rolling your own license check, abuse protection, and revocation is another deep pit. make1day.dev's license-code system is ready, with a queryable distribution log.

Drift

Dependency & version drift

Ignore it for three months and one upgrade breaks everything. The Care plan merges patches into your fork drift-safely — no merging from scratch.

CAPABILITY MATRIX

What we lead with, what we keep quiet

We put differentiators up front; commodity SaaS features aren't hyped or padded — they sit in the footnote.

Differentiators (production-grade boundaries)

RAG knowledge base

Runnable doc ingest → retrieve → cite Q&A. Wire in your data and ship.

Multi-tenancy

Org/workspace isolation scaffolding with helpers to extend per-customer data.

Row-level security (RLS)

Supabase least-privilege policies by default — authorization bugs blocked at design time.

License-code distribution

Buyout license codes: generate, activate, revoke — with a transparent distribution log.

Payment compliance pack

Each gateway ships with a machine-readable contract: signing rules, event duties, refund and dispute terms. One command audits your build against it before launch.

Durable AI pipelines

n8n-style flows as code in your project: Inngest retries every step, resumes where it stopped and counts what each run costs. The admin canvas shows what ran and what it cost.

Commodity included (no hype, works out of the box)

Auth (email + OAuth)Subscription billing (Waffo · Stripe · PayPal · Creem · Lemon Squeezy, one webhook)1-click deploy (Vercel/Cloudflare)Observability (structured logs + error boundary)

The commodity items above are production-grade — but we don't sell them as features. They're the entry ticket, not your product.

THEME SYSTEM

Not another UI kit — a design asset you can take with you

make1day.dev's theme system exports reusable design assets, not hardcoded styles locked inside a project you can't touch.

Reusable CSS tokens
Colors, spacing and type scale ship as CSS variables (design tokens). Change once, apply everywhere — reuse them in other projects.
design.md spec file
Auto-generated design.md documents design decisions, token mappings and component conventions — so you and your AI coding assistant extend the UI consistently.
Open theme preview

:root — design tokens

--bg: 255 248 231;
--surface: 255 255 255;
--accent: 201 80 58;
--ink: 17 17 17;
--line: 96 88 72;

design.md

Export sample: CSS tokens and design.md side by side

# Tokens · # Spacing · # Type scale · # Component conventions

INTERACTIVE SHOWROOM

One studio, every template, every screen size

Switch templates on the left, surfaces along the top, and preview the real theme engine at phone, tablet and desktop widths. Static renderings with the same theme variables your downloaded project receives — demo controls are inert; the real app runs on your own deployment.

FROM THE BLOG

Written for developers who actually ship

Read all posts
FAQ

Questions indie founders actually ask

Everything about using make1day.dev to ship your AI SaaS — auth, checkout, AI, deployment, white-labelling and licensing, including the limits we do not hide.

Does the starter include a user dashboard and an admin dashboard?+

Yes — two separate consoles ship by default.

  • `/account` is the signed-in user area: profile, subscription, issued license keys, settings.
  • `/admin` is the operator area: users, licenses, traffic, runtime status.

Both are five-language (EN/ZH/JA/FR/DE).

In the Builder, account and admin are toggleable features. Unchecking one removes its entire route tree from the ZIP, and navigation plus post-login redirects are rewritten so no dead links remain.

Both are writable:

  • PATCH /api/profile edits the signed-in profile
  • POST /api/account/security changes the password, re-sends the verification mail or deletes the account (each action re-checks the current password)
  • PATCH /api/admin/users manages roles (admin only)
  • /api/billing/portal opens the provider billing portal
  • /admin/tickets changes ticket status

Writes are tiered by one capability matrix (lib/rbac.ts): manage_roles, manage_models and trigger_workflows are admin-only; manage_tickets is admin OR staff. Routes enforce with can(capability, role) and the console disables the controls a role lacks.

Every privileged action — and every capability denial — lands in the append-only audit_events trail (emails SHA-256 hashed, ≥365-day retention), viewable at /admin/audit.

RBAC tables (0004_profiles_rbac.sql) and org tables (0007_orgs.sql) ship with every build.

Protect `/admin` before deploying: ADMIN_USER / ADMIN_PASSWORD create an operator account that signs in through /admin's own form with an HMAC-signed session cookie; with no credentials configured, the console stays closed in every environment. A Supabase user with an admin/staff role — or an ADMIN_EMAILS allowlist entry — is accepted too.

How do I get my license key after paying?+

The full source ZIP requires a Buyout license ($99, or $69 during Black Friday) — one-time, the source is yours forever, with 12 months of free rebuild updates. Care ($9/mo, $6 on Black Friday) is a subscription around that license, not a substitute for it: it re-opens your update window after the free 12 months, ships new modules first, delivers upstream merge patches and buys 12-hour priority support. A Care plan alone cannot download the full source. Buyout is refundable within 14 days; Care can be cancelled anytime from the billing portal.

After a paid webhook, the key is emailed to the checkout address automatically, idempotent per issued key. A failed send is queued in mail_outbox and retried by a cron endpoint.

You can also:

  • Sign in with the email you paid with and open /account/licenses
  • Paste an offline key into /license
  • Use the claim form on /license to request a re-send if you checked out as a guest or used a different login email

Real delivery still requires configuring a mail provider and a host scheduler — those are deployment steps, not missing code.

No license yet? Download a free preview: the runnable project skeleton of your build (configs + themed placeholder page), the complete file inventory and the design tokens - no application source. The gate protects this site only; the project you download ships with it disabled.

What is a Next.js SaaS boilerplate?+

It's a prebuilt, production-grade starting point for a SaaS: authentication, database, billing, an admin area and often a working AI feature.

The point is to skip 4–8 weeks of commodity setup and build only what makes your product unique.

How do I build a SaaS with Next.js?+
  1. Start from a configurable starter such as make1day.dev.
  2. Set your env vars — Supabase, a payment gateway, an AI key.
  3. Pick your stack in the Builder.
  4. Download the generated scaffold and deploy to Vercel or Cloudflare.

Most founders reach a launchable MVP in days, not months.

Does make1day.dev include subscription billing and Stripe support?+

Yes. The generated app ships with hosted checkout (Waffo Pancake by default) and webhook-synced plan status.

In the Builder you can switch to Stripe, Creem, PayPal, Lemon Squeezy or Waffo Acquiring — checkout and webhook routes are provider-agnostic, and only the selected adapter ships in the ZIP.

Trial periods are configured in your payment provider's dashboard, not hardcoded in the scaffold.

PRICING

Buy once, or care as you go

The Care plan sells ongoing maintenance, patches and compliance updates — not another copy of code. Free gets you running without nagging you to pay.

Free

$0forever
  • · Everything in the builder, with live theme previews
  • · Free preview pack: a runnable project skeleton, the file list and design tokens
  • · No account, no card. A preview downloads in seconds

Buyout Core

launch price
$69one-time$99
  • · Complete source: Next.js + Supabase, payments swappable across five gateways
  • · Core modules included: auth, billing, admin console, user console, multi-tenancy, hybrid RAG
  • · Payment compliance starter pack: a machine-readable contract per gateway plus npm run compliance:check
  • · 12 months of free updates included; keep updating later with Care
  • · Use it in as many of your own projects as you like, commercial included
  • · One boundary: build your products with it, do not resell it as a template
popular

Buyout Studio

LAUNCH OFFER
$119one-time$199-30%
  • · Everything in Buyout Core
  • · Plus the AI video & image workflow source module: script, storyboard, cost quote, render, then edit by conversation. Only changed scenes re-render
  • · Model settings live in your admin console: providers per task, fallbacks, budgets, and a per-run cost ledger
  • · Future AI modules ship to Studio first
  • · Same license, same 12 months of updates

Care

$6/month$9
  • · Keeps your updates alive: while Care runs, you can always regenerate a build matching current dependencies
  • · Upstream changes (Next, Supabase, payment and AI SDKs) arrive as mergeable diffs; your edits stay yours
  • · Agent docs regenerated monthly so skills, scoped rules and AGENTS.md keep up with Cursor / Claude Code / Codex
  • · New modules and component packs land early
  • · Priority email + ticket support, first response within 12 hours on weekdays

Update window kept open · early modules · priority support

Start your MVP today.

Create an account, pick a plan, and you're building on a stack that's already earned its keep.