The library · The stack

The SaaS starter

Start with accounts, organisations, email and analytics wired into a React app and Hono API.

5 files · 151 KB

Why I keep it

I want the first brief to be about the product, so I’ve built the account-and-organisation app I’d otherwise have to brief again. React runs on Vite with TanStack; Hono handles the API, Better Auth handles sign-in and Drizzle holds the Postgres schema.

I’ve included Loops account email, PostHog events, shared contracts and the checks behind pnpm verify. The setup prompt and AGENTS.md help your agent work through the launch checklist with you. Deploy in one click with my Railway template, or use Docker Compose with Caddy on your own host.

How I use it: Keep the plan with the work →

Take the files

5 files · 151 KB

  • README.md2 KB
  • react-saas-starter/AGENTS.md801 B
  • react-saas-starter/README.md7 KB
  • react-saas-starter/STARTER.md2 KB
  • react-saas-starter.zip140 KB

Keep building your setup: The stack

Back to the shelves →
  • 015 files · 6 KB

    Turborepo

    Run builds, tests and type checks across your apps in dependency order, with cached results.

  • 0216 files · 18 KB

    Hono

    Give your API typed routes, generated docs and a consistent error response before adding features.

  • 038 files · 8 KB

    Drizzle

    Keep your database schema typed and your SQL migrations checked in beside the code that needs them.

  • 042 files · 5 KB

    Better Auth with passkeys

    Keep accounts, organisations and passkey sign-in in your own Hono API and Postgres database.

  • 059 files · 10 KB

    TanStack

    Keep React routes, session checks and cached server data working from the same types.

  • 065 files · 5 KB

    Lefthook and Biome

    Check staged code at commit time and types before a push, including work written by your agents.