ShipFast Pricing vs BoiledPlate: Which SaaS Kit Wins?

Comparing SaaS starter kits usually starts and ends with a price tag. ShipFast runs somewhere between $129 and $199 depending on the tier and whatever discount is live that week. BoiledPlate is €159 one-time. You could stop there, declare a winner, and move on. But if pricing were the real decision, you'd already have shipped. The question that actually matters is which kit removes the weeks of work that stand between a stack and a product.

The Real Problem: 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 by lunch. The framework is not what slows you down.

What slows you down is the plumbing between the pieces: webhook idempotency, row-level security, refund flows, EU consent. None of it is clever. All of it eats weeks. Comparing ShipFast pricing to BoiledPlate pricing while ignoring that gap is like comparing the price of two cars by the cost of the key.

BoiledPlate Pricing Breakdown

BoiledPlate Pro is €159, paid once, with lifetime updates and instant delivery via GitHub. There's no seat count and no annual renewal. "Updates" here means semantic, agent-readable release notes and opt-in patches you can apply even after you've customized the code.

There's also a free tier. BoiledPlate Lite is the same app — Nuxt 4, Supabase, Stripe, Resend — minus the AI tooling that makes the paid one set itself up. It's MIT-licensed. You clone it, wire it by hand, and ship. If you want to learn the wiring, start there. If you want the wiring done for you, pay once.

One-time pricing aligns with how builders think: you bought a tool, you own it, you move on.

What You Actually Get

Feature parity checklists flatten real differences. Here's where the depth lives.

Authentication and security. Supabase auth with row-level security enforced at query time, not a generic auth wrapper that trusts your client code. Auth is the fast part; RLS is the part most kits forget.

Billing. Multi-plan Stripe subscriptions with signature-verified, idempotent webhooks. Billing state is sourced from Stripe webhooks, not your checkout success page.

AI-agent ready. A shipped AGENTS.md contract documents one way to do data access and secrets, so a coding agent produces consistent output instead of drifting.

Localization. Four languages from day one — i18n as a core, not an addon you retrofit later.

Email. Resend transactional email, wired to send exactly once.

SEO. JSON-LD, og:url canonicals, and a prerendered Markdown blog that's indexable the day you deploy.

The Hidden Cost of "All-in-One" Kits

ShipFast markets breadth: website, domain, email, payments, banking, AI agents, all in one. That sounds efficient until you realize breadth is also surface area. Every feature you don't use is a feature you have to understand, disable, or route around.

BoiledPlate goes the other way. Nuxt + Supabase + Stripe, done deeply. Three things done well beats ten things done adequately, because the three you actually ship on are the ones with the hard edge cases. A kit that also handles your domain and email is a kit you inherit debt from when you inevitably want to manage those yourself.

Differentiators the Top Results Miss

The ShipFast reviews dominating search rarely go past pricing and feature counts. Here's what they skip.

Agent-driven setup. BoiledPlate isn't a template you fill in. Your coding agent interviews you — name, languages, theme, billing model — then reshapes the codebase to your answers with deterministic patches. The provisioning of Stripe products, webhooks, and Supabase RLS happens in one session.

Deterministic patches. Because customization is applied through repeatable patches, future updates don't turn into merge hell. You opt in, the patch applies cleanly, your changes survive.

Webhook architecture as documented reality. The delivery mechanism — a Stripe webhook where some failures throw and some never do — is written down with the edge cases that made it trustworthy, not hand-waved.

RLS by default. Billing state comes from Stripe, gets enforced in Postgres, and is never trusted from client logic.

Where Each Kit Wins

ShipFast makes sense if you want domain, email, and website bundled, you're not on Nuxt or Supabase, and you're comfortable trading technical depth for breadth.

BoiledPlate wins if you're a Nuxt + Supabase developer avoiding integration weeks, you work with Claude or another coding agent, you care about EU compliance, and you want to actually understand and customize your billing logic.

The Honest Trade-offs

Neither kit is free of demands.

BoiledPlate assumes familiarity with Nuxt, TypeScript strict mode, and Supabase RLS. If you're new to those, there's a learning curve, and the free Lite tier is the honest place to climb it.

ShipFast's broader scope means more to strip out. Every bundled feature you don't need is customization work and one more dependency to manage.

Webhook Architecture: Why This Matters More Than Pricing

Here's the scenario no pricing table shows you. Stripe retries a webhook at 3am. Your code processed the first delivery but returned a 500 on a downstream hiccup, so Stripe sends it again. If your handler isn't idempotent, you've now granted access twice, or refunded twice, or double-counted a charge.

BoiledPlate's webhooks are signature-verified — fraudulent calls get rejected — and idempotent, so retries are safe. That's the difference between a kit that ships a webhook route and a kit that ships a webhook you can trust. Stripe's own documentation on handling duplicate events exists precisely because most implementations get this wrong.

EU Compliance and Billing Reality

If you sell to Germany, you can't just show a pay button. You need a properly encoded withdrawal-waiver consent for digital goods. BoiledPlate handles this through Stripe Checkout consent_collection — the kind of requirement that's invisible in a feature comparison until a customer's chargeback makes it visible.

Refund flows are the other place kits fail quietly. Full refunds, partial refunds, expired refund windows — each is a state transition your billing has to reconcile. Getting this wrong isn't a cosmetic bug; it's revenue and legal exposure.

The Anti-Plumbing Stack

BoiledPlate is optimized for one specific stack, and that's the point. Wiring Nuxt, Supabase, Stripe, and Resend into something trustworthy is where the weeks go. Nuxt gives you full-stack TypeScript and agent-friendly conventions. Supabase gives you RLS and Postgres reliability. Stripe gives you a webhook trust model where billing is the source of truth. BoiledPlate optimizes for these tools instead of abstracting them away.

Free Tier vs Paid Tier: The Real Decision

Lite is a real product: MIT clone, manual wiring, no support. Pro is instant GitHub delivery, lifetime updates, and interview-based provisioning. The break-even math is simple. If the agent-driven setup saves you more than a day of wiring — and it saves considerably more — the €159 has paid for itself before your first deploy.

AI Agent Consistency: A Feature No One Else Talks About

Coding agents drift. Ask Claude to touch your billing logic across ten sessions and you'll get ten subtly different conventions unless something anchors them. That's what AGENTS.md does: conventions written for the agent, not the next hire. BoiledPlate's bet is that agents are part of your workflow, not an optional extra — so the codebase is built for them from the start.

SEO, TypeScript, and Email

Small things compound. BoiledPlate ships JSON-LD structured data, og:url canonicals, and a prerendered blog that's fast and indexable on day one — details that are easy to get wrong, as our own canonical-URL-pointing-at-localhost bug proved. TypeScript strict mode runs end to end, which matters more than ever when an agent is modifying your code: loose types let mistakes through silently. And Resend handles transactional email — receipts, onboarding, password resets — where deliverability failures quietly break the flows customers actually see.

The Verdict: Pricing Isn't the Question; Velocity Is

Choose ShipFast if you want breadth, domain and email bundled, and less technical depth is an acceptable trade. Choose BoiledPlate if you're shipping on Nuxt and Supabase, working with coding agents, and you want billing confidence and EU compliance handled rather than discovered in production.

"Cheaper" is misleading when setup time is the real cost. A kit that's $30 less but leaves you three weeks of plumbing is not the cheaper kit. Before you decide, ask yourself: Do you use or want Nuxt? Are you working with agents? Do you need domain and email bundled? How well do you understand Stripe billing? Is EU compliance a concern?

If your answers point to the anti-plumbing stack, start with BoiledPlate — €159 once, or clone Lite for free and wire it yourself. Either way, the stack was never the hard part. The plumbing is the project, and that's exactly what this kit removes.