ShipFast Tech vs BoiledPlate: SaaS Boilerplate Comparison

When people search for "shipfast tech," they're usually asking one question: which SaaS boilerplate gets me to production fastest? ShipFast, Marc Lou's Next.js template, popularized the "days not weeks" pitch. BoiledPlate makes a similar promise on a different stack. But most head-to-head comparisons stop at feature checklists and miss the part that actually eats your launch: the plumbing.

What This Comparison Actually Covers

This isn't a feature-parity table. Both products ship auth, Stripe, a database, and email. The interesting differences are architectural: ShipFast is a Next.js template you clone and customize by hand. BoiledPlate is a Nuxt + Supabase starter whose setup runs itself — your coding agent interviews you, then provisions services and patches the code.

"Days not weeks" means different things depending on which of those workflows you buy into. Let's look at where the weeks actually hide.

The Plumbing Layer: Where Weeks Actually Hide

Picking Next.js or Nuxt takes an afternoon. Wiring Stripe webhooks, writing row-level security policies, handling refunds, and encoding EU consent takes weeks. We've argued this at length in how to ship SaaS fast: the stack is easy, the plumbing is the project. The framework is not what slows you down.

Webhook Architecture: The Invisible Complexity

The Stripe checkout redirect is the easy 20%. The webhook is where subscriptions actually live. You need signature verification, idempotent handling so duplicate deliveries don't double-grant access, and logic that survives events arriving out of order — Stripe can deliver subscription.updated before subscription.created. Stripe's own webhook documentation warns you to respond within seconds and process asynchronously.

Most boilerplates ship a happy-path handler and call it done. BoiledPlate treats Stripe webhooks as the source of truth — your checkout success page should never touch billing state — and documents the webhook contract so it stays consistent when an agent modifies it later.

Deterministic Patches vs Manual Wiring

Here's the workflow fork. ShipFast: clone the template, customize by hand, and when an update lands, work through merge conflicts. BoiledPlate: the agent interviews you (name, languages, theme, billing model), then reshapes the codebase with deterministic patches — automated, repeatable changes applied to match your answers. Updates arrive as opt-in semantic release notes rather than a git merge you have to referee.

If a coding agent is part of your daily workflow, that difference compounds over the life of the project.

Billing Edge Cases That Swallow Weeks

Subscription State Management

Multi-plan billing is harder than single-tier: downgrades, proration, refunds, and cancellations all have to reconcile against Stripe without race conditions. The pattern that works is documented in how to set up Stripe subscriptions in a Nuxt + Supabase app — plans defined in one place, checkout as a redirect, webhooks as the store of record, and subscription state turned into access at query time.

EU Compliance and Refund Flows

US-first boilerplates routinely miss EU requirements. German law, for example, requires a specific digital-goods withdrawal waiver before you can charge — we encoded it directly into the pay button using Stripe Checkout's consent_collection. Refunds carry their own trap: process one twice and you've made a financial error. Stripe deduplicates with idempotency keys, but your application layer still needs to mark a refund as processing before it fires.

This is where Supabase RLS earns its place: billing boundaries are enforced at the database layer, not in application code that an agent might accidentally drift away from.

Architecture Comparison: Next.js vs Nuxt + Supabase

Why BoiledPlate Chose Nuxt + Supabase

Nuxt's file-based routing and server routes give agents predictable conventions to read and extend. Supabase pushes security into the database with row-level security, so a leaked query can't return another tenant's rows. These tools work well together — and each demands something in return, which we break down in what it actually takes to wire up a Nuxt, Supabase and Stripe SaaS.

ShipFast's Next.js Stack

Next.js brings a larger ecosystem and more database flexibility. That flexibility is a genuine strength if you already live in that world — but it comes with fewer opinions on RLS, which means security is more your responsibility than the framework's.

The Anti-Plumbing Stack Question

Do these tools prevent plumbing, or just hide it? Honestly, neither eliminates it. The difference is where it's hidden. BoiledPlate hides it in agent-driven setup, deterministic patches, and an AGENTS.md convention contract that keeps agent output consistent. ShipFast hides it in battle-tested code you clone and customize by hand.

Agent-Driven Setup: The Overlooked Differentiator

The Interview Model

BoiledPlate's setup is a conversation: the agent asks questions, patches code, and provisions Stripe products, a Supabase database with RLS, and Google sign-in in one session. ShipFast is the traditional model — clone the template, run manual setup, keep a spreadsheet of secrets, click through provider consoles.

AGENTS.md: A Data Access Contract

AGENTS.md documents one way to access data and handle secrets. That single source of convention is why an agent can handle, say, a subscription downgrade months later without inventing a second, inconsistent data-access pattern. Most existing boilerplates weren't designed for agent co-authorship, so they don't ship anything like it. We covered this shift in every boilerplate ships the stack — that was never the hard part.

Feature Parity: What Both Ship

On the checklist, they overlap more than they differ:

• Auth: both ship it; quality differs on RLS enforcement.
• Stripe: both ship it; webhook robustness varies.
• Database: ShipFast flexible; BoiledPlate opinionated on Supabase.
• Transactional email: both; BoiledPlate defaults to Resend.
• i18n: BoiledPlate ships four languages by default; ShipFast optional.
• Blog: BoiledPlate prerenders Markdown; ShipFast is ecosystem-dependent.
• Theming: both; BoiledPlate lets you pick a preset or describe a custom theme in the setup interview.

BoiledPlate-specific: deterministic patch system, agent-driven interview, AGENTS.md in the repo, opt-in semantic release notes, TypeScript strict mode, JSON-LD and canonical-URL SEO, RLS as a first-class concern.

ShipFast-specific: larger ecosystem, more third-party integrations, a longer track record, more community templates, and freedom over database and backend choice.

Pricing and Delivery

BoiledPlate is €159 one-time with lifetime updates and instant GitHub delivery — the repo is cloned into your account via webhook — plus a free, MIT-licensed Lite tier you can wire up manually. ShipFast runs roughly $129–$199 one-time depending on tier, with traditional download-and-clone delivery.

Both are one-time purchases at a similar price. The real cost difference is update friction over the project's lifetime: merge conflicts versus semantic release notes.

Real-World Shipping Time: An Honest Breakdown

ShipFast's "5 minutes to production" claim is true for scaffolding and a first deploy. It is not true for webhook testing, RLS policies, multi-plan billing, consent flows, and edge-case refunds. Those are the hidden weeks.

BoiledPlate's claim is narrower and, we think, more honest. The interview runs 15–30 minutes. Service provisioning happens while you watch, roughly 10–15 minutes. Deterministic patches customize the code during the interview. Then you still need to verify billing and webhooks work — hours, not weeks. The agent handles the wiring; it does not replace thinking about your product's UX.

Per phase: auth setup saves days on both. Billing is where the agent saves the most — idempotent webhooks, RLS, and multi-plan handling are pre-solved. Email and notifications are similar. The biggest long-term saving is maintenance: semantic versioning saves weeks over a customized codebase's lifetime.

Common Bugs Both Stacks Hit

Real launches trip on real bugs. Incorrect JSON-LD can crash hydration — we shipped a page that returned 200 from curl and 500 in Chrome because of source order. Canonical URLs are easy to break in multilingual sites; our blog once told Google its canonical URL was localhost:3000. And delivery-critical webhooks need careful failure semantics — some failures must throw, some never should, which we unpack in the GitHub invite is the product.

Who Should Pick Which

Pick BoiledPlate if you're comfortable with Nuxt, you use a coding agent like Claude as part of your workflow, your billing is complex (multi-plan, refunds, EU compliance), and you value database-layer security.

Pick ShipFast if you're Next.js-first, you prefer manual control over interview-driven setup, your billing is simple, you don't use agents, and you want maximum integration flexibility.

Don't decide on framework popularity or "faster shipping" alone. Both hit the same plumbing wall.

The Real Lesson

Neither boilerplate eliminates plumbing — they hide it differently. BoiledPlate hides it in agent-driven setup, deterministic patches, and an AGENTS.md contract. ShipFast hides it in battle-tested code you clone by hand.

So "shipfast tech" isn't really a framework question. It's a workflow question. If your coding agent is going to be a regular co-author, an architecture built for agent consistency and safe, semantic updates is worth more than ecosystem size. If it isn't, a proven Next.js template you customize by hand is a perfectly reasonable bet. Pick based on how you actually work — not on the marketing copy on either landing page.