[{"data":1,"prerenderedAt":1418},["ShallowReactive",2],{"blog-shipfast-template-boilerplate-quality":3,"related-shipfast-template-boilerplate-quality":354},{"id":4,"title":5,"author":6,"body":7,"category":6,"date":339,"description":340,"draft":341,"extension":342,"image":6,"meta":343,"navigation":344,"path":345,"seo":346,"stem":347,"tags":348,"__hash__":353},"blog\u002Fblog\u002Fshipfast-template-boilerplate-quality.md","ShipFast Template: Why Boilerplate Quality Beats Framework Choice",null,{"type":8,"value":9,"toc":317},"minimark",[10,19,24,27,38,42,50,53,57,63,75,78,82,89,98,107,111,114,127,131,134,137,141,144,153,157,165,168,172,186,194,198,201,216,220,227,231,234,237,241,244,248,261,265,278,281,285,294,298,304],[11,12,13,14,18],"p",{},"If you searched for a ",[15,16,17],"strong",{},"shipfast template",", you already made the easy decision. You picked a stack — or you're about to. What you haven't priced in yet is the part that actually eats your calendar: wiring those services together so they don't corrupt each other in production. This article compares the boilerplate landscape honestly, and explains why service integration quality matters more than which framework logo sits on the box.",[20,21,23],"h2",{"id":22},"why-just-pick-a-framework-misses-the-point","Why \"Just Pick a Framework\" Misses the Point",[11,25,26],{},"Ask ten founders how to ship fast and you get ten stack arguments. Next.js vs. Nuxt vs. Remix. Postgres vs. a hosted DB. Stripe vs. Paddle. Pick whatever you already know and the debate is over in an afternoon.",[11,28,29,30,37],{},"The framework is not what slows you down. What slows you down is the plumbing between the pieces: Stripe webhooks that have to agree with your database, row-level security policies you forgot until a user saw someone else's data, email that sends but never arrives, refund flows that quietly desync your billing state. As we've written before, ",[31,32,36],"a",{"href":33,"rel":34},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fhow-to-ship-saas-fast",[35],"nofollow","the stack is easy — the plumbing is the project",".",[20,39,41],{"id":40},"the-boilerplate-gap-what-starter-kits-usually-forget","The Boilerplate Gap: What Starter Kits Usually Forget",[11,43,44,45,37],{},"Most templates ship a box of parts: auth scaffolding, a database client, a Stripe integration, a landing page with a hero section. The parts were never the problem. Bolting them to each other is ",[31,46,49],{"href":47,"rel":48},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-saas-boilerplate-for-ai-agents",[35],"what ate our weekends",[11,51,52],{},"What starters routinely skip is the unglamorous middle layer: idempotent webhook architecture, production-grade billing state management, EU consent flows, subscription edge cases. \"Battle-tested UI components\" is a real thing. It does not mean \"battle-tested billing.\" Those are separate audits, and the second one is where the money lives.",[20,54,56],{"id":55},"boiledplate-vs-shipfast-stack-philosophy-and-trade-offs","BoiledPlate vs. ShipFast: Stack, Philosophy, and Trade-offs",[11,58,59,62],{},[15,60,61],{},"ShipFast"," is a Next.js boilerplate (Supabase, Stripe, Tailwind) with the largest ecosystem and fastest adoption in this category. If your team lives in React and you want a well-trodden path, it's a reasonable default.",[11,64,65,68,69,74],{},[15,66,67],{},"BoiledPlate"," is a Nuxt + Supabase + Stripe starter with a different center of gravity: it's ",[31,70,73],{"href":71,"rel":72},"https:\u002F\u002Fboiledplate.ai",[35],"AI-native and its setup runs itself",". Your coding agent interviews you, then provisions Stripe products and webhooks, a Supabase database with RLS, and Google sign-in — in one session, using deterministic patches.",[11,76,77],{},"The honest take: stack matters less than service integration quality. Choose based on where your expertise already is, whether you build with coding agents like Claude, and how much update-maintenance burden you're willing to carry. React shop with no agent workflow? ShipFast fits. Nuxt-comfortable, agent-driven, allergic to merge hell? Keep reading.",[20,79,81],{"id":80},"the-webhook-problem-nobody-talks-about","The Webhook Problem Nobody Talks About",[11,83,84,85,88],{},"Here is the thing every marketing page glosses over: ",[15,86,87],{},"delivery matters more than docs."," A webhook that fires but doesn't reliably land is worse than no webhook, because now your billing state lies to you.",[11,90,91,92,97],{},"Idempotency is a requirement, not a feature. Stripe retries. Networks time out mid-write. Two events race. If your handler runs twice and grants access twice, or charges twice, you've built a bug generator. The ",[31,93,96],{"href":94,"rel":95},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-webhooks-source-of-truth",[35],"checkout success page should never touch your billing state"," — the Stripe webhook is the source of truth, not the client redirect the user happened to see.",[11,99,100,101,106],{},"Refunds are where this gets sharp. We wrote a whole post on ",[31,102,105],{"href":103,"rel":104},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-github-invite-is-the-product-building-a-stripe-webhook-where-delivery-throws",[35],"a Stripe webhook where some failures must throw and some must never do",", because getting that distinction wrong either drops paying customers or floods your logs with false alarms.",[20,108,110],{"id":109},"agent-driven-setup-the-automation-layer-boilerplates-miss","Agent-Driven Setup: The Automation Layer Boilerplates Miss",[11,112,113],{},"Coding agents can do more than autocomplete templates — they can provision services. In BoiledPlate, the agent's first session interviews you (name, languages, theme, billing model), then reshapes the codebase to your answers with deterministic patches: automated, repeatable changes rather than copy-paste guesswork.",[11,115,116,117,120,121,126],{},"The glue that keeps this consistent is a shipped ",[15,118,119],{},"AGENTS.md"," contract — one documented way to do data access and secrets — so agent output doesn't drift. If you've watched an agent invent three different patterns for the same task, you understand why ",[31,122,125],{"href":123,"rel":124},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fconventions-for-ai-coding-agents",[35],"writing conventions for the agent, not the next hire"," is the real unlock. This closes the gap between \"generated a file\" and \"wired a working service.\"",[20,128,130],{"id":129},"database-security-that-doesnt-require-a-security-audit","Database Security That Doesn't Require a Security Audit",[11,132,133],{},"Supabase auth is the fast part. RLS is the part you forget — until someone reads a row they shouldn't. Row-level security enforced at query time should be the default, not an afterthought bolted on before launch.",[11,135,136],{},"The trap is that RLS looks simple and behaves subtly: a policy that works for the owner can silently over-share on a join, and it survives your first refactor only if you wrote it deliberately. A solid pattern isolates tenants at the database, not just in application code, and gets tested against real query paths before production — not discovered by a customer.",[20,138,140],{"id":139},"billing-edge-cases-the-unglamorous-reality","Billing Edge Cases: The Unglamorous Reality",[11,142,143],{},"Multi-plan subscriptions mean state transitions: upgrades, downgrades, cancellations, grace periods. Each one is a chance to corrupt state if the webhook and database disagree.",[11,145,146,147,152],{},"Then there's compliance. EU consent law isn't optional decoration — for digital goods, German law requires an explicit withdrawal waiver, and we documented exactly how to ",[31,148,151],{"href":149,"rel":150},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-checkout-consent-collection-german-withdrawal-waiver",[35],"encode that waiver into the pay button with Stripe Checkout consent_collection",". Refunds must reverse access without corrupting subscription state. Proration needs a deliberate policy. And webhook signature verification is your defense against forged events — the cheap line of code that prevents an expensive incident.",[20,154,156],{"id":155},"transactional-email-that-actually-arrives","Transactional Email That Actually Arrives",[11,158,159,160,164],{},"Resend paired with Supabase is a clean setup: simple to send, annoying to send ",[161,162,163],"em",{},"exactly once",". Verification flows fail silently more often than teams admit — the email \"sent,\" the user never got it, and support inherits the mystery.",[11,166,167],{},"Templates need to survive both theming and localization, which means your copy and your markup can't be hard-coupled. Receipts and invoices should generate from your billing events without a fourth external service in the mix.",[20,169,171],{"id":170},"seo-and-canonicals-why-these-matter-for-shipped-products","SEO and Canonicals: Why These Matter for Shipped Products",[11,173,174,175,180,181,37],{},"SEO-out-of-the-box saves weeks of debugging you didn't budget for. Two real bugs from our own build: a ",[31,176,179],{"href":177,"rel":178},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-page-that-returned-200-on-the-server-and-500-in-the-browser-a-json-ld-tempor",[35],"JSON-LD block that returned 200 from curl and 500 in the browser"," because of source order, and a blog that ",[31,182,185],{"href":183,"rel":184},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Four-blog-canonically-pointed-at-localhost",[35],"told Google its canonical URL was localhost:3000",[11,187,188,189,193],{},"Canonicals get harder with multi-language routes, ",[190,191,192],"code",{},"og:url"," needs to be correct for social sharing, and prerendered Markdown gives you a fast, indexable content foundation from day one. None of it is clever. All of it is the kind of thing that quietly tanks your launch if it ships broken.",[20,195,197],{"id":196},"typescript-end-to-end-what-strict-mode-actually-gives-you","TypeScript End-to-End: What \"Strict Mode\" Actually Gives You",[11,199,200],{},"Strict mode is worth the friction because billing bugs are the expensive kind, and catching them at compile time beats catching them in a chargeback. Type safety that spans API routes, database queries, and client state means a wrong shape fails your build, not your customer.",[11,202,203,204,215],{},"Typing Stripe webhooks correctly is the part nobody covers — event payloads are unions, and narrowing them properly is where most integrations get loose. And peer-dependency hell is real: we hit a case where ",[31,205,208,211,212],{"href":206,"rel":207},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fvercel-web-analytics-nuxt-4-analytics-package-breaks-typecheck",[35],[190,209,210],{},"@vercel\u002Fanalytics"," broke ",[190,213,214],{},"nuxt typecheck",". A boilerplate earns its price partly by having already absorbed those fights.",[20,217,219],{"id":218},"deployment-in-minutes-github-as-product-delivery","Deployment in Minutes: GitHub as Product Delivery",[11,221,222,223,226],{},"BoiledPlate ships via instant GitHub delivery — the invite ",[161,224,225],{},"is"," the product — rather than a download-and-configure ZIP. Service provisioning happens during onboarding, not as a scavenger hunt after. Environment variables, Docker for local Supabase, and Vercel\u002FNetlify deployment are part of the path, so getting to a live URL is a small number of decisions, not a weekend.",[20,228,230],{"id":229},"theming-and-customization-without-the-maintenance-tax","Theming and Customization Without the Maintenance Tax",[11,232,233],{},"You pick a dashboard theme in the setup interview — Warm Studio, Clean SaaS, Midnight Pro, Sharp Enterprise — or describe your own, and the agent maps it onto the codebase. These are real previews every buyer gets, not stock screenshots.",[11,235,236],{},"The harder problem is updating after you've customized. Semantic, agent-readable release notes make updates opt-in on code you've already changed — which is the actual answer to merge hell, not a promise that you'll never touch the source.",[20,238,240],{"id":239},"four-languages-from-day-one-i18n-that-doesnt-feel-bolted-on","Four Languages from Day One: i18n That Doesn't Feel Bolted On",[11,242,243],{},"Shipping with translation infrastructure beats retrofitting it, because a new locale string has to land in several places before the build stops complaining. BoiledPlate ships four languages with message management, component- and route-level switching, and copy structured so it survives A\u002FB testing instead of hard-coding English into your markup.",[20,245,247],{"id":246},"the-anti-plumbing-stack-why-these-tools-work-together","The Anti-Plumbing Stack: Why These Tools Work Together",[11,249,250,251,254,255,260],{},"Nuxt's ",[190,252,253],{},"server\u002F"," directory sits naturally next to Supabase RLS. Stripe's webhook model beats polling — and you genuinely can't cheat it; delivery is the contract. TypeScript strict mode plus agent-driven, convention-bound code means fewer surprises reach production. It's composition over configuration: fewer decisions to get wrong, more defaults that are already correct. We broke down ",[31,256,259],{"href":257,"rel":258},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-supabase-stripe-saas-boilerplate",[35],"what each piece really demands"," if you want the wiring in detail.",[20,262,264],{"id":263},"the-hidden-cost-of-faster-setup","The Hidden Cost of \"Faster Setup\"",[11,266,267,268,273,274,277],{},"Free tier or paid? ",[31,269,272],{"href":270,"rel":271},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Ffree-nuxt-supabase-saas-boilerplate",[35],"BoiledPlate Lite is MIT-licensed"," — clone it and wire manually if you enjoy the plumbing or want to inspect every seam. ",[15,275,276],{},"Pro"," is €159 one-time with lifetime updates and instant GitHub delivery.",[11,279,280],{},"\"Lifetime updates\" means something specific here: semantic versioning with agent-readable changes, so upgrades are legible rather than a diff you fear. Deterministic patches reduce forking risk by keeping customization structured. Open source buys transparency and trust; paid buys the absorbed edge cases.",[20,282,284],{"id":283},"metrics-that-matter-after-launch","Metrics That Matter After Launch",[11,286,287,288,293],{},"Track webhook delivery success rate and retry behavior. Watch RLS query performance under load. Monitor email delivery and bounce rates. Verify billing-state consistency across refunds and cancellations. And review which agent-driven customizations held up — that feedback loop is how your setup stays trustworthy. Stripe's own ",[31,289,292],{"href":290,"rel":291},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks\u002Fbest-practices",[35],"webhook best practices"," are worth bookmarking here.",[20,295,297],{"id":296},"the-decision-framework-is-a-boilerplate-worth-your-time","The Decision Framework: Is a Boilerplate Worth Your Time?",[11,299,300,301,303],{},"DIY plumbing is faster than a good boilerplate roughly never — and when it ",[161,302,225],{},", it's because your requirements are so unusual that no template fits. Evaluate any starter by three things: the quality of its billing implementation, whether security is default or afterthought, and how its agent design handles drift.",[11,305,306,307,310,311,316],{},"Refactoring a bad foundation costs more than the upfront investment in a good one. Before you commit to any ",[15,308,309],{},"shipfast-style template",", ask: How does it handle webhook idempotency? Are RLS policies tested? What happens to billing state on a refund? If the answers are vague, the plumbing is still yours to build. Skim ",[31,312,315],{"href":313,"rel":314},"https:\u002F\u002Fboiledplate.ai\u002Fblog",[35],"the blog"," — the questions worth asking are the ones we kept a running log of.",{"title":318,"searchDepth":319,"depth":319,"links":320},"",3,[321,323,324,325,326,327,328,329,330,331,332,333,334,335,336,337,338],{"id":22,"depth":322,"text":23},2,{"id":40,"depth":322,"text":41},{"id":55,"depth":322,"text":56},{"id":80,"depth":322,"text":81},{"id":109,"depth":322,"text":110},{"id":129,"depth":322,"text":130},{"id":139,"depth":322,"text":140},{"id":155,"depth":322,"text":156},{"id":170,"depth":322,"text":171},{"id":196,"depth":322,"text":197},{"id":218,"depth":322,"text":219},{"id":229,"depth":322,"text":230},{"id":239,"depth":322,"text":240},{"id":246,"depth":322,"text":247},{"id":263,"depth":322,"text":264},{"id":283,"depth":322,"text":284},{"id":296,"depth":322,"text":297},"2026-09-10","Discover why a quality shipfast template matters more than your framework. Learn how service integration and plumbing separate fast shipping from slow debugging.",false,"md",{},true,"\u002Fblog\u002Fshipfast-template-boilerplate-quality",{"title":5,"description":340},"blog\u002Fshipfast-template-boilerplate-quality",[349,350,351,352],"shipfast","boilerplate","saas-development","starter-templates","BzjDbCW8Cnp_xkO7YxbpPG3il5Bl8s0lq5G6DArHov4",[355,707,1039],{"id":356,"title":357,"author":6,"body":358,"category":6,"date":696,"description":697,"draft":341,"extension":342,"image":6,"meta":698,"navigation":344,"path":699,"seo":700,"stem":701,"tags":702,"__hash__":706},"blog\u002Fblog\u002Fshipfast-tech-vs-boiledplate-saas-boilerplate.md","ShipFast Tech vs BoiledPlate: SaaS Boilerplate Comparison",{"type":8,"value":359,"toc":670},[360,363,367,370,373,377,385,390,407,415,419,422,425,429,433,442,446,454,457,461,465,472,476,479,483,495,499,503,506,510,520,524,527,573,579,585,589,602,605,609,612,615,618,622,638,642,648,654,660,664,667],[11,361,362],{},"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.",[20,364,366],{"id":365},"what-this-comparison-actually-covers","What This Comparison Actually Covers",[11,368,369],{},"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.",[11,371,372],{},"\"Days not weeks\" means different things depending on which of those workflows you buy into. Let's look at where the weeks actually hide.",[20,374,376],{"id":375},"the-plumbing-layer-where-weeks-actually-hide","The Plumbing Layer: Where Weeks Actually Hide",[11,378,379,380,384],{},"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 ",[31,381,383],{"href":33,"rel":382},[35],"how to ship SaaS fast: the stack is easy, the plumbing is the project",". The framework is not what slows you down.",[386,387,389],"h3",{"id":388},"webhook-architecture-the-invisible-complexity","Webhook Architecture: The Invisible Complexity",[11,391,392,393,396,397,400,401,406],{},"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 ",[190,394,395],{},"subscription.updated"," before ",[190,398,399],{},"subscription.created",". Stripe's own ",[31,402,405],{"href":403,"rel":404},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks",[35],"webhook documentation"," warns you to respond within seconds and process asynchronously.",[11,408,409,410,414],{},"Most boilerplates ship a happy-path handler and call it done. BoiledPlate treats ",[31,411,413],{"href":94,"rel":412},[35],"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.",[386,416,418],{"id":417},"deterministic-patches-vs-manual-wiring","Deterministic Patches vs Manual Wiring",[11,420,421],{},"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.",[11,423,424],{},"If a coding agent is part of your daily workflow, that difference compounds over the life of the project.",[20,426,428],{"id":427},"billing-edge-cases-that-swallow-weeks","Billing Edge Cases That Swallow Weeks",[386,430,432],{"id":431},"subscription-state-management","Subscription State Management",[11,434,435,436,441],{},"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 ",[31,437,440],{"href":438,"rel":439},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-subscriptions-nuxt-supabase",[35],"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.",[386,443,445],{"id":444},"eu-compliance-and-refund-flows","EU Compliance and Refund Flows",[11,447,448,449,453],{},"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 ",[31,450,452],{"href":149,"rel":451},[35],"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.",[11,455,456],{},"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.",[20,458,460],{"id":459},"architecture-comparison-nextjs-vs-nuxt-supabase","Architecture Comparison: Next.js vs Nuxt + Supabase",[386,462,464],{"id":463},"why-boiledplate-chose-nuxt-supabase","Why BoiledPlate Chose Nuxt + Supabase",[11,466,467,468,37],{},"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 ",[31,469,471],{"href":257,"rel":470},[35],"what it actually takes to wire up a Nuxt, Supabase and Stripe SaaS",[386,473,475],{"id":474},"shipfasts-nextjs-stack","ShipFast's Next.js Stack",[11,477,478],{},"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.",[386,480,482],{"id":481},"the-anti-plumbing-stack-question","The Anti-Plumbing Stack Question",[11,484,485,486,489,490,494],{},"Do these tools prevent plumbing, or just hide it? Honestly, neither eliminates it. The difference is ",[161,487,488],{},"where"," it's hidden. BoiledPlate hides it in agent-driven setup, deterministic patches, and an ",[31,491,493],{"href":123,"rel":492},[35],"AGENTS.md convention contract"," that keeps agent output consistent. ShipFast hides it in battle-tested code you clone and customize by hand.",[20,496,498],{"id":497},"agent-driven-setup-the-overlooked-differentiator","Agent-Driven Setup: The Overlooked Differentiator",[386,500,502],{"id":501},"the-interview-model","The Interview Model",[11,504,505],{},"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.",[386,507,509],{"id":508},"agentsmd-a-data-access-contract","AGENTS.md: A Data Access Contract",[11,511,512,515,516,37],{},[31,513,119],{"href":123,"rel":514},[35]," 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 ",[31,517,519],{"href":47,"rel":518},[35],"every boilerplate ships the stack — that was never the hard part",[20,521,523],{"id":522},"feature-parity-what-both-ship","Feature Parity: What Both Ship",[11,525,526],{},"On the checklist, they overlap more than they differ:",[528,529,530,537,543,549,555,561,567],"ul",{},[531,532,533,536],"li",{},[15,534,535],{},"Auth",": both ship it; quality differs on RLS enforcement.",[531,538,539,542],{},[15,540,541],{},"Stripe",": both ship it; webhook robustness varies.",[531,544,545,548],{},[15,546,547],{},"Database",": ShipFast flexible; BoiledPlate opinionated on Supabase.",[531,550,551,554],{},[15,552,553],{},"Transactional email",": both; BoiledPlate defaults to Resend.",[531,556,557,560],{},[15,558,559],{},"i18n",": BoiledPlate ships four languages by default; ShipFast optional.",[531,562,563,566],{},[15,564,565],{},"Blog",": BoiledPlate prerenders Markdown; ShipFast is ecosystem-dependent.",[531,568,569,572],{},[15,570,571],{},"Theming",": both; BoiledPlate lets you pick a preset or describe a custom theme in the setup interview.",[11,574,575,578],{},[15,576,577],{},"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.",[11,580,581,584],{},[15,582,583],{},"ShipFast-specific:"," larger ecosystem, more third-party integrations, a longer track record, more community templates, and freedom over database and backend choice.",[20,586,588],{"id":587},"pricing-and-delivery","Pricing and Delivery",[11,590,591,592,596,597,601],{},"BoiledPlate is €159 one-time with lifetime updates and instant ",[31,593,595],{"href":71,"rel":594},[35],"GitHub delivery"," — the repo is cloned into your account via webhook — plus a free, MIT-licensed ",[31,598,600],{"href":270,"rel":599},[35],"Lite tier"," you can wire up manually. ShipFast runs roughly $129–$199 one-time depending on tier, with traditional download-and-clone delivery.",[11,603,604],{},"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.",[20,606,608],{"id":607},"real-world-shipping-time-an-honest-breakdown","Real-World Shipping Time: An Honest Breakdown",[11,610,611],{},"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.",[11,613,614],{},"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.",[11,616,617],{},"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.",[20,619,621],{"id":620},"common-bugs-both-stacks-hit","Common Bugs Both Stacks Hit",[11,623,624,625,629,630,633,634,37],{},"Real launches trip on real bugs. Incorrect JSON-LD can crash hydration — we shipped a page that ",[31,626,628],{"href":177,"rel":627},[35],"returned 200 from curl and 500 in Chrome"," because of source order. Canonical URLs are easy to break in multilingual sites; our blog once ",[31,631,185],{"href":183,"rel":632},[35],". And delivery-critical webhooks need careful failure semantics — some failures must throw, some never should, which we unpack in ",[31,635,637],{"href":103,"rel":636},[35],"the GitHub invite is the product",[20,639,641],{"id":640},"who-should-pick-which","Who Should Pick Which",[11,643,644,647],{},[15,645,646],{},"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.",[11,649,650,653],{},[15,651,652],{},"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.",[11,655,656,659],{},[15,657,658],{},"Don't decide on"," framework popularity or \"faster shipping\" alone. Both hit the same plumbing wall.",[20,661,663],{"id":662},"the-real-lesson","The Real Lesson",[11,665,666],{},"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.",[11,668,669],{},"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.",{"title":318,"searchDepth":319,"depth":319,"links":671},[672,673,677,681,686,690,691,692,693,694,695],{"id":365,"depth":322,"text":366},{"id":375,"depth":322,"text":376,"children":674},[675,676],{"id":388,"depth":319,"text":389},{"id":417,"depth":319,"text":418},{"id":427,"depth":322,"text":428,"children":678},[679,680],{"id":431,"depth":319,"text":432},{"id":444,"depth":319,"text":445},{"id":459,"depth":322,"text":460,"children":682},[683,684,685],{"id":463,"depth":319,"text":464},{"id":474,"depth":319,"text":475},{"id":481,"depth":319,"text":482},{"id":497,"depth":322,"text":498,"children":687},[688,689],{"id":501,"depth":319,"text":502},{"id":508,"depth":319,"text":509},{"id":522,"depth":322,"text":523},{"id":587,"depth":322,"text":588},{"id":607,"depth":322,"text":608},{"id":620,"depth":322,"text":621},{"id":640,"depth":322,"text":641},{"id":662,"depth":322,"text":663},"2026-09-09","Compare ShipFast and BoiledPlate SaaS boilerplates. Learn which Next.js or Nuxt template gets you to production fastest with minimal plumbing headaches.",{},"\u002Fblog\u002Fshipfast-tech-vs-boiledplate-saas-boilerplate",{"title":357,"description":697},"blog\u002Fshipfast-tech-vs-boiledplate-saas-boilerplate",[703,349,704,705],"saas-boilerplate","nuxt","next.js","JOhPGmMdHqpb4AXq6DZI6kqDMsQ47_s_iUq70C7tQ14",{"id":708,"title":709,"author":6,"body":710,"category":6,"date":1031,"description":1032,"draft":341,"extension":342,"image":6,"meta":1033,"navigation":344,"path":1034,"seo":1035,"stem":1036,"tags":1037,"__hash__":1038},"blog\u002Fblog\u002Fshipfast-source-code-analysis.md","ShipFast Source Code: A Real Developer's Analysis",{"type":8,"value":711,"toc":1010},[712,715,719,722,729,732,736,747,750,758,761,773,777,780,790,794,797,829,832,836,843,846,850,858,862,865,882,885,889,908,912,918,922,933,937,940,944,947,951,957,961,964,968,971,975,986,990,1001],[11,713,714],{},"Search \"shipfast source code\" and you find the same story repeated: a Next.js boilerplate that's closed until you pay, a handful of forks trying to recreate it, and threads of developers asking whether any of it is worth the money. The honest answer buried in those threads is worth pulling out: the code was never the hard part. This is a comparison for developers who already know that — and who want a Nuxt + Supabase alternative built around it.",[20,716,718],{"id":717},"the-saas-starter-problem-nobody-talks-about","The SaaS Starter Problem Nobody Talks About",[11,720,721],{},"Every boilerplate sells you a feature checklist. Auth, payments, email, a landing page. Those features are real, but choosing them is roughly 10% of the work. The other 90% is wiring the services into something that survives a real customer: idempotent webhooks, row-level security, refunds, EU consent flows. \"Production-ready code\" claims quietly skip that part, because the plumbing is where launches actually stall.",[11,723,724,725,728],{},"We wrote about this at length in ",[31,726,383],{"href":33,"rel":727},[35],". The framework picks itself in an afternoon. The wiring is the project.",[11,730,731],{},"So when you compare boilerplates, look past the feature grid. Ask how each one handles webhook retries, how it configures RLS, and what happens when Stripe sends the same event twice.",[20,733,735],{"id":734},"what-shipfast-does-and-doesnt","What ShipFast Does (And Doesn't)",[11,737,738,739,742,743,746],{},"ShipFast is a Next.js boilerplate that ships a complete codebase after purchase. Its pitch — \"launch in days, not weeks,\" and now \"give your AI editor real context to build features\" — is well-earned marketing. You do get full source code after buying, and the community forks (like ",[190,740,741],{},"vietanhdev\u002Fshipfast"," and ",[190,744,745],{},"krishna-praveen\u002Fshipfast-template-1",") show people rebuilding the pattern in the open.",[11,748,749],{},"Two things it doesn't do. First, it's closed until you pay, which is why \"honest review\" threads keep pointing at open-source alternatives. Second, it's Next.js-locked. If your workflow, deployment target, or team lives in Nuxt, a Next.js boilerplate is a permanent tax, not a head start. And \"time to first customer\" claims of five minutes describe running the template locally — not billing that survives production.",[20,751,753,754],{"id":752},"why-nuxt-supabase-stripe-beats-nextjs-alternative-stack","Why Nuxt + Supabase + Stripe Beats Next.js + ",[755,756,757],"span",{},"Alternative Stack",[11,759,760],{},"Framework compatibility matters more than any marketing bullet. If you're already productive in Nuxt, its SSR\u002FSSG defaults and edge-friendly runtime are a better fit than fighting a different framework's conventions.",[11,762,763,764,768,769,37],{},"The rest of the stack earns its place too. Supabase gives you Postgres with ",[31,765,767],{"href":257,"rel":766},[35],"row-level security"," enforced at query time — application security that isn't bolted on afterward. And Stripe webhooks, not client-side success pages, are the source of truth for billing state. We made that argument in full in ",[31,770,772],{"href":94,"rel":771},[35],"your checkout success page should not touch your billing state",[20,774,776],{"id":775},"boiledplates-agent-first-architecture","BoiledPlate's Agent-First Architecture",[11,778,779],{},"\"AI-native\" gets thrown around loosely. Here it has a specific meaning: your coding agent's first session interviews you — name, languages, theme, billing model — then reshapes the entire codebase to your answers using deterministic patches. Not a plugin. A setup that runs itself.",[11,781,782,783,785,786,37],{},"Deterministic patches matter because they're repeatable. Manual wiring drifts; automated, testable changes don't. And to keep an agent consistent across sessions, BoiledPlate ships an ",[190,784,119],{}," contract: one documented way to do data access and secrets, so the agent doesn't reinvent conventions each time. We explain why that file matters in ",[31,787,789],{"href":123,"rel":788},[35],"write your conventions for the agent, not the next hire",[20,791,793],{"id":792},"the-plumbing-nobody-enjoys","The Plumbing Nobody Enjoys",[11,795,796],{},"This is the 90%, and it's what BoiledPlate automates.",[528,798,799,805,811,817,823],{},[531,800,801,804],{},[15,802,803],{},"Webhook idempotency"," is the line between \"deployed\" and \"in production.\" Stripe will retry; your handler has to process each event exactly once.",[531,806,807,810],{},[15,808,809],{},"Row-level security"," is easier to get wrong than right. Auth is the fast part; the RLS policies are the part people forget until data leaks.",[531,812,813,816],{},[15,814,815],{},"Multi-plan subscriptions and refunds"," need real state management, not a single price ID.",[531,818,819,822],{},[15,820,821],{},"Google sign-in plus email auth"," without disappearing down the OAuth rabbit hole.",[531,824,825,828],{},[15,826,827],{},"Resend"," for transactional mail — simple to send, genuinely annoying to send exactly once.",[11,830,831],{},"BoiledPlate provisions Supabase, Stripe products and webhooks, and Google sign-in in one session, so this list stops being your first two weeks.",[20,833,835],{"id":834},"billing-edge-cases-that-sink-founders","Billing Edge Cases That Sink Founders",[11,837,838,839,37],{},"The edge cases are where founders bleed. EU consent law is a good example: selling a digital product in Germany often means encoding a withdrawal-right waiver into the pay button itself. We documented that exact implementation in ",[31,840,842],{"href":149,"rel":841},[35],"Stripe Checkout consent_collection",[11,844,845],{},"Then there's refund idempotency and state reconciliation, cancellation timing and proration, and the quiet lie of client-side success pages — which happily tell a user they're subscribed while your database says nothing happened. Billing state has to be reconciled from webhooks, not from the browser.",[20,847,849],{"id":848},"customization-without-merge-hell","Customization Without Merge Hell",[11,851,852,853,857],{},"Most starters rot the moment you customize them: the next update becomes a merge fight. BoiledPlate ships semantic, agent-readable release notes and opt-in updates to your already-customized code. Delivery is Git-based — GitHub invites are literally the distribution mechanism, which we unpack in ",[31,854,856],{"href":103,"rel":855},[35],"the GitHub invite IS the product",". At some point cloning a static template stops making sense, and a maintained, updatable codebase wins.",[20,859,861],{"id":860},"open-source-vs-paid-the-boiledplate-tiers","Open Source vs. Paid: The BoiledPlate Tiers",[11,863,864],{},"There are two tiers.",[528,866,867,877],{},[531,868,869,872,873,37],{},[15,870,871],{},"Lite"," is free and MIT-licensed: Supabase auth, Stripe billing, transactional email, a blog, and i18n on Nuxt 4. You clone it and wire it up by hand. Full details in ",[31,874,876],{"href":270,"rel":875},[35],"the free Nuxt + Supabase SaaS boilerplate post",[531,878,879,881],{},[15,880,276],{}," is €159 one-time, with lifetime updates and instant delivery via GitHub. It's the same app plus the AI tooling that makes setup run itself.",[11,883,884],{},"\"Instant GitHub delivery\" means a webhook adds you to the repository on purchase. And €159 once, versus recurring SaaS tooling costs, is easy math for a solo builder.",[20,886,888],{"id":887},"real-world-bugs-and-lessons-learned","Real-World Bugs and Lessons Learned",[11,890,891,892,896,897,900,901,907],{},"Shipping fast means debugging faster, and BoiledPlate's blog is a running log of the bugs it took to make the plumbing trustworthy. A JSON-LD block returned ",[31,893,895],{"href":177,"rel":894},[35],"200 from curl and 500 in Chrome"," because of SSR source order. The blog once ",[31,898,185],{"href":183,"rel":899},[35],". And a peer-dependency conflict from ",[31,902,904,906],{"href":206,"rel":903},[35],[190,905,210],{}," broke Nuxt typecheck",". These aren't hypotheticals — they're the edge cases a boilerplate should have already absorbed.",[20,909,911],{"id":910},"language-and-localization-from-day-one","Language and Localization from Day One",[11,913,914,915,917],{},"BoiledPlate ships four languages prebuilt. i18n done late fractures your codebase; strings scattered everywhere, routes duplicated, canonicals misfiring. Done early — with proper ",[190,916,192],{}," canonicals per locale — it's an SEO asset instead of a liability. Nuxt's i18n is the tax on doing this right, and it's paid up front here.",[20,919,921],{"id":920},"the-blog-thats-actually-ready-to-write","The Blog That's Actually Ready to Write",[11,923,924,925,927,928,932],{},"Content is organic reach, and blogging shouldn't require yet another tool. BoiledPlate's blog is prerendered Markdown with TypeScript frontmatter, wired with JSON-LD and ",[190,926,192],{}," canonicals out of the box. You write a file; it ships. The ",[31,929,931],{"href":313,"rel":930},[35],"BoiledPlate blog"," itself runs on exactly this.",[20,934,936],{"id":935},"typed-end-to-end","Typed End to End",[11,938,939],{},"TypeScript strict mode isn't decoration. Type safety flows across Supabase queries, Stripe webhook payloads, and API routes, which means a mismatched billing field is a compile error, not a 2 a.m. production incident. A starter that enforces correctness is a better developer experience than one that trusts you to remember everything.",[20,941,943],{"id":942},"dashboard-theming-and-white-label","Dashboard Theming and White-Label",[11,945,946],{},"Theming shouldn't spawn a CSS-in-JS debate. Pick a preset in the setup interview — Warm Studio, Clean SaaS, Midnight Pro, Sharp Enterprise — or describe your brand and the agent maps it onto the codebase. Every buyer gets real previews of the dashboard they'll ship. Template to product in minutes, without a styling detour.",[20,948,950],{"id":949},"deployment-reality-check","Deployment Reality Check",[11,952,953,954,956],{},"\"Deploy in minutes\" is honest only if you separate it from \"running locally.\" Real deployment means Supabase migrations applied in the right order, RLS policies live, environment variables mapped correctly, and secrets handled per the ",[190,955,119],{}," contract. Nuxt's edge runtime keeps cold starts and time-to-first-byte reasonable, but the migration and secrets step is where careless setups break. BoiledPlate's provisioning handles the parts people skip.",[20,958,960],{"id":959},"when-to-choose-boiledplate-over-alternatives","When to Choose BoiledPlate Over Alternatives",[11,962,963],{},"Choose it if you're already comfortable in Nuxt and Supabase, if you work with Claude or a similar coding agent, if billing complexity matters more to you than a longer feature list, and if you'd rather pay once for lifetime updates than rent your tooling monthly.",[20,965,967],{"id":966},"when-boiledplate-isnt-the-right-fit","When BoiledPlate Isn't the Right Fit",[11,969,970],{},"Be honest about the trade-offs. If your ecosystem is Next.js-locked, a Next.js boilerplate like ShipFast is the lower-friction choice. If your team is married to Auth0 or Clerk, BoiledPlate's Supabase-first auth is a poor match. And if you're building a headless-first or pure API architecture, a full-stack SaaS starter isn't your shape. No tool wins every fit.",[20,972,974],{"id":973},"getting-started-lite-vs-pro","Getting Started: Lite vs. Pro",[11,976,977,978,981,982,985],{},"With ",[31,979,871],{"href":270,"rel":980},[35]," you clone and wire manually — a good way to learn the seams. With ",[31,983,276],{"href":71,"rel":984},[35],", the €159 buys an agent-driven, one-session setup: the interview, the deterministic patches, provisioned services, and instant GitHub delivery. Common first-week mistakes are the usual suspects — trusting the success page over the webhook, or forgetting an RLS policy — and the codebase is built to steer you away from both.",[20,987,989],{"id":988},"the-coding-agent-advantage-nobody-mentions","The Coding Agent Advantage Nobody Mentions",[11,991,992,993,995,996,1000],{},"Agents are powerful and forgetful. Without conventions they drift, reinventing your data-access pattern every session. ",[190,994,119],{}," is the guardrail. The ",[31,997,999],{"href":438,"rel":998},[35],"Stripe subscriptions guide"," shows the kind of decision an interview-driven setup makes for you instead of leaving it to chance. Once the plumbing is contracted and consistent, the agent's real job begins: building your actual features on a foundation that already works.",[11,1002,1003,1004,1009],{},"For a deeper reference on how Stripe expects webhooks to be verified and made idempotent, the ",[31,1005,1008],{"href":1006,"rel":1007},"https:\u002F\u002Fstripe.com\u002Fdocs\u002Fwebhooks",[35],"official Stripe webhooks documentation"," is worth reading alongside this — because whichever boilerplate you pick, that's the part that has to be right.",{"title":318,"searchDepth":319,"depth":319,"links":1011},[1012,1013,1014,1016,1017,1018,1019,1020,1021,1022,1023,1024,1025,1026,1027,1028,1029,1030],{"id":717,"depth":322,"text":718},{"id":734,"depth":322,"text":735},{"id":752,"depth":322,"text":1015},"Why Nuxt + Supabase + Stripe Beats Next.js + Alternative Stack",{"id":775,"depth":322,"text":776},{"id":792,"depth":322,"text":793},{"id":834,"depth":322,"text":835},{"id":848,"depth":322,"text":849},{"id":860,"depth":322,"text":861},{"id":887,"depth":322,"text":888},{"id":910,"depth":322,"text":911},{"id":920,"depth":322,"text":921},{"id":935,"depth":322,"text":936},{"id":942,"depth":322,"text":943},{"id":949,"depth":322,"text":950},{"id":959,"depth":322,"text":960},{"id":966,"depth":322,"text":967},{"id":973,"depth":322,"text":974},{"id":988,"depth":322,"text":989},"2026-09-08","Explore ShipFast source code alternatives. Compare Next.js and Nuxt boilerplates for SaaS—beyond the feature checklist to production-ready plumbing.",{},"\u002Fblog\u002Fshipfast-source-code-analysis",{"title":709,"description":1032},"blog\u002Fshipfast-source-code-analysis",[349,703,705,704],"K4qljmp3ZHCA3PVMZfWVXde90eBZ0TxzUNzj2pi5JA8",{"id":1040,"title":1041,"author":6,"body":1042,"category":6,"date":1408,"description":1409,"draft":341,"extension":342,"image":6,"meta":1410,"navigation":344,"path":1411,"seo":1412,"stem":1413,"tags":1414,"__hash__":1417},"blog\u002Fblog\u002Fshipfast-saas-boilerplate-comparison.md","ShipFast vs BoiledPlate: SaaS Boilerplate Comparison",{"type":8,"value":1043,"toc":1389},[1044,1047,1051,1054,1057,1061,1069,1072,1089,1092,1096,1099,1107,1111,1114,1117,1121,1130,1138,1145,1149,1152,1159,1163,1170,1173,1177,1185,1189,1197,1201,1204,1208,1215,1218,1222,1225,1228,1232,1235,1239,1242,1246,1362,1365,1369,1372,1376],[11,1045,1046],{},"ShipFast made \"launch in days, not weeks\" a rallying cry, and for good reason: a Next.js boilerplate with auth, Stripe, and battle-tested UI components saves real time. But if you've actually shipped a SaaS, you know the template is the easy part. The weeks disappear in the wiring — webhook idempotency, RLS policies, refund flows, EU consent. This is where an AI-native starter changes the math. Here's an honest comparison of ShipFast against BoiledPlate, and why the plumbing is the whole game.",[20,1048,1050],{"id":1049},"what-shipfast-does-and-what-it-doesnt","What ShipFast Does (And What It Doesn't)",[11,1052,1053],{},"ShipFast is a Next.js SaaS boilerplate. It ships authentication, Stripe payments, a UI component library, email scaffolding, and sensible defaults. It's popular because it's genuinely good at what it is: a code template you clone and customize.",[11,1055,1056],{},"What it doesn't do is provision anything. You still create your Stripe products, configure webhooks, verify signatures, design your database schema, write RLS policies, set up Google OAuth, and wire your environment variables by hand. ShipFast hands you the code. The infrastructure is your job. For teams comfortable with that setup overhead, that's a fair trade.",[20,1058,1060],{"id":1059},"the-real-problem-with-manual-saas-setup","The Real Problem With Manual SaaS Setup",[11,1062,1063,1064,1068],{},"Choosing a stack takes an afternoon. Wiring four services into something trustworthy takes weeks. We know because we ",[31,1065,1067],{"href":257,"rel":1066},[35],"logged every edge case it took"," to make ours reliable.",[11,1070,1071],{},"The list is longer than it looks:",[528,1073,1074,1077,1080,1083,1086],{},[531,1075,1076],{},"Stripe product creation, price objects, webhook endpoints, signature verification",[531,1078,1079],{},"Supabase schema design, migrations, and RLS policies that actually isolate tenants",[531,1081,1082],{},"Google OAuth setup, redirect URIs, token handling",[531,1084,1085],{},"Transactional email (Resend or SendGrid) that sends exactly once",[531,1087,1088],{},"Testing all of it before a real customer hits it",[11,1090,1091],{},"Most boilerplates, ShipFast included, leave you at the starting line of this list.",[20,1093,1095],{"id":1094},"boiledplate-agent-driven-provisioning-not-just-code","BoiledPlate: Agent-Driven Provisioning, Not Just Code",[11,1097,1098],{},"BoiledPlate is an AI-native Nuxt + Supabase starter whose setup runs itself. Instead of handing you a template to customize, an AI coding agent interviews you — name, languages, theme, billing model — then reshapes the entire codebase with deterministic patches and provisions your services.",[11,1100,1101,1102,1106],{},"In a single session, your agent creates Stripe products and webhooks, stands up a Supabase database with row-level security, and configures Google sign-in. As the ",[31,1103,1105],{"href":71,"rel":1104},[35],"homepage"," puts it: your coding agent doesn't just write the code — it provisions the services. That's the categorical difference from a code-only template.",[20,1108,1110],{"id":1109},"nuxt-supabase-stripe-why-this-stack-works-together","Nuxt + Supabase + Stripe: Why This Stack Works Together",[11,1112,1113],{},"The stack is deliberate. Nuxt's server routes map cleanly onto webhook handlers. Supabase RLS enforces billing state at the database layer, not in fragile client-side logic. Stripe webhooks are the source of truth for subscription state. TypeScript strict mode runs end to end, so fewer surprises reach production.",[11,1115,1116],{},"Next.js, ShipFast's foundation, is excellent — but it tends to demand more glue code to reach the same guarantees, especially around server-side billing state.",[20,1118,1120],{"id":1119},"idempotent-webhooks-the-plumbing-nobody-talks-about","Idempotent Webhooks: The Plumbing Nobody Talks About",[11,1122,1123,1124,1129],{},"Webhook delivery matters more than UI elegance, because a dropped or duplicated event corrupts billing state silently. Stripe ",[31,1125,1128],{"href":1126,"rel":1127},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks#handle-duplicate-events",[35],"explicitly recommends"," handling duplicate events, because it will send them.",[11,1131,1132,1133,1137],{},"BoiledPlate's webhook handling is idempotent by design: repeated Stripe events don't double-apply side effects, signatures are verified to block replay attacks, and refund flows don't corrupt subscription state. We wrote about the harder version of this problem — ",[31,1134,1136],{"href":103,"rel":1135},[35],"a Stripe webhook where some failures must throw and some never should"," — because the difference between a retry and a permanent failure is where real bugs live.",[11,1139,1140,1141,1144],{},"A related principle: ",[31,1142,772],{"href":94,"rel":1143},[35],". The webhook is the source of truth. The success page is just a redirect.",[20,1146,1148],{"id":1147},"row-level-security-database-enforced-billing","Row-Level Security: Database-Enforced Billing",[11,1150,1151],{},"Client-side permission checks are suggestions. RLS is enforcement. BoiledPlate enforces multi-tenant isolation at query time, so a query that would leak another tenant's data is simply impossible to write, not merely discouraged by middleware.",[11,1153,1154,1155,1158],{},"This also carries into compliance. EU rules around German withdrawal waivers and consent flows aren't optional if you sell there, and we encoded one directly into ",[31,1156,452],{"href":149,"rel":1157},[35],". Database-enforced billing plus correct consent is the unglamorous part that keeps you out of trouble.",[20,1160,1162],{"id":1161},"agent-consistency-the-agentsmd-contract","Agent Consistency: The AGENTS.md Contract",[11,1164,1165,1166,1169],{},"Coding agents drift without conventions. Ask Claude the same question twice and you may get two different data-access patterns. BoiledPlate ships an AGENTS.md contract: one documented way to read secrets and access data, so agent output stays consistent. We argue you should ",[31,1167,789],{"href":123,"rel":1168},[35]," — the agent reads them every session.",[11,1171,1172],{},"Deterministic patches make customization repeatable, and semantic, agent-readable release notes let your agent understand what changed. Updates are opt-in, applied to your customized code without a merge-hell rewrite.",[20,1174,1176],{"id":1175},"billing-edge-cases-that-bite-you-later","Billing Edge Cases That Bite You Later",[11,1178,1179,1180,1184],{},"Subscriptions aren't binary. They transition: active, grace period, past due, canceled. Layer in refund idempotency, double-refund prevention, proration on mid-cycle plan changes, and failed-payment dunning retries, and you have a matrix that's easy to get wrong. Manual setup means debugging these at 2 AM after a customer complaint. BoiledPlate's ",[31,1181,1183],{"href":438,"rel":1182},[35],"Stripe subscription setup"," handles these transitions as designed behavior, not afterthoughts.",[20,1186,1188],{"id":1187},"transactional-email-and-seo-not-afterthoughts","Transactional Email and SEO: Not Afterthoughts",[11,1190,1191,1192,1196],{},"Email verification and receipts affect churn, so Resend is integrated, not bolted on later — including sending exactly once, which is harder than it sounds. On SEO, starter kits routinely ship broken defaults. We shipped one ourselves: ",[31,1193,1195],{"href":183,"rel":1194},[35],"our blog told Google its canonical URL was localhost:3000",". BoiledPlate ships JSON-LD structured data, correct og:url canonicals, and a prerendered Markdown blog — correct by default, customizable after.",[20,1198,1200],{"id":1199},"internationalization-from-day-one","Internationalization from Day One",[11,1202,1203],{},"Four languages ship out of the box. This matters because adding i18n later means refactoring every string, route, and email template. Retrofitting is the \"we'll translate later\" trap that never gets untrapped. Building on top of existing i18n is cheap; grafting it on afterward is not.",[20,1205,1207],{"id":1206},"free-vs-paid-boiledplate-lite-vs-pro","Free vs. Paid: BoiledPlate Lite vs. Pro",[11,1209,1210,1214],{},[31,1211,1213],{"href":270,"rel":1212},[35],"BoiledPlate Lite"," is free and MIT-licensed: the same Nuxt 4, Supabase, Stripe, and Resend app, minus the AI tooling. You clone it and wire it by hand — much like using ShipFast, but Vue-based instead of React.",[11,1216,1217],{},"Pro is €159 one-time, with lifetime updates and instant delivery via GitHub. It includes the agent-driven provisioning: the interview, the deterministic patches, the whole set-itself-up experience. Honestly: Lite is more work, Pro is instant. Pick Lite if you enjoy the wiring or want to inspect everything first; pick Pro if you'd rather ship product.",[20,1219,1221],{"id":1220},"dashboard-theming-deployment-and-typescript","Dashboard Theming, Deployment, and TypeScript",[11,1223,1224],{},"Theming is part of the interview: pick a preset (Warm Studio, Clean SaaS, Midnight Pro, Sharp Enterprise) or describe your own colors in plain language, and the agent maps it onto the codebase. Deployment runs in minutes to Vercel, Netlify, or self-hosted — and because the agent interview handles environment variables and provisioning, the classic first-run friction (missing keys, misconfigured webhooks) largely disappears.",[11,1226,1227],{},"TypeScript strict mode is enforced, not optional. The cost is more upfront friction; the benefit is catching edge cases before production instead of after.",[20,1229,1231],{"id":1230},"github-delivery-the-product-is-your-code","GitHub Delivery: The Product Is Your Code",[11,1233,1234],{},"When you buy Pro, you get a GitHub repo. That's the product. Your code, in your control, from day one — no locked-in SaaS platform, no managed builder holding your app hostage. This is the opposite of \"no-code\" platforms where you rent your product forever.",[20,1236,1238],{"id":1237},"honest-gaps-and-trade-offs","Honest Gaps and Trade-Offs",[11,1240,1241],{},"BoiledPlate uses Nuxt, so if you're committed to Next.js or React, ShipFast is the better fit. Supabase is opinionated — no swapping in Firebase. Stripe is non-negotiable for the subscription logic. And it's not a visual builder; you're still coding. If you need a different payment processor or a fundamentally different stack, build from scratch.",[20,1243,1245],{"id":1244},"comparison-at-a-glance","Comparison at a Glance",[1247,1248,1249,1266],"table",{},[1250,1251,1252],"thead",{},[1253,1254,1255,1258,1260,1263],"tr",{},[1256,1257],"th",{},[1256,1259,61],{},[1256,1261,1262],{},"BoiledPlate Pro",[1256,1264,1265],{},"Building alone",[1267,1268,1269,1284,1297,1309,1322,1334,1348],"tbody",{},[1253,1270,1271,1275,1278,1281],{},[1272,1273,1274],"td",{},"Framework",[1272,1276,1277],{},"Next.js",[1272,1279,1280],{},"Nuxt 4",[1272,1282,1283],{},"Your choice",[1253,1285,1286,1289,1292,1295],{},[1272,1287,1288],{},"Provisions services",[1272,1290,1291],{},"No",[1272,1293,1294],{},"Yes (agent)",[1272,1296,1291],{},[1253,1298,1299,1302,1304,1306],{},[1272,1300,1301],{},"Auth + RLS",[1272,1303,535],{},[1272,1305,1301],{},[1272,1307,1308],{},"DIY",[1253,1310,1311,1314,1317,1320],{},[1272,1312,1313],{},"Idempotent webhooks",[1272,1315,1316],{},"Manual",[1272,1318,1319],{},"Built-in",[1272,1321,1308],{},[1253,1323,1324,1326,1329,1332],{},[1272,1325,559],{},[1272,1327,1328],{},"Add-on",[1272,1330,1331],{},"4 languages",[1272,1333,1308],{},[1253,1335,1336,1339,1342,1345],{},[1272,1337,1338],{},"Delivery",[1272,1340,1341],{},"Code template",[1272,1343,1344],{},"GitHub repo",[1272,1346,1347],{},"—",[1253,1349,1350,1353,1356,1359],{},[1272,1351,1352],{},"Time to launch",[1272,1354,1355],{},"Days",[1272,1357,1358],{},"A session",[1272,1360,1361],{},"Weeks+",[11,1363,1364],{},"Over 12 months, the cost of ownership isn't the license fee — it's the maintenance and update friction. Semantic release notes and opt-in patches keep that low.",[20,1366,1368],{"id":1367},"who-should-pick-boiledplate-and-who-shouldnt","Who Should Pick BoiledPlate (And Who Shouldn't)",[11,1370,1371],{},"BoiledPlate is ideal for Nuxt-comfortable developers, teams using AI coding agents, and billing-heavy products where the webhook and RLS work would otherwise eat weeks. It's sized for teams of one to three, not enterprise procurement. Accept the trade-offs — Vue, Supabase, Stripe, no swaps — and it's a fast path. Reject them and ShipFast or a from-scratch build serves you better.",[20,1373,1375],{"id":1374},"conclusion-plumbing-done-shipping-starts","Conclusion: Plumbing Done, Shipping Starts",[11,1377,1378,1379,1383,1384,1388],{},"The framework is not what slows you down. ShipFast is right that you can launch fast — but a code template still leaves the ",[31,1380,1382],{"href":33,"rel":1381},[35],"plumbing as the project",". BoiledPlate automates that plumbing so you own the product, not the setup: one agent session provisions Stripe, Supabase with RLS, and Google sign-in, then hands you your code via GitHub. Skip the weeks of wiring and start shipping. Browse the ",[31,1385,1387],{"href":313,"rel":1386},[35],"blog"," for the edge cases we hit so you don't have to.",{"title":318,"searchDepth":319,"depth":319,"links":1390},[1391,1392,1393,1394,1395,1396,1397,1398,1399,1400,1401,1402,1403,1404,1405,1406,1407],{"id":1049,"depth":322,"text":1050},{"id":1059,"depth":322,"text":1060},{"id":1094,"depth":322,"text":1095},{"id":1109,"depth":322,"text":1110},{"id":1119,"depth":322,"text":1120},{"id":1147,"depth":322,"text":1148},{"id":1161,"depth":322,"text":1162},{"id":1175,"depth":322,"text":1176},{"id":1187,"depth":322,"text":1188},{"id":1199,"depth":322,"text":1200},{"id":1206,"depth":322,"text":1207},{"id":1220,"depth":322,"text":1221},{"id":1230,"depth":322,"text":1231},{"id":1237,"depth":322,"text":1238},{"id":1244,"depth":322,"text":1245},{"id":1367,"depth":322,"text":1368},{"id":1374,"depth":322,"text":1375},"2026-09-07","Compare ShipFast and BoiledPlate SaaS templates. Learn which boilerplate handles auth, Stripe, and infrastructure best for your Next.js project.",{},"\u002Fblog\u002Fshipfast-saas-boilerplate-comparison",{"title":1041,"description":1409},"blog\u002Fshipfast-saas-boilerplate-comparison",[349,1415,705,1416],"saas boilerplate","saas development","KhX3NSHLjAPepGO0fWifUvLcdlXA5piVm6wtgmZeFJk",1789001515684]