// the find
nextify-limited/saasfly
Your Next SaaS Template or Boilerplate ! A magic trip start with `bun create saasfly` . The more stars, the more surprises
A Next.js 15 SaaS starter in a Turborepo monorepo, wiring together Clerk auth, Stripe billing, tRPC, Prisma/Kysely for DB, and shadcn/ui — the standard stack for someone who wants to ship a SaaS without building plumbing from scratch. Targets developers who know what all those pieces are and just want them pre-connected. Not opinionated about your domain, just about your infrastructure choices.
The monorepo package split is clean — auth, db, stripe, api, ui are separate packages with clear responsibilities, which makes it easier to swap one without breaking everything else. Using Kysely for runtime queries while keeping Prisma only for schema management is a genuinely good call: you get type-safe SQL without the Prisma runtime overhead. The i18n setup handles locale routing at the Next.js middleware layer, which is the right place for it. Bun as the package manager cuts install times noticeably on a repo this size.
The auth situation is a mess: there are two parallel implementations (NextAuth on a feature branch, Clerk in main), and the README still references both without being clear which one you should actually use. The k8s components (cluster creation, config pages) have no obvious connection to the SaaS template use case — they feel like leftovers from an internal tool the authors were building, and new adopters will spend time figuring out what to delete. The admin dashboard is described as 'alpha' with only a static page — it ships as a stub you'll need to fully build. Prisma and Kysely both pointing at the same database means two different schema representations to keep in sync; the README hand-waves this as 'Prisma for schema management' but the boundary will blur the moment you add a migration.