Skip to content

Add MailKite SaaS Starter to Boilerplate (remove archived nwb) - #632

Open
bucabay wants to merge 1 commit into
brillout:masterfrom
bucabay:add-mailkite-saas-starter
Open

Add MailKite SaaS Starter to Boilerplate (remove archived nwb)#632
bucabay wants to merge 1 commit into
brillout:masterfrom
bucabay:add-mailkite-saas-starter

Conversation

@bucabay

@bucabay bucabay commented Aug 3, 2026

Copy link
Copy Markdown

Hi 👋

This PR adds MailKite SaaS Starter to the Boilerplate section, placed alphabetically between generator-starhackit and nx.

The one-line description follows the existing style (no bare "React") and a demo link is included per CONTRIBUTING.

It's a production-ready Next.js 15 SaaS starter. The bit that distinguishes it from the other full-stack entries here: auth runs inside your own app (Google/GitHub OAuth + email/password via JWT + sessions) rather than depending on a hosted auth vendor (Clerk / Auth0 / Supabase Auth) — so you can clone it and run it end-to-end without any third-party auth account. It also ships Stripe subscriptions, teams, and PostgreSQL via Drizzle ORM.

Full transparency: the project is new and doesn't have many stars yet. I'm submitting because it's a genuinely complete, runnable SaaS scaffold (the live demo above runs the full app), which fits the "scaffold / starter kit" spirit of this section. Happy to withdraw if you'd rather wait until it's more established.

Per CONTRIBUTING's keep-fresh requirement, this PR also removes nwb (insin/nwb) — that repository is archived (read-only), so it no longer qualifies as awesome. Net change is one add + one remove.

Thanks for maintaining the list — it's a genuinely useful resource.

- Add MailKite SaaS Starter (Next.js 15 SaaS starter, self-contained
  OAuth/email auth, Stripe, teams, Postgres) to the Boilerplate section,
  placed alphabetically between generator-starhackit and nx, with a live
  demo link per CONTRIBUTING.
- Remove nwb (insin/nwb): repo is archived/unmaintained, satisfying
  CONTRIBUTING's keep-fresh requirement (remove one un-awesome entry).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant