I rebuilt the same SaaS backend five times. So I turned it into one SDK.

I build SaaS products with my brother. After shipping five of them, I realized I'd rebuilt the exact same backend (auth, Stripe, multi-tenancy, workflows, email, webhooks) five separate times. So I extracted it into one SDK for React/Next.js. It now runs all five products in production. This is the honest version, including what it still can't do.

The fifth time I sat down to write sign-up and login, I stopped.

It wasn't hard. That was the problem. I'd done it four times already, and I could see the next three weeks laid out in front of me like a checklist I'd memorized: auth, then Stripe, then workspaces, then roles and permissions, then usage limits, then transactional emails, then webhooks. Weeks of plumbing before I could touch the one feature that was the actual reason I started the project.

I build software with my brother. Five of our products are live right now:

Imejis - a template-based image-generation API

I rebuilt the same SaaS backend five times. So I turned it into one SDK.

Related reading

I Got Tired of Rebuilding Auth, Billing, and AI Features for Every SaaS

I Built a Production-Ready Node.js SaaS Boilerplate So You Don't Have To

I built a production-ready SaaS boilerplate - here's what I learned

Mistakes I Made Building My First SaaS Starter Kit

I Built a SaaS with AdonisJS 7, and I Loved It

I tried to build a SaaS. I'm shipping tiny libraries instead.