5 min read
ShipSafe review: security-first Next.js SaaS boilerplate
Operator review of ShipSafe.st: a security-first Next.js SaaS boilerplate with Firebase session auth, Stripe, Resend, Zod, and a one-time purchase codebase.
ShipSafe is a security-first Next.js SaaS boilerplate: Firebase session auth, Stripe billing, Resend email, Zod validation, and a domain-driven features/ layout. Tagline: Secure by default. Fast by design. It is a one-time purchase codebase, not a hosted SaaS. Live product: https://www.shipsafe.st.
Bias disclosure: I am KLJr, the MakerHunt operator. ShipSafe is the spine under several products I ship, including patterns that landed in MakerHunt. This is an operator review of my own boilerplate, not an affiliate roundup.
If you buy a stack and then need a launch venue, pair this with how to launch an indie product on MakerHunt and the landscape piece on Product Hunt alternatives in 2026. Boilerplate gets you to shippable; hunt day gets you seen.
What it is
ShipSafe removes the “secure by accident” phase of shipping a SaaS. You clone a production-shaped Next.js App Router codebase with auth, billing, validation, and middleware already wired the way you would want after your second breach scare, not after your first tutorial.
It is not Bubble. It is not a hosted multi-tenant platform you rent forever. You buy the codebase once (Core or AI-SaaS Core), own unlimited projects, and get lifetime updates under that purchase model. You still bring Firebase, Stripe, and Resend accounts. The product is the architecture and the defaults.
Domain-driven features/ keeps business logic out of React components. DaisyUI + Tailwind give you a coherent UI starting point. Cursor rules and docs exist so agents and humans follow the same security recipes instead of inventing session cookies from TikTok.
Who it is for
Good fit:
- Indie developers who already know React and Next.js and want a boring, secure spine
- Founders who will customize UI and domain logic on top of a known auth + billing path
- Builders who care that checkout redirects and webhooks are pinned server-side, not vibed client-side
Not for:
- No-code buyers who want a visual builder instead of a repo
- Teams locked on Auth.js / Supabase / ShipFast-style stacks who will not switch
- Landing-only shoppers who need a pretty marketing page and nothing behind
/dashboard
If you refuse TypeScript and env files, stop here. If you want the security middleware story without reinventing CSRF and session cookies, keep reading.
Real USPs and how it works
Accurate to what ships:
- 7-layer middleware. HTTPS enforcement, rate limiting, API firewall, CSRF (webhooks excluded by design), security headers, auth guard (401 for APIs, redirect for pages), and audit logging. Security is a first-class feature, not a README afterthought.
- Firebase → httpOnly session cookies. Client Firebase login yields an idToken; server mints a session cookie via Admin (
createSessionCookie/verifySessionCookie). No raw UID stuffed in a cookie and called “auth.” - Stripe Checkout + customer portal + signed webhooks. Raw body + signature verification. Success/cancel URLs are server-pinned (
buildSiteUrl), not client-supplied redirect toys. Duplicate active plan paths return a clear conflict instead of silent double-charges. - Resend + Zod + domain-driven
features/. Transactional email, validated payloads, business logic in.tsfeature modules without React mixed in. - DaisyUI templates + Cursor rules + docs. Opinionated UI and agent guidance so the stack stays coherent across clones.
- AI-SaaS Core add-on. Extension path for AI chat / subscription-gated AI patterns on top of the same secure spine.
- Showcase apps prove the stack. Live products (ThinkMate patterns, MakerHunt patterns, siblings) back the claim that this is production-tested, not a toy demo repo.
The honest USP is secure defaults you would otherwise reinvent poorly, sold as OTP code you own, not a rented black box.
Pricing
As of this review (one-time purchase, not subscription SaaS):
| Product | Price | Anchor (list) | Notes |
|---|---|---|---|
| Core | €99 OTP | €199 | Security-first Next.js SaaS boilerplate |
| AI-SaaS Core | €149 OTP | €249 | Core + AI-SaaS patterns / add-on path |
Both: unlimited projects, lifetime updates under the OTP model. Confirm live pricing and package contents on shipsafe.st before checkout. Anchors are marketing list prices; street price is the OTP number above.
You still pay Firebase / Stripe / Resend usage yourself. The boilerplate is the codebase, not your cloud bill.
Fit on MakerHunt
Boilerplates and developer tools list cleanly when the tagline is sharp and the marketing site is crawlable. ShipSafe’s story is security-first OTP code, not “another AI wrapper.”
- Categories: developer tools, security, SaaS
- Alternatives neighbors: Firebase, Stripe, Vercel, Cursor, GitHub
Those alternatives pages are neighbors for comparison, not claim that ShipSafe replaces Firebase or Stripe. It uses them correctly. On MakerHunt, list the marketing site, not a private Git clone URL. For launch sequencing after you buy, how to launch on MakerHunt covers the hunt-day ritual; Product Hunt alternatives 2026 covers venue choice if ShipSafe is the product you are launching (or if your product is built on it).
Pros
- Production patterns backported from live apps, not a weekend toy
- Session cookies and Stripe URL pinning are correct by default
- 7-layer middleware is named and shippable, not vibes
- OTP + unlimited projects is a clean fit for serial indie builders
- Cursor rules and docs reduce “agent rewrote auth badly” risk
- AI-SaaS Core exists when chat is the product, without abandoning the secure spine
Caveats
- You still own Firebase, Stripe, Resend, env hygiene, and product design
- Buying a boilerplate does not buy product-market fit
- Stack lock-in is real: if you want Auth.js + Supabase as religion, this is the wrong buy
- AI-SaaS Core is an add-on path; Core alone does not magically make you an AI company
- Operator bias applies; MakerHunt rank is still votes on launch day, not this review
Verdict
Pick ShipSafe if you want a security-first Next.js SaaS starting point, you are willing to read the architecture, and you prefer OTP code over renting a platform. Look elsewhere if you need no-code, a different auth/db religion, or only a landing page.
CTA: Buy or inspect packages on https://www.shipsafe.st. When the product built on it is ready for a public day, submit on MakerHunt.