ShipFast Boilerplate vs BoiledPlate: Full Comparison

If you've shopped for a SaaS starter kit, you've met ShipFast. It's the reference point in the category: a NextJS boilerplate with auth, payments, a database, and UI components, priced at $199. It does what it says. But the question worth asking before you buy any boilerplate isn't "does it include a login page?" — every one of them does. The question is what happens after you clone it, when you're alone in a room with a box of parts and a README.

This is an honest comparison between ShipFast and BoiledPlate, the AI-native Nuxt + Supabase alternative. Both ship the same stack of features. They diverge on the part that actually eats your launch.

Why Stack Choice Isn't Your Bottleneck

Ask ten founders how to ship fast and you get ten stack arguments — Next vs Nuxt, Postgres vs a hosted DB, Stripe vs Paddle. Pick whatever you already know and the debate is over in an afternoon. The framework is not what slows you down.

What slows you down is the plumbing between the pieces: the Stripe webhook that has to agree with your database, the row-level security policy you forgot until a user saw someone else's data, the five places a new locale string has to land before the build stops complaining. None of it is clever. It's just endless. We wrote a whole piece on why the stack is easy and the plumbing is the project, and it's the single idea that separates these two products.

The Setup Story: Manual Wiring vs. Agent Interview

Here's the core difference. ShipFast follows the classic model: clone the repo, read the docs, wire the services yourself. You create your Stripe products, copy the keys, set up your webhook endpoint, configure your database, and connect Google sign-in by hand. The code is good; the assembly is on you.

BoiledPlate's setup runs itself. Your coding agent interviews you — name, languages, theme, billing model — then reshapes the codebase to your answers with deterministic patches and provisions the services: Stripe products and webhooks, a Supabase database with RLS, Google sign-in. That's not a marketing flourish. As we argued in every boilerplate ships the stack — that was never the hard part, the slow part with coding agents moved somewhere else, and the win is measured in weeks, not hours.

"Agent-driven" doesn't mean magic. It means the repetitive, error-prone wiring is scripted and repeatable, with a human confirming each decision. You still build your product. You just skip the parts nobody enjoys.

Billing That Survives Reality

Both products give you Stripe subscriptions. The difference shows up in the edge cases.

A client-side success page is a lie. The user's browser can close, refresh, or lose connection between paying and landing back on your site — so your checkout success page should never touch your billing state. The Stripe webhook is the source of truth. That means you need signature verification, idempotent processing (Stripe retries; duplicate delivery is normal), and a plan for partially refunded subscriptions.

BoiledPlate ships multi-plan subscriptions with signature-verified, idempotent webhooks out of the box, and we've documented the messy specifics — including encoding a German withdrawal waiver into the pay button for EU consent law, and a webhook where some failures must throw and some never do. These aren't hypotheticals. They're the difference between a demo and a product that survives contact with real customers.

Database Security: Row-Level Security Matters

ShipFast leans on its own database setup with security largely handled in the application layer. BoiledPlate uses Supabase row-level security, which enforces access rules at query time in the database itself — not in your API handlers, where one forgotten check leaks data across tenants.

For multi-tenant SaaS this matters enormously. RLS means a bug in your application code can't hand user A the rows belonging to user B, because the database refuses to return them. Supabase's own RLS documentation is worth reading if you're weighing this trade-off.

Agent Consistency: The AGENTS.md Contract

This is BoiledPlate's genuinely unique angle, and ShipFast doesn't address it at all.

Coding agents drift. Ask one to add a feature and it may invent a new way to access data, handle secrets, or name things — subtly inconsistent with the last thing it wrote. BoiledPlate ships an AGENTS.md contract: one documented way to do data access and secret handling, so agent output stays consistent across sessions. We made the full case in write your conventions for the agent, not the next hire. If you build with Claude or similar, this is the feature that keeps your codebase from turning into archaeology.

Authentication and Internationalization

Both boilerplates handle Google sign-in. BoiledPlate pairs it with Supabase auth backed by RLS, so authentication and authorization share one enforcement point rather than a scattered JWT strategy layered on top.

On languages, ShipFast's i18n story is minimal. BoiledPlate ships four languages from day one, with locale setup handled by the same deterministic patches — because adding a language later means touching every string in the app, and that's exactly the kind of endless, slightly-different work described in what it actually takes to wire up a Nuxt, Supabase and Stripe SaaS.

The Blog, SEO, and Transactional Email

Every SaaS needs SEO momentum from day one, which is why both include a blog. BoiledPlate's is prerendered Markdown with JSON-LD schema, canonical URLs, and og:url tags. That corner has real pitfalls — we shipped a bug where our blog told Google its canonical URL was localhost:3000, and another where a JSON-LD source-order issue returned 200 from curl but 500 in Chrome. Prevention is baked in because we hit them first.

For email, BoiledPlate integrates Resend for billing confirmations, refunds, and multi-language templates. Sending once is easy; sending exactly once, with SPF, DKIM, and unsubscribe handling correct, is the annoying part a starter should absorb.

Updates and Maintenance: The Merge Hell Problem

With most boilerplates, ShipFast included, you own all your customizations and every upstream update is yours to integrate — which usually means rebase conflicts you postpone forever. BoiledPlate writes semantic, agent-readable release notes and offers opt-in updates to customized code, so your agent can apply an improvement without stomping your changes. Lifetime updates are part of the Pro tier.

Deployment, Types, and Theming

BoiledPlate deploys in minutes to Vercel, Netlify, or self-hosted, with environment variables and secrets documented. It's TypeScript strict mode end to end — server, client, and database layer — which is how you catch billing bugs at compile time instead of in a customer's inbox. (One caveat we hit: Vercel's analytics package can break Nuxt typecheck, documented so you don't lose an afternoon to it.)

Theming is handled in the setup interview: pick a preset — Warm Studio, Clean SaaS, Midnight Pro, Sharp Enterprise — or describe your own and the agent maps it onto the codebase. The dashboard previews on the homepage are the real thing every buyer gets.

Pricing: One-Time vs. Recurring

ShipFast is $199 per license. BoiledPlate comes in two tiers: Lite is free and MIT-licensed — clone it and wire the services manually, exactly the ShipFast experience minus the price — documented in our post on the free Nuxt + Supabase boilerplate. Pro is €159 one-time with lifetime updates and instant delivery via GitHub invite.

The honest total-cost comparison isn't the sticker price. It's the sticker price plus the weeks of wiring. If you value an afternoon over a fortnight, the setup process is where the money is.

When a Boilerplate Isn't Enough

Be clear-eyed: any boilerplate solves maybe 60–70% of setup. Your actual product logic — the thing that makes you money — is still yours to write. What both products give you is a clean, owned starting point. BoiledPlate's agent-readable conventions arguably reduce lock-in, because the code documents its own contract.

Decision Framework: ShipFast or BoiledPlate?

• Choose ShipFast if: you're committed to NextJS, prefer wiring services by hand, and don't build with coding agents.
• Choose BoiledPlate if: you're on (or happy to be on) the Nuxt + Supabase + Stripe stack, you build with agents, you want RLS enforced at the database, and lifetime updates matter.

The framework is not the differentiator. The setup process and the maintenance cost are.

The Bigger Picture

Agent-native contracts like AGENTS.md are becoming table stakes. As more code gets written with coding assistants, the boilerplates that win won't just be readable by humans — they'll be written for agent consumption, with one documented way to do every dangerous thing. That's the bet BoiledPlate makes, and it's worth understanding before you commit €159 or $199 to a codebase you'll live in for the next year. Read the full blog if you want the edge cases in detail before you decide.