finds.dev← search

// the find

boxyhq/saas-starter-kit

★ 4,840 · TypeScript · Apache-2.0 · updated May 2026

🔥 Enterprise SaaS Starter Kit - Kickstart your enterprise app development with the Next.js SaaS boilerplate 🚀

A Next.js boilerplate targeting B2B SaaS products that need enterprise auth from day one — SAML SSO, SCIM directory sync, audit logs, team management, and Stripe billing are all wired up before you write a line of product code. It's maintained by BoxyHQ, the company behind the SAML Jackson service it depends on, so this is partly a product demo. Best fit for a solo dev or small team who wants to ship a multi-tenant app to enterprise buyers without building the plumbing.

- SAML SSO and SCIM directory sync are genuinely working, not stub implementations — they use the BoxyHQ Jackson service which is battle-tested and handles the protocol complexity you don't want to touch

- The RBAC model and team invitation flow are complete: roles, permissions, pending invitations, and domain-based restrictions are all implemented and backed by real API routes

- Prisma migrations are checked in and sequential, so the schema is reproducible and you can trace every change — this is the right way to manage a shared DB schema

- Playwright E2E tests cover the auth and team flows, which are the hardest things to test and the most expensive to debug in production

- Hard dependency on BoxyHQ's hosted Jackson service for SAML/SCIM — you can self-host Jackson, but it's another service to run, and if BoxyHQ changes pricing or availability you're in a migration

- Uses the Pages Router, not App Router — fine today but Next.js is clearly moving on, and a starter kit built on the old model will feel dated faster than the code it generates

- Unit and integration tests are explicitly listed as 'coming soon' in the README; you have E2E tests but no unit or integration coverage, which means regressions in business logic won't surface until they break a user flow

- The i18n setup (next-i18next) only ships English locale files — the infrastructure is there but you'll be starting from scratch on translations, which is deceptive given how much setup time i18n usually requires

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →