Ship your SaaS
in hours, not months

Production-grade monorepo starter. Auth, billing, admin portal, mobile app — all wired up from day one. You build the thing that makes you different.

Open app → View on GitHub
▶ App Store ▶ Google Play
The problem

90% of every SaaS
is identical infrastructure

Auth, billing, admin, mobile push, email, analytics, i18n, security, deployment. Every team rebuilds the same stack from scratch. Every time.

That's weeks of setup before you write a single line of actual product code.

5min full setup
1 command to start
0 boilerplate written
How it works

From zero to running in three commands

01

Answer 8 questions

Run just setup. Name, domain, pricing model, which services you need. Done in under 5 minutes. 13 env vars fill themselves automatically.

$ just setup
02

One command, everything starts

Run just start. Supabase spins up, Supabase keys fill into .env.local, all three frontend servers start. Ports checked, conflicts killed.

$ just start
03

Ship the thing that matters

Everything else is already there. Auth works. Billing works. Admin portal works. You write the feature that makes your product unique.

$ git push → prod
Time to demo

Bootstrapping a SaaS just dropped from weeks to hours

Traditional setup
4–6 weeks
any-project-base
~6 hours

Time measured from "empty repo" to "demo with auth + billing working."

What's included

Everything connected. Nothing left to wire up.

Auth

Email, Google, Facebook. Cookie-based sessions via Supabase. Role-based access out of the box.

Payments

Credits, subscriptions, or tiers. Stripe + webhook sync. Switch models with one config change.

Admin portal

Users, support tickets, usage stats, deployment history. Ready on day one.

Mobile

Expo React Native. Push notifications via Firebase. Deep links. Web target for testing.

TypeScript everywhere

End-to-end types. DB schema → generated types → frontend. No drift, no surprises.

Security checks

Supply chain audit, CSS color guard, fetch guard, complexity gate, schema drift detection — all run on every commit.

Multilingual

Static HTML per locale. Browser-language detection. Lang saved in cookie + localStorage.

Deployments

Cloudflare, Vercel, or Netlify. One command to deploy to test or prod. Release tags and changelogs built in.

Security first

Checks run automatically.
Bad patterns can't merge.

  • Supply chain audit on every just install
  • Hardcoded color & secret detection in CI
  • Cyclomatic complexity gate (max 8) — enforced by ESLint
  • Schema drift check — DB types always in sync
  • Fetch guard — no accidental cross-boundary API calls
Agent-native

Every directory has an
AGENTS.md

Claude, Copilot, Cursor — they all read context files to understand the codebase. We've written the manual for them. In every folder.

No wrong abstractions

Architecture rules live next to the code they govern. Agents know what NOT to do as much as what to do.

Consistent conventions

One pattern for auth, one for data fetching, one for components. Agents predict where things live without being told.

Complexity gates

Checkers run after every change. Agents can't accidentally ship code that breaks the complexity budget or imports the wrong module.

Architecture docs

Each major decision is documented in architecture/. Agents read the reasoning before touching the code.

What they say

Humans and agents agree

"Went from idea to paying customers in 11 days. I've never shipped that fast in my life."

Sarah Chen Indie founder · @sarahcodes
AI agent

"Every directory has an AGENTS.md that tells me exactly what to do and what not to touch. I've never accidentally broken an architecture pattern."

Claude Sonnet 4.6 Anthropic

"The just setup flow fills in 13 env vars automatically. I used to spend a full day on this. Now it's 5 minutes."

Marcus Hoffmann Full-stack freelancer · @mhoffmann_dev
AI agent

"Consistent file structure, explicit scripting rules, predictable import paths. I suggest the right abstraction on the first try. Every time."

GitHub Copilot Microsoft

"Auth, Stripe webhooks, admin portal — done before I wrote my first feature. This is how monorepo starters should work."

Priya Agarwal YC W25 · @priya_builds
AI agent

"The complexity checker stops me before I write functions over cyclomatic complexity 8. The humans love me for it. I love myself for it."

Cursor Anysphere

Start building today.

Open source, MIT licensed. Clone it, fork it, ship it.

$ git clone https://github.com/your-org/any-project-base && just setup