ShipFast Alternatives: Nuxt + Supabase Comparison

Ask on r/SaaS for a ShipFast alternative and you get a list of names: Kostra, Open SaaS, Shipped Club, Makerkit, IndieKit, CodeConductor. What you rarely get is an honest answer to the question underneath the question. People don't leave ShipFast because $150 is too much. They leave because the template hands them a working stack and then leaves the hard part — the wiring between services — as an exercise for the reader.

This is a comparison for a specific kind of builder: you use or want to use Nuxt and Supabase, you work with a coding agent like Claude, and you'd rather ship product than debug webhooks for a month. If that's not you, some of the alternatives below are perfectly good. If it is you, most of them leave the same gap.

Why Developers Leave ShipFast (And What They Actually Need)

ShipFast is Next.js, MongoDB, Stripe, Google Auth, Mailgun, Tailwind. It's a fine kit if that's your stack. The friction shows up in four places.

Stack lock-in. Next.js only. If you're a Nuxt shop, you're translating conventions before you write a line of your own. MongoDB means no Postgres row-level security — your multi-tenant isolation lives in application code, where it's one forgotten where clause away from leaking data.

Manual provisioning. The template writes code. It doesn't create your Stripe products, register your webhook endpoint, or wire your Google sign-in credentials. You do all of that by hand, per environment.

The plumbing tax. Auth usually works out of the box. Billing edge cases don't. Refunds, failed payments, EU consent — those are left to you, and they're exactly the parts that take weeks.

One-way customization. You modify the template, the template gets an update, and now you're merging by hand. There's no semantic release layer designed for a coding agent to read and apply safely.

The Real Cost of "Free vs. Paid"

The Reddit thread always tilts toward "just use the free one." Kostra and Open SaaS are MIT-licensed and genuinely good. But free saves you a license fee, not the work. You still design RLS policies, still build idempotent webhook handling, still scaffold email templates, still wire consent flows.

What you pay for in a purpose-built kit isn't the code — code is cheap now. You pay for the accumulated decisions: idempotent webhook architecture, deterministic patches that customize the codebase without breaking it, and an agent contract that keeps output consistent. As our post on shipping SaaS fast argues, the framework is not what slows you down. The plumbing between the pieces is.

DIY boilerplates cost more than they look when your time has a price. We'll put a number on that at the end.

Stack Comparison Matrix

The Next.js dominance myth. Next.js is popular, not mandatory. For European SaaS, Nuxt earns its place: i18n is first-class, server composables keep your API tidy, and edge deployment is straightforward. BoiledPlate ships four languages from day one — most Next.js starters treat i18n as a later problem.

Database choice. MongoDB versus PostgreSQL isn't a taste debate when compliance is involved. Postgres gives you transactions, auditability, and — via Supabase — row-level security enforced at query time. Security in the database beats security in a middleware you might forget to apply.

Payment processors. Stripe, Lemon Squeezy, or a hand-rolled webhook layer. Lemon Squeezy simplifies tax as a merchant of record, which is real value. But whatever you use, your billing state's source of truth should be the webhook, not a client redirect. More on that below.

Auth maturity. Google sign-in alone gets a user logged in. It does nothing for tenant isolation. RLS-enforced multi-tenancy is a different tier of maturity, and it's the one that matters once you have paying customers sharing a database.

Agent-Native Architecture (The Gap Nobody Addresses)

Here's the thing almost none of the alternatives address: your codebase now has a second author. You use Claude for features. So did the starter's author, probably. If there's no documented contract for how data access and secrets work, the agent drifts — and every session invents a new pattern.

BoiledPlate ships an AGENTS.md contract: one documented way to do data access, one place for secrets, so agent output stays consistent. Combined with deterministic patches, a coding agent can reshape the starter to your answers safely rather than free-styling.

Shipped Club, Makerkit, and CodeConductor are all reasonable products, but none ship a documented agent contract as a first-class artifact. The real scenario this unlocks: Claude provisions your Stripe products and updates the matching RLS policies in the same session, because both follow one written convention.

Webhook Architecture Breakdown

The webhook is the product. The checkout is the easy bit.

Idempotent design. Stripe retries. If your handler isn't idempotent, a retry becomes a duplicate charge record or a double-provisioned subscription. Many free starters demo the happy path and never show the idempotency key handling.

Failure recovery. Some failures should return non-200 so Stripe retries; some should never throw, because retrying won't help and will just orphan state. We wrote about exactly this distinction in the Stripe webhook where some failures throw and some never do.

Source of truth. Your checkout success page should not touch billing state. A user can close the tab before redirect; a refund never hits the success page at all. Only the webhook sees the full lifecycle.

Signature verification. BoiledPlate ships verified, idempotent webhook handling as working code — not as a paragraph in the docs telling you to add it.

Billing Edge Cases the Alternatives Skip

EU consent withdrawals. German law requires an explicit withdrawal-right waiver for instant digital delivery. We encoded it directly into Stripe Checkout's consent_collection — here's how. Most starters ignore this entirely.
Refund workflows. Partial refunds, cancellation cascades, and an audit trail that survives a dispute.
Multi-plan subscriptions. Seat upgrades, downgrade proration, trial logic — five decisions most templates make for you badly.
Churn. Payment method failures, dunning, reactivation.

The "Plumbing Tax" in Each Alternative

Kostra (free, MIT). Excellent Next.js starter. You save $159 and spend it back in RLS design, webhook retries, and email scaffolding.
Open SaaS (free). Solid and open. Verify the webhook signature-verification story yourself before relying on it in production.
Shipped Club (paid). Stripe and Lemon Squeezy, which is genuinely nice. Weaker on multi-language i18n from day one.
Makerkit (paid). Full-featured and mature — but Next.js only, and not structured around an agent contract.
CodeConductor (AI-focused). Prompt-based generation. Powerful, but there's no delivered, versioned scaffold to update over time.
IndieKit. B2B and B2C out of the box; typically tied to a single payment processor.
LaunchFast, supastarter, AnotherWrapper. All ship a stack competently. The shared shortfall is depth on webhook correctness and EU compliance.

Technical Specificity: What Gaps These Alternatives Leave

Real bugs the polished demos don't mention, most of which we hit and documented:

JSON-LD hydration crashes — 200 from curl, 500 in the browser, all from source order.
Canonical URLs pointing at localhost across i18n routes.
Peer dependency conflicts in Nuxt — a package that quietly breaks typecheck.
RLS policy drift with no versioning convention.
Transactional email retry logic (sending exactly once with Resend is harder than sending).
Deployment environment variable validation.

When to Pick Each Alternative

Kostra / Open SaaS: you want maximum control and have 6+ weeks for plumbing.
Shipped Club / Makerkit: you're committed to their stack and won't drive updates with an agent.
CodeConductor: you're prompt-first and don't want a pre-built scaffold.
BoiledPlate: you want Nuxt + Supabase, value agent consistency, and need EU billing compliance with setup done in one session.

The Anti-Plumbing Stack: Why These Tools Work Together

Nuxt is the full-stack glue with built-in i18n and edge deployment. Supabase gives you Postgres plus RLS, so security is enforced at query time. Stripe webhooks are the single source of truth for billing. Resend is transactional email native to TypeScript. Google sign-in removes password resets and their compliance theater. Each choice is defensible; the official Stripe webhook docs will confirm why idempotency and signature verification aren't optional.

Pricing Honesty

ShipFast: ~$150 flat, no lifetime updates. You pay for the initial time save.
BoiledPlate Lite: free, MIT, wire it by hand.
BoiledPlate Pro: €159 one-time, lifetime semantic updates, instant delivery via GitHub, agent-readable AGENTS.md.
Subscription kits: recurring fees with feature-gated updates and no agent contract.

The Shipping Cost Hidden in the Alternatives

Price out the "free" path at a contractor rate:

Webhook retry logic: ~40 hours
RLS policy design and review: ~20 hours
EU consent forms: ~16 hours
Email template scaffolding: ~8 hours
Multi-language routing: ~12 hours

That's ~96 hours. At $150/hr, roughly $14,400 of work — to save a €159 license.

Conclusion: Picking the Right Plumbing Kit

Plumbing isn't glamorous, but it's not optional. Free alternatives are free because they push that work onto you, and DIY looks cheap only until you count the hours. Agent-native architecture is a genuine differentiator: a documented contract plus deterministic patches means your starter can keep changing safely long after purchase. And EU billing compliance is exactly the kind of thing you should not learn on your own live checkout.

If your stack is Nuxt and Supabase and you build with an agent, BoiledPlate provisions the services instead of just writing the code. Ship product, not plumbing.