[{"data":1,"prerenderedAt":1455},["ShallowReactive",2],{"blog-shipfast-twitter-hype-reality":3,"related-shipfast-twitter-hype-reality":347},{"id":4,"title":5,"author":6,"body":7,"category":6,"date":332,"description":333,"draft":334,"extension":335,"image":6,"meta":336,"navigation":337,"path":338,"seo":339,"stem":340,"tags":341,"__hash__":346},"blog\u002Fblog\u002Fshipfast-twitter-hype-reality.md","ShipFast Twitter Hype vs Reality: What the Template Actually Solves",null,{"type":8,"value":9,"toc":300},"minimark",[10,14,19,22,27,30,34,37,41,52,56,65,69,78,82,85,89,97,101,110,114,117,121,124,128,137,141,150,154,163,167,170,174,177,181,189,193,208,212,221,225,238,244,248,251,255,269,272,276,279],[11,12,13],"p",{},"Search \"shipfast twitter\" and you land in a familiar place: Marc Lou's timeline, screenshots of revenue, and a stream of indie builders debating whether a Next.js template is worth the money. The conversation is almost always about the same thing — which starter, which framework, which stack. That's the wrong debate. Stack choice is the easy part. The thing that actually eats your launch is the wiring between services, and no amount of Twitter hype changes that.",[15,16,18],"h2",{"id":17},"the-shipfast-phenomenon","The ShipFast Phenomenon",[11,20,21],{},"ShipFast is Marc Lou's Next.js boilerplate, and its story is genuinely impressive: a solo maker turned a single template into a seven-figure business, largely on the back of a 100k+ follower audience on X. It resonates because it sells a feeling every builder recognizes — \"launch in days, not weeks\" — and because Marc shipped it in public, proving the market with receipts instead of promises.",[23,24,26],"h3",{"id":25},"what-shipfast-does-right","What ShipFast Does Right",[11,28,29],{},"Credit where it's due. ShipFast validated that developers will pay for setup they could theoretically do themselves. It bundles a proven stack, a clean landing page, auth, and a payment integration into one clone-and-go package. For a Next.js builder who wants a head start, it removes real friction.",[23,31,33],{"id":32},"what-shipfast-doesnt-solve","What ShipFast Doesn't Solve",[11,35,36],{},"Here's the honest limitation, and it's the same limitation every template shares. ShipFast hands you code. It does not provision your services, keep an AI agent consistent across sessions, or ship production-grade billing that survives webhook retries and refunds. The parts arrive in a box. Bolting them together — the part that actually consumes your weekends — is still your job.",[15,38,40],{"id":39},"the-hidden-cost-of-saas-plumbing","The Hidden Cost of SaaS Plumbing",[11,42,43,44,51],{},"Ask ten founders how to ship fast and you get ten stack arguments. Pick whatever you already know and the debate is over in an afternoon. ",[45,46,50],"a",{"href":47,"rel":48},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fhow-to-ship-saas-fast",[49],"nofollow","The framework is not what slows you down",".",[23,53,55],{"id":54},"stack-choice-takes-hours-wiring-takes-weeks","Stack Choice Takes Hours; Wiring Takes Weeks",[11,57,58,59,64],{},"The real time sink isn't Next vs Nuxt. It's webhook idempotency, row-level security policies, refund flows, and EU consent law. As we documented in ",[45,60,63],{"href":61,"rel":62},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-supabase-stripe-saas-boilerplate",[49],"what it actually takes to wire up a Nuxt, Supabase and Stripe SaaS",", auth is the fast part and RLS is the part you forget until a user sees someone else's data.",[23,66,68],{"id":67},"why-templates-stop-short","Why Templates Stop Short",[11,70,71,72,77],{},"Every SaaS starter hands you the same box of parts: auth, a database client, a Stripe integration, a pile of Tailwind. Then it ",[45,73,76],{"href":74,"rel":75},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-saas-boilerplate-for-ai-agents",[49],"leaves you alone in a room with the box and a README",". None of the wiring is clever. It's hard in the sense of being endless and slightly different every time.",[15,79,81],{"id":80},"boiledplate-automation-beyond-the-template","BoiledPlate: Automation Beyond the Template",[11,83,84],{},"BoiledPlate is a different layer of the stack. It's an AI-native Nuxt + Supabase starter whose setup runs itself. Your coding agent doesn't just write code — it interviews you, then provisions Stripe products and webhooks, a Supabase database with RLS, and Google sign-in in a single session.",[23,86,88],{"id":87},"agent-driven-setup-the-interview-model","Agent-Driven Setup: The Interview Model",[11,90,91,92,96],{},"The agent's first session asks the questions a template can't: name, languages, theme, billing model. Then it reshapes the entire codebase to your answers using ",[93,94,95],"strong",{},"deterministic patches"," — repeatable, trackable changes rather than manual copy-paste. You describe your dashboard theme in plain language and the agent maps it onto real code.",[23,98,100],{"id":99},"agentsmd-the-consistency-contract","AGENTS.md: The Consistency Contract",[11,102,103,104,109],{},"Coding agents drift when conventions aren't written down. BoiledPlate ships an AGENTS.md contract: one documented way to do data access, secrets, and API calls, so ",[45,105,108],{"href":106,"rel":107},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fconventions-for-ai-coding-agents",[49],"your agent's output stays predictable across sessions",". Write your conventions for the agent, not just the next hire.",[15,111,113],{"id":112},"billing-that-actually-works","Billing That Actually Works",[11,115,116],{},"This is where \"ship in days\" quietly breaks. Billing is complex because money is complex, and the complexity doesn't disappear because your template skipped it.",[23,118,120],{"id":119},"idempotent-webhooks-the-non-negotiable-foundation","Idempotent Webhooks: The Non-Negotiable Foundation",[11,122,123],{},"Stripe retries webhooks. If your handler isn't idempotent, a retry becomes a double-charge or a duplicated entitlement. Most naive implementations process the same event twice without noticing. BoiledPlate's billing is built on signature-verified, idempotent webhooks — the boring foundation that stops silent failures.",[23,125,127],{"id":126},"the-source-of-truth-isnt-your-ui","The Source of Truth Isn't Your UI",[11,129,130,131,136],{},"A checkout success page means the browser reached a URL. It does not mean payment settled. ",[45,132,135],{"href":133,"rel":134},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-webhooks-source-of-truth",[49],"Your success page should not touch your billing state",". Stripe webhooks are the source of truth; the UI is a courtesy. Skip this and you'll grant access to abandoned payments and deny it to successful ones.",[23,138,140],{"id":139},"the-consent-problem-german-withdrawal-waivers-and-gdpr","The Consent Problem: German Withdrawal Waivers and GDPR",[11,142,143,144,149],{},"EU law isn't optional, and it's exactly the kind of edge case templates punt on. Selling digital goods to German customers requires encoding a withdrawal waiver into the pay button itself. We wrote up ",[45,145,148],{"href":146,"rel":147},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-checkout-consent-collection-german-withdrawal-waiver",[49],"how to do this with Stripe Checkout's consent_collection"," — the sort of detail that fails audits when ignored.",[15,151,153],{"id":152},"multi-plan-subscriptions-and-real-complexity","Multi-Plan Subscriptions and Real Complexity",[11,155,156,157,162],{},"Simple templates break under feature-gated billing. Multi-plan Stripe subscriptions demand that you sync product data with your database without race conditions, handle mid-cycle downgrades, and verify that Stripe isn't lying via signature verification. ",[45,158,161],{"href":159,"rel":160},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-subscriptions-nuxt-supabase",[49],"The five decisions behind Stripe subscriptions"," — plans, entitlements, state, webhooks, and consent — are the ones that decide whether your billing survives contact with real customers.",[15,164,166],{"id":165},"auth-done-right-rls-and-row-level-security","Auth Done Right: RLS and Row-Level Security",[11,168,169],{},"Supabase policies aren't decorative. Client-side auth checks protect nothing; a determined user bypasses your UI and hits your database directly. Row-level security enforces isolation at query time, so a forgotten check in one component doesn't leak another tenant's data. Application-layer auth survives demos. RLS survives production.",[15,171,173],{"id":172},"the-anti-plumbing-stack-nuxt-supabase-stripe","The Anti-Plumbing Stack: Nuxt + Supabase + Stripe",[11,175,176],{},"These three tools demand each other, and each is genuinely good at its job. Nuxt gives you server-side rendering that doesn't fight you: auto-imports, Nitro, built-in composables. Supabase gives you Postgres without the DevOps — RLS, real-time, and auth in one place. Stripe's complexity isn't bloat; it's the price of handling refunds, disputes, and tax correctly. And Google sign-in — OAuth flows, token validation, user mapping — is the integration nobody wants to wire by hand, which is exactly why automating it saves hours.",[15,178,180],{"id":179},"transactional-email-resend-and-the-idempotency-problem","Transactional Email: Resend and the Idempotency Problem",[11,182,183,184,188],{},"Email is simple to send and ",[45,185,187],{"href":61,"rel":186},[49],"annoying to send exactly once",". The order of operations matters: Stripe fires, your webhook processes, then email goes out. Get it backwards and a retried webhook sends three confirmation emails. Do it inside the idempotent handler and each customer gets one — in the right language, since BoiledPlate ships i18n across four languages from day one.",[15,190,192],{"id":191},"seo-and-real-debugging-stories","SEO and Real Debugging Stories",[11,194,195,196,201,202,207],{},"BoiledPlate ships JSON-LD, canonical URLs, and og:url meta tags so your blog actually gets indexed. We learned these the hard way. One JSON-LD source-order bug ",[45,197,200],{"href":198,"rel":199},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-page-that-returned-200-on-the-server-and-500-in-the-browser-a-json-ld-tempor",[49],"returned 200 from curl and 500 in the browser",". Another time our ",[45,203,206],{"href":204,"rel":205},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Four-blog-canonically-pointed-at-localhost",[49],"blog told Google its canonical URL was localhost:3000",". Blogs run on prerendered Markdown — static, fast, no headless CMS required.",[15,209,211],{"id":210},"deployment-the-github-invite-as-your-product","Deployment: The GitHub Invite as Your Product",[11,213,214,215,220],{},"Product delivery is a technical problem. Sending code via email or Slack is a support nightmare. BoiledPlate treats ",[45,216,219],{"href":217,"rel":218},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-github-invite-is-the-product-building-a-stripe-webhook-where-delivery-throws",[49],"the GitHub invite itself as the product",", delivered instantly via a Stripe webhook where some failures must throw and some must never — the kind of nuance that separates working delivery from silent data loss.",[15,222,224],{"id":223},"lite-vs-pro-free-or-lifetime-updates","Lite vs. Pro: Free or Lifetime Updates",[11,226,227,228,231,232,237],{},"There are two paths. ",[93,229,230],{},"BoiledPlate Lite"," is ",[45,233,236],{"href":234,"rel":235},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Ffree-nuxt-supabase-saas-boilerplate",[49],"free and MIT-licensed",": clone it, wire the services manually, own everything. It's the right call when you want to understand every line and have the time.",[11,239,240,243],{},[93,241,242],{},"BoiledPlate Pro"," is €159 one-time with lifetime updates and instant GitHub delivery. The value isn't just the initial setup — it's staying current. Stripe API versions change, Supabase schemas migrate, security patches land. Semantic, agent-readable release notes let you opt into updates without merge hell, even on customized code. Version drift is what quietly kills a SaaS long after launch.",[15,245,247],{"id":246},"real-world-failure-modes","Real-World Failure Modes",[11,249,250],{},"Shipping \"days not weeks\" doesn't prevent the disasters that show up in production: peer dependency conflicts and lock-file entropy, webhook handlers that crash mid-payment and lose data silently, the partial refund flow nobody shipped with, and schema migrations that break production at 2 a.m. These are the reasons ShipFast reviews on X and Reddit mention bugs and security concerns — not because Marc did anything uniquely wrong, but because plumbing is genuinely hard and templates leave it to you.",[15,252,254],{"id":253},"choosing-your-path","Choosing Your Path",[11,256,257,260,261,264,265,268],{},[93,258,259],{},"Clone and wire manually"," when you have strong stack opinions and time to spend. ",[93,262,263],{},"Use a standard template"," like ShipFast when you like the stack and are happy wiring services yourself. ",[93,266,267],{},"Choose automation"," when billing is critical to your business, you work with coding agents, and you value staying current without rewriting.",[11,270,271],{},"The distinction is honest: this isn't ShipFast versus BoiledPlate as competitors. Marc Lou proved the market. BoiledPlate automates the layer he punts — service provisioning, agent consistency, and billing that survives reality.",[15,273,275],{"id":274},"the-bottom-line","The Bottom Line",[11,277,278],{},"The Twitter conversation about ShipFast is really a conversation about wanting to ship faster. That instinct is correct. But the bottleneck was never the framework. It's the plumbing — webhook idempotency, RLS, refunds, consent, delivery — that no template automates and every successful SaaS eventually rebuilds. If your product succeeds, the first refactor is always the plumbing. Starting on a foundation that already solves it is the actual shortcut.",[11,280,281,282,287,288,293,294,299],{},"You can ",[45,283,286],{"href":284,"rel":285},"https:\u002F\u002Fboiledplate.ai",[49],"start with BoiledPlate"," or read the ",[45,289,292],{"href":290,"rel":291},"https:\u002F\u002Fboiledplate.ai\u002Fblog",[49],"full blog"," on how each piece of the stack really fits together. For the deeper industry context on why webhook reliability matters, Stripe's own ",[45,295,298],{"href":296,"rel":297},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks",[49],"webhook best practices"," documentation is worth the read — it explains, in Stripe's words, exactly why idempotency and signature verification aren't optional.",{"title":301,"searchDepth":302,"depth":302,"links":303},"",3,[304,309,313,317,322,323,324,325,326,327,328,329,330,331],{"id":17,"depth":305,"text":18,"children":306},2,[307,308],{"id":25,"depth":302,"text":26},{"id":32,"depth":302,"text":33},{"id":39,"depth":305,"text":40,"children":310},[311,312],{"id":54,"depth":302,"text":55},{"id":67,"depth":302,"text":68},{"id":80,"depth":305,"text":81,"children":314},[315,316],{"id":87,"depth":302,"text":88},{"id":99,"depth":302,"text":100},{"id":112,"depth":305,"text":113,"children":318},[319,320,321],{"id":119,"depth":302,"text":120},{"id":126,"depth":302,"text":127},{"id":139,"depth":302,"text":140},{"id":152,"depth":305,"text":153},{"id":165,"depth":305,"text":166},{"id":172,"depth":305,"text":173},{"id":179,"depth":305,"text":180},{"id":191,"depth":305,"text":192},{"id":210,"depth":305,"text":211},{"id":223,"depth":305,"text":224},{"id":246,"depth":305,"text":247},{"id":253,"depth":305,"text":254},{"id":274,"depth":305,"text":275},"2026-09-12","ShipFast Twitter buzz promises fast launches, but Marc Lou's Next.js template has real limitations. Here's what it actually does and doesn't solve.",false,"md",{},true,"\u002Fblog\u002Fshipfast-twitter-hype-reality",{"title":5,"description":333},"blog\u002Fshipfast-twitter-hype-reality",[342,343,344,345],"shipfast","next.js","indie hackers","boilerplate","Ke8c5Jf200Ucs7-Hf2CoelPnFMCo4kuAztgCccoNUEI",[348,793,1111],{"id":349,"title":350,"author":6,"body":351,"category":6,"date":782,"description":783,"draft":334,"extension":335,"image":6,"meta":784,"navigation":337,"path":785,"seo":786,"stem":787,"tags":788,"__hash__":792},"blog\u002Fblog\u002Fshipfast-tutorial.md","ShipFast Tutorial: Build Production-Ready Startups Faster",{"type":8,"value":352,"toc":762},[353,356,360,368,371,375,378,391,395,398,426,429,433,442,450,454,462,465,473,477,480,483,487,494,497,501,539,543,556,560,563,567,573,579,585,600,606,610,629,632,636,668,672,684,690,696,700,703,707,710,714,717,721,750],[11,354,355],{},"If you searched for a \"shipfast tutorial,\" you already know the pitch: launch your startup in days, not weeks, from an easy-to-follow boilerplate. The pitch is right about one thing — the framework is not what slows you down. But most tutorials stop exactly where the real work begins: wiring Stripe webhooks, writing row-level security, and making billing state survive a retry. BoiledPlate is built around that gap. Here's what it is, how it works, and where it beats the \"ship in five minutes\" promise that quietly leaves you debugging in production.",[15,357,359],{"id":358},"what-is-boiledplate","What is BoiledPlate?",[11,361,362,363,367],{},"BoiledPlate is an AI-native Nuxt + Supabase starter kit that sets itself up. Instead of cloning a template and manually connecting services, your coding agent interviews you, then provisions the stack: ",[45,364,366],{"href":284,"rel":365},[49],"Stripe products and webhooks, a Supabase database with RLS, and Google sign-in"," — in a single session.",[11,369,370],{},"It's not just boilerplate code. Generic Next.js templates hand you files and a tutorial; you're still the integration engineer. BoiledPlate ships an agent contract and deterministic patches so the setup is a conversation, not a checklist. You answer questions about pricing tiers, languages, and theme; the agent reshapes the codebase to match.",[15,372,374],{"id":373},"the-real-problem-boiledplate-solves","The Real Problem BoiledPlate Solves",[11,376,377],{},"Picking a stack is trivial. Nuxt or Next, Postgres or hosted — decide over coffee and move on. What eats four to six weeks is the plumbing between the pieces: idempotent webhooks, RLS policies, refund handling, transactional email that sends exactly once, and EU consent flows.",[11,379,380,381,385,386,390],{},"\"Easy to follow\" tutorials skip this because it's the hard, unglamorous part. They get you to a checkout redirect and a success page, then leave you to discover that ",[45,382,384],{"href":133,"rel":383},[49],"your success page should never be the source of billing truth",". We wrote about this at length in ",[45,387,389],{"href":47,"rel":388},[49],"why the stack is easy and the plumbing is the project"," — it's the thesis the whole product is built on.",[15,392,394],{"id":393},"how-boiledplate-actually-works","How BoiledPlate Actually Works",[11,396,397],{},"The flow is concrete, not marketing:",[399,400,401,408,414,420],"ol",{},[402,403,404,407],"li",{},[93,405,406],{},"The agent interviews you."," Name, languages, theme, billing model, user roles, consent requirements.",[402,409,410,413],{},[93,411,412],{},"The agent reads the AGENTS.md contract and applies deterministic patches."," These are repeatable, idempotent code changes — not vibes.",[402,415,416,419],{},[93,417,418],{},"Services auto-provision."," Supabase (cloud or local Docker) with RLS policies, Stripe products and webhooks, Google OAuth.",[402,421,422,425],{},[93,423,424],{},"A webhook proves billing state landed."," The source of truth is the webhook hitting your database, not client-side confetti.",[11,427,428],{},"That fourth step is the difference between a demo and a product. A five-minute tutorial that ends at the redirect hasn't shipped billing; it's shown you the happy path, which is maybe a fifth of the work.",[15,430,432],{"id":431},"the-anti-plumbing-stack-why-nuxt-supabase-stripe","The Anti-Plumbing Stack: Why Nuxt + Supabase + Stripe",[11,434,435,436,441],{},"These three aren't arbitrary. Nuxt's server middleware, composables, and auto-imports give an agent predictable places to write code, which is what makes consistent patches possible. Supabase enforces ",[45,437,440],{"href":438,"rel":439},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fpostgres\u002Frow-level-security",[49],"RLS at query time",", so access logic can't quietly leak through an application-layer mistake. Stripe's webhooks, when handled idempotently, mean refunds and retries don't double-charge.",[11,443,444,445,449],{},"The trap is mixing them carelessly — trusting a checkout redirect for access, or checking auth in middleware and calling it security. ",[45,446,448],{"href":61,"rel":447},[49],"Wiring these four services correctly"," is precisely the multi-week task BoiledPlate collapses.",[15,451,453],{"id":452},"billing-architecture-that-survives-reality","Billing Architecture That Survives Reality",[11,455,456,457,461],{},"Stripe and Supabase have a clean division of labor: Stripe owns payment and subscription lifecycle; your database owns access. The ",[45,458,460],{"href":159,"rel":459},[49],"webhook is where subscriptions actually live",". BoiledPlate ships multi-plan subscriptions with signature-verified, idempotent webhook handlers.",[11,463,464],{},"Consider the retry case. Stripe re-delivers events on any non-2xx or timeout. If your handler credits the customer without an idempotency key, a retry double-credits. BoiledPlate's handlers key on the event ID so repeated delivery is a no-op.",[11,466,467,468,472],{},"Refunds are harder than the docs admit, especially in the EU. German law requires an explicit withdrawal waiver before a digital product is delivered — we encoded that directly into the pay button using ",[45,469,471],{"href":146,"rel":470},[49],"Stripe Checkout's consent_collection",". No five-minute tutorial touches this.",[15,474,476],{"id":475},"auth-done-right-rls-without-footguns","Auth Done Right: RLS Without Footguns",[11,478,479],{},"RLS enforces policies at query time, in the database, not in your handler code. That's the point: you can't forget to check, because the check is the query. But it demands discipline. The classic footgun is a policy that forgets a tenant ID and exposes other customers' rows. BoiledPlate generates policies that match your declared user roles and pricing tiers, so access maps to billing state rather than to hope.",[11,481,482],{},"The other footgun is skipping signature verification on webhooks. An unverified endpoint accepts forged events. BoiledPlate verifies signatures before anything touches the database.",[15,484,486],{"id":485},"agent-consistency-the-agentsmd-contract","Agent Consistency: The AGENTS.md Contract",[11,488,489,490,51],{},"Coding agents drift when there's no single source of truth for conventions. Ask an agent to add a billing event today and a role tomorrow, and you get two incompatible styles. AGENTS.md fixes this: one documented way to access data, manage secrets, and structure API handlers. We explain the reasoning in ",[45,491,493],{"href":106,"rel":492},[49],"write your conventions for the agent, not the next hire",[11,495,496],{},"Because patches are deterministic and idempotent, they stay safe even after you customize. Adding a new billing event type doesn't break the agent's model of your codebase — it extends it.",[15,498,500],{"id":499},"features-that-ship-out-of-the-box","Features That Ship Out of the Box",[502,503,504,510,516,522,528],"ul",{},[402,505,506,509],{},[93,507,508],{},"Transactional email (Resend):"," onboarding, receipts, and cancellations wired, not left as an exercise.",[402,511,512,515],{},[93,513,514],{},"i18n from day one:"," four languages preloaded; the agent respects translation keys in every patch.",[402,517,518,521],{},[93,519,520],{},"A blog ready to write:"," prerendered Markdown with SEO — JSON-LD and canonical URLs — built in.",[402,523,524,527],{},[93,525,526],{},"Dashboard theming:"," pick a preset or describe your own; the agent maps it onto the component library. These are real previews every buyer gets.",[402,529,530,533,534,538],{},[93,531,532],{},"TypeScript strict mode:"," no ",[535,536,537],"code",{},"any"," escape hatches, which makes agent-readable types and safer patches.",[15,540,542],{"id":541},"the-seo-foundation-tutorials-usually-miss","The SEO Foundation Tutorials Usually Miss",[11,544,545,546,550,551,555],{},"\"SEO out of the box\" is lazy marketing unless the canonical URL doesn't drift per language or route. We learned this the embarrassing way when ",[45,547,549],{"href":204,"rel":548},[49],"our blog told Google its canonical was localhost:3000",". JSON-LD matters too — and it can bite you. A ",[45,552,554],{"href":198,"rel":553},[49],"JSON-LD script in the wrong source order returned 200 from curl and 500 in Chrome",". Those SSR patterns are documented so you don't rediscover them in production.",[15,557,559],{"id":558},"shipping-without-merge-hell","Shipping Without Merge Hell",[11,561,562],{},"BoiledPlate ships semantic, agent-readable release notes that describe what changed and why. Updates are opt-in: you pull patches, the agent shows diffs before applying. That's how you upgrade six months later without rewinding your own customizations — the update respects the code you wrote on top.",[15,564,566],{"id":565},"setup-walkthrough-zero-to-stripe-webhook-in-one-session","Setup Walkthrough: Zero to Stripe Webhook in One Session",[11,568,569,572],{},[93,570,571],{},"Prerequisites:"," a Stripe account, a Supabase org, and a Google OAuth app.",[11,574,575,578],{},[93,576,577],{},"Run the interview."," The agent asks about plans, roles, languages, theme, and consent. Answer plainly; there's no framework debate to have.",[11,580,581,584],{},[93,582,583],{},"What it provisions:"," database schema, RLS policies, webhook endpoints, and environment variables. The agent writes what it can and tells you which secrets to paste.",[11,586,587,590,591,599],{},[93,588,589],{},"Deploy to Vercel or Netlify."," After the agent finishes, deployment is minutes because the wiring is already done. (One note if you add Vercel Web Analytics: the ",[45,592,595,596],{"href":593,"rel":594},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fvercel-web-analytics-nuxt-4-analytics-package-breaks-typecheck",[49],"package can break ",[535,597,598],{},"nuxt typecheck"," — we documented the fix.)",[11,601,602,605],{},[93,603,604],{},"Verify the first webhook."," Trigger a test event and confirm the row landed in Supabase. That's proof billing state actually arrived — the thing tutorials never make you check.",[15,607,609],{"id":608},"boiledplate-lite-vs-pro","BoiledPlate Lite vs. Pro",[502,611,612,623],{},[402,613,614,617,618,622],{},[93,615,616],{},"Lite (MIT, free):"," clone the repo and ",[45,619,621],{"href":234,"rel":620},[49],"wire services yourself",". Good for learning the patterns or a custom stack.",[402,624,625,628],{},[93,626,627],{},"Pro (€159 one-time, lifetime updates):"," agent-driven setup, instant delivery via GitHub, semantic opt-in updates.",[11,630,631],{},"Honest trade-off: Pro is faster; Lite is more flexible if you don't use Nuxt or want to understand every wire yourself.",[15,633,635],{"id":634},"common-pitfalls-boiledplate-prevents","Common Pitfalls BoiledPlate Prevents",[502,637,638,644,650,656,662],{},[402,639,640,643],{},[93,641,642],{},"Retry loops that double-charge"," — idempotency keys make repeated events safe.",[402,645,646,649],{},[93,647,648],{},"RLS policies that expose other tenants"," — generated policies carry the tenant ID.",[402,651,652,655],{},[93,653,654],{},"Canonical URL drift"," — prerendering plus verification, born from real pain.",[402,657,658,661],{},[93,659,660],{},"JSON-LD hydration crashes"," — documented Nuxt SSR source-order patterns.",[402,663,664,667],{},[93,665,666],{},"Peer dependency hell"," — Stripe, Supabase, and Resend versions pinned and tested together.",[15,669,671],{"id":670},"real-debugging-youll-actually-hit","Real Debugging You'll Actually Hit",[11,673,674,678,679,683],{},[675,676,677],"em",{},"\"Webhook arrived but didn't update my database.\""," Run the signature-verification checklist; the ",[45,680,682],{"href":217,"rel":681},[49],"GitHub-invite webhook post"," explains which failures should throw and which should never.",[11,685,686,689],{},[675,687,688],{},"\"RLS is blocking my own query.\""," Test policies against a non-production role; check that your policy references the right claim.",[11,691,692,695],{},[675,693,694],{},"\"Refund went through but the UI still shows active.\""," That's eventual consistency — the webhook is the source of truth, and the UI follows it, not the other way around.",[15,697,699],{"id":698},"why-agent-driven-setup-changes-the-game","Why Agent-Driven Setup Changes the Game",[11,701,702],{},"Manual tutorials scale linearly: you redo the plumbing for every SaaS. Agent-driven setup scales better because the agent learns your conventions and applies them consistently. Add a user role and the agent updates RLS, UI, and API in one coherent patch — respecting the naming scheme your team already uses.",[15,704,706],{"id":705},"when-boiledplate-isnt-the-right-fit","When BoiledPlate Isn't the Right Fit",[11,708,709],{},"If you're married to Next.js and won't learn Nuxt, Pro needs buy-in (Lite still teaches the patterns). If your billing is too complex for standard SaaS tiers, or you need a GraphQL API, expect custom work — BoiledPlate ships server middleware and assumes conventional subscription models.",[15,711,713],{"id":712},"the-philosophy","The Philosophy",[11,715,716],{},"The framework is not what slows you down; the integration is. BoiledPlate respects your time by automating the boring wiring without hiding the complexity, and it's built for AI agents because they'll be writing your SaaS tomorrow — you might as well design for consistency now.",[15,718,720],{"id":719},"getting-started","Getting Started",[502,722,723,729,740],{},[402,724,725,728],{},[93,726,727],{},"30 minutes:"," skim the conventions and decide if agent-driven setup appeals to you.",[402,730,731,734,735,739],{},[93,732,733],{},"2 hours:"," ",[45,736,738],{"href":234,"rel":737},[49],"clone Lite",", wire one service by hand, and feel where the weeks go.",[402,741,742,734,745,749],{},[93,743,744],{},"Ready to ship:",[45,746,748],{"href":284,"rel":747},[49],"get Pro",", run the interview, deploy, and write your first real feature instead of your fortieth webhook handler.",[11,751,752,753,757,758,761],{},"For deeper reading, the ",[45,754,756],{"href":290,"rel":755},[49],"BoiledPlate blog"," documents each edge case with the real bug and the real fix — and Stripe's own ",[45,759,298],{"href":296,"rel":760},[49]," are essential even when a starter handles the hard parts for you.",{"title":301,"searchDepth":302,"depth":302,"links":763},[764,765,766,767,768,769,770,771,772,773,774,775,776,777,778,779,780,781],{"id":358,"depth":305,"text":359},{"id":373,"depth":305,"text":374},{"id":393,"depth":305,"text":394},{"id":431,"depth":305,"text":432},{"id":452,"depth":305,"text":453},{"id":475,"depth":305,"text":476},{"id":485,"depth":305,"text":486},{"id":499,"depth":305,"text":500},{"id":541,"depth":305,"text":542},{"id":558,"depth":305,"text":559},{"id":565,"depth":305,"text":566},{"id":608,"depth":305,"text":609},{"id":634,"depth":305,"text":635},{"id":670,"depth":305,"text":671},{"id":698,"depth":305,"text":699},{"id":705,"depth":305,"text":706},{"id":712,"depth":305,"text":713},{"id":719,"depth":305,"text":720},"2026-09-11","Learn how BoiledPlate goes beyond ShipFast templates with AI-native setup, Stripe integration, and production-ready infrastructure for startups.",{},"\u002Fblog\u002Fshipfast-tutorial",{"title":350,"description":783},"blog\u002Fshipfast-tutorial",[342,789,790,791],"tutorial","startup-boilerplate","stripe-integration","tDZYFFDL49lAdCZJNAP9-tOsrJ4PCoW-berk9aTYAg0",{"id":794,"title":795,"author":6,"body":796,"category":6,"date":1101,"description":1102,"draft":334,"extension":335,"image":6,"meta":1103,"navigation":337,"path":1104,"seo":1105,"stem":1106,"tags":1107,"__hash__":1110},"blog\u002Fblog\u002Fshipfast-template-boilerplate-quality.md","ShipFast Template: Why Boilerplate Quality Beats Framework Choice",{"type":8,"value":797,"toc":1082},[798,805,809,812,819,823,830,833,837,843,854,857,861,868,876,884,888,891,903,907,910,913,917,920,928,932,939,942,946,958,965,969,972,985,989,996,1000,1003,1006,1010,1013,1017,1029,1033,1045,1048,1052,1060,1064,1070],[11,799,800,801,804],{},"If you searched for a ",[93,802,803],{},"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.",[15,806,808],{"id":807},"why-just-pick-a-framework-misses-the-point","Why \"Just Pick a Framework\" Misses the Point",[11,810,811],{},"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,813,814,815,51],{},"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, ",[45,816,818],{"href":47,"rel":817},[49],"the stack is easy — the plumbing is the project",[15,820,822],{"id":821},"the-boilerplate-gap-what-starter-kits-usually-forget","The Boilerplate Gap: What Starter Kits Usually Forget",[11,824,825,826,51],{},"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 ",[45,827,829],{"href":74,"rel":828},[49],"what ate our weekends",[11,831,832],{},"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.",[15,834,836],{"id":835},"boiledplate-vs-shipfast-stack-philosophy-and-trade-offs","BoiledPlate vs. ShipFast: Stack, Philosophy, and Trade-offs",[11,838,839,842],{},[93,840,841],{},"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,844,845,848,849,853],{},[93,846,847],{},"BoiledPlate"," is a Nuxt + Supabase + Stripe starter with a different center of gravity: it's ",[45,850,852],{"href":284,"rel":851},[49],"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,855,856],{},"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.",[15,858,860],{"id":859},"the-webhook-problem-nobody-talks-about","The Webhook Problem Nobody Talks About",[11,862,863,864,867],{},"Here is the thing every marketing page glosses over: ",[93,865,866],{},"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,869,870,871,875],{},"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 ",[45,872,874],{"href":133,"rel":873},[49],"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,877,878,879,883],{},"Refunds are where this gets sharp. We wrote a whole post on ",[45,880,882],{"href":217,"rel":881},[49],"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.",[15,885,887],{"id":886},"agent-driven-setup-the-automation-layer-boilerplates-miss","Agent-Driven Setup: The Automation Layer Boilerplates Miss",[11,889,890],{},"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,892,893,894,897,898,902],{},"The glue that keeps this consistent is a shipped ",[93,895,896],{},"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 ",[45,899,901],{"href":106,"rel":900},[49],"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.\"",[15,904,906],{"id":905},"database-security-that-doesnt-require-a-security-audit","Database Security That Doesn't Require a Security Audit",[11,908,909],{},"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,911,912],{},"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.",[15,914,916],{"id":915},"billing-edge-cases-the-unglamorous-reality","Billing Edge Cases: The Unglamorous Reality",[11,918,919],{},"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,921,922,923,927],{},"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 ",[45,924,926],{"href":146,"rel":925},[49],"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.",[15,929,931],{"id":930},"transactional-email-that-actually-arrives","Transactional Email That Actually Arrives",[11,933,934,935,938],{},"Resend paired with Supabase is a clean setup: simple to send, annoying to send ",[675,936,937],{},"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,940,941],{},"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.",[15,943,945],{"id":944},"seo-and-canonicals-why-these-matter-for-shipped-products","SEO and Canonicals: Why These Matter for Shipped Products",[11,947,948,949,953,954,51],{},"SEO-out-of-the-box saves weeks of debugging you didn't budget for. Two real bugs from our own build: a ",[45,950,952],{"href":198,"rel":951},[49],"JSON-LD block that returned 200 from curl and 500 in the browser"," because of source order, and a blog that ",[45,955,957],{"href":204,"rel":956},[49],"told Google its canonical URL was localhost:3000",[11,959,960,961,964],{},"Canonicals get harder with multi-language routes, ",[535,962,963],{},"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.",[15,966,968],{"id":967},"typescript-end-to-end-what-strict-mode-actually-gives-you","TypeScript End-to-End: What \"Strict Mode\" Actually Gives You",[11,970,971],{},"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,973,974,975,984],{},"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 ",[45,976,978,981,982],{"href":593,"rel":977},[49],[535,979,980],{},"@vercel\u002Fanalytics"," broke ",[535,983,598],{},". A boilerplate earns its price partly by having already absorbed those fights.",[15,986,988],{"id":987},"deployment-in-minutes-github-as-product-delivery","Deployment in Minutes: GitHub as Product Delivery",[11,990,991,992,995],{},"BoiledPlate ships via instant GitHub delivery — the invite ",[675,993,994],{},"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.",[15,997,999],{"id":998},"theming-and-customization-without-the-maintenance-tax","Theming and Customization Without the Maintenance Tax",[11,1001,1002],{},"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,1004,1005],{},"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.",[15,1007,1009],{"id":1008},"four-languages-from-day-one-i18n-that-doesnt-feel-bolted-on","Four Languages from Day One: i18n That Doesn't Feel Bolted On",[11,1011,1012],{},"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.",[15,1014,1016],{"id":1015},"the-anti-plumbing-stack-why-these-tools-work-together","The Anti-Plumbing Stack: Why These Tools Work Together",[11,1018,1019,1020,1023,1024,1028],{},"Nuxt's ",[535,1021,1022],{},"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 ",[45,1025,1027],{"href":61,"rel":1026},[49],"what each piece really demands"," if you want the wiring in detail.",[15,1030,1032],{"id":1031},"the-hidden-cost-of-faster-setup","The Hidden Cost of \"Faster Setup\"",[11,1034,1035,1036,1040,1041,1044],{},"Free tier or paid? ",[45,1037,1039],{"href":234,"rel":1038},[49],"BoiledPlate Lite is MIT-licensed"," — clone it and wire manually if you enjoy the plumbing or want to inspect every seam. ",[93,1042,1043],{},"Pro"," is €159 one-time with lifetime updates and instant GitHub delivery.",[11,1046,1047],{},"\"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.",[15,1049,1051],{"id":1050},"metrics-that-matter-after-launch","Metrics That Matter After Launch",[11,1053,1054,1055,1059],{},"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 ",[45,1056,298],{"href":1057,"rel":1058},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks\u002Fbest-practices",[49]," are worth bookmarking here.",[15,1061,1063],{"id":1062},"the-decision-framework-is-a-boilerplate-worth-your-time","The Decision Framework: Is a Boilerplate Worth Your Time?",[11,1065,1066,1067,1069],{},"DIY plumbing is faster than a good boilerplate roughly never — and when it ",[675,1068,994],{},", 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,1071,1072,1073,1076,1077,1081],{},"Refactoring a bad foundation costs more than the upfront investment in a good one. Before you commit to any ",[93,1074,1075],{},"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 ",[45,1078,1080],{"href":290,"rel":1079},[49],"the blog"," — the questions worth asking are the ones we kept a running log of.",{"title":301,"searchDepth":302,"depth":302,"links":1083},[1084,1085,1086,1087,1088,1089,1090,1091,1092,1093,1094,1095,1096,1097,1098,1099,1100],{"id":807,"depth":305,"text":808},{"id":821,"depth":305,"text":822},{"id":835,"depth":305,"text":836},{"id":859,"depth":305,"text":860},{"id":886,"depth":305,"text":887},{"id":905,"depth":305,"text":906},{"id":915,"depth":305,"text":916},{"id":930,"depth":305,"text":931},{"id":944,"depth":305,"text":945},{"id":967,"depth":305,"text":968},{"id":987,"depth":305,"text":988},{"id":998,"depth":305,"text":999},{"id":1008,"depth":305,"text":1009},{"id":1015,"depth":305,"text":1016},{"id":1031,"depth":305,"text":1032},{"id":1050,"depth":305,"text":1051},{"id":1062,"depth":305,"text":1063},"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.",{},"\u002Fblog\u002Fshipfast-template-boilerplate-quality",{"title":795,"description":1102},"blog\u002Fshipfast-template-boilerplate-quality",[342,345,1108,1109],"saas-development","starter-templates","BzjDbCW8Cnp_xkO7YxbpPG3il5Bl8s0lq5G6DArHov4",{"id":1112,"title":1113,"author":6,"body":1114,"category":6,"date":1445,"description":1446,"draft":334,"extension":335,"image":6,"meta":1447,"navigation":337,"path":1448,"seo":1449,"stem":1450,"tags":1451,"__hash__":1454},"blog\u002Fblog\u002Fshipfast-tech-vs-boiledplate-saas-boilerplate.md","ShipFast Tech vs BoiledPlate: SaaS Boilerplate Comparison",{"type":8,"value":1115,"toc":1419},[1116,1119,1123,1126,1129,1133,1141,1145,1161,1169,1173,1176,1179,1183,1187,1195,1199,1206,1209,1213,1217,1223,1227,1230,1234,1246,1250,1254,1257,1261,1271,1275,1278,1322,1328,1334,1338,1351,1354,1358,1361,1364,1367,1371,1387,1391,1397,1403,1409,1413,1416],[11,1117,1118],{},"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.",[15,1120,1122],{"id":1121},"what-this-comparison-actually-covers","What This Comparison Actually Covers",[11,1124,1125],{},"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,1127,1128],{},"\"Days not weeks\" means different things depending on which of those workflows you buy into. Let's look at where the weeks actually hide.",[15,1130,1132],{"id":1131},"the-plumbing-layer-where-weeks-actually-hide","The Plumbing Layer: Where Weeks Actually Hide",[11,1134,1135,1136,1140],{},"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 ",[45,1137,1139],{"href":47,"rel":1138},[49],"how to ship SaaS fast: the stack is easy, the plumbing is the project",". The framework is not what slows you down.",[23,1142,1144],{"id":1143},"webhook-architecture-the-invisible-complexity","Webhook Architecture: The Invisible Complexity",[11,1146,1147,1148,1151,1152,1155,1156,1160],{},"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 ",[535,1149,1150],{},"subscription.updated"," before ",[535,1153,1154],{},"subscription.created",". Stripe's own ",[45,1157,1159],{"href":296,"rel":1158},[49],"webhook documentation"," warns you to respond within seconds and process asynchronously.",[11,1162,1163,1164,1168],{},"Most boilerplates ship a happy-path handler and call it done. BoiledPlate treats ",[45,1165,1167],{"href":133,"rel":1166},[49],"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.",[23,1170,1172],{"id":1171},"deterministic-patches-vs-manual-wiring","Deterministic Patches vs Manual Wiring",[11,1174,1175],{},"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,1177,1178],{},"If a coding agent is part of your daily workflow, that difference compounds over the life of the project.",[15,1180,1182],{"id":1181},"billing-edge-cases-that-swallow-weeks","Billing Edge Cases That Swallow Weeks",[23,1184,1186],{"id":1185},"subscription-state-management","Subscription State Management",[11,1188,1189,1190,1194],{},"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 ",[45,1191,1193],{"href":159,"rel":1192},[49],"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.",[23,1196,1198],{"id":1197},"eu-compliance-and-refund-flows","EU Compliance and Refund Flows",[11,1200,1201,1202,1205],{},"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 ",[45,1203,471],{"href":146,"rel":1204},[49],". 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,1207,1208],{},"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.",[15,1210,1212],{"id":1211},"architecture-comparison-nextjs-vs-nuxt-supabase","Architecture Comparison: Next.js vs Nuxt + Supabase",[23,1214,1216],{"id":1215},"why-boiledplate-chose-nuxt-supabase","Why BoiledPlate Chose Nuxt + Supabase",[11,1218,1219,1220,51],{},"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 ",[45,1221,63],{"href":61,"rel":1222},[49],[23,1224,1226],{"id":1225},"shipfasts-nextjs-stack","ShipFast's Next.js Stack",[11,1228,1229],{},"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.",[23,1231,1233],{"id":1232},"the-anti-plumbing-stack-question","The Anti-Plumbing Stack Question",[11,1235,1236,1237,1240,1241,1245],{},"Do these tools prevent plumbing, or just hide it? Honestly, neither eliminates it. The difference is ",[675,1238,1239],{},"where"," it's hidden. BoiledPlate hides it in agent-driven setup, deterministic patches, and an ",[45,1242,1244],{"href":106,"rel":1243},[49],"AGENTS.md convention contract"," that keeps agent output consistent. ShipFast hides it in battle-tested code you clone and customize by hand.",[15,1247,1249],{"id":1248},"agent-driven-setup-the-overlooked-differentiator","Agent-Driven Setup: The Overlooked Differentiator",[23,1251,1253],{"id":1252},"the-interview-model","The Interview Model",[11,1255,1256],{},"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.",[23,1258,1260],{"id":1259},"agentsmd-a-data-access-contract","AGENTS.md: A Data Access Contract",[11,1262,1263,1266,1267,51],{},[45,1264,896],{"href":106,"rel":1265},[49]," 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 ",[45,1268,1270],{"href":74,"rel":1269},[49],"every boilerplate ships the stack — that was never the hard part",[15,1272,1274],{"id":1273},"feature-parity-what-both-ship","Feature Parity: What Both Ship",[11,1276,1277],{},"On the checklist, they overlap more than they differ:",[502,1279,1280,1286,1292,1298,1304,1310,1316],{},[402,1281,1282,1285],{},[93,1283,1284],{},"Auth",": both ship it; quality differs on RLS enforcement.",[402,1287,1288,1291],{},[93,1289,1290],{},"Stripe",": both ship it; webhook robustness varies.",[402,1293,1294,1297],{},[93,1295,1296],{},"Database",": ShipFast flexible; BoiledPlate opinionated on Supabase.",[402,1299,1300,1303],{},[93,1301,1302],{},"Transactional email",": both; BoiledPlate defaults to Resend.",[402,1305,1306,1309],{},[93,1307,1308],{},"i18n",": BoiledPlate ships four languages by default; ShipFast optional.",[402,1311,1312,1315],{},[93,1313,1314],{},"Blog",": BoiledPlate prerenders Markdown; ShipFast is ecosystem-dependent.",[402,1317,1318,1321],{},[93,1319,1320],{},"Theming",": both; BoiledPlate lets you pick a preset or describe a custom theme in the setup interview.",[11,1323,1324,1327],{},[93,1325,1326],{},"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,1329,1330,1333],{},[93,1331,1332],{},"ShipFast-specific:"," larger ecosystem, more third-party integrations, a longer track record, more community templates, and freedom over database and backend choice.",[15,1335,1337],{"id":1336},"pricing-and-delivery","Pricing and Delivery",[11,1339,1340,1341,1345,1346,1350],{},"BoiledPlate is €159 one-time with lifetime updates and instant ",[45,1342,1344],{"href":284,"rel":1343},[49],"GitHub delivery"," — the repo is cloned into your account via webhook — plus a free, MIT-licensed ",[45,1347,1349],{"href":234,"rel":1348},[49],"Lite tier"," you can wire up manually. ShipFast runs roughly $129–$199 one-time depending on tier, with traditional download-and-clone delivery.",[11,1352,1353],{},"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.",[15,1355,1357],{"id":1356},"real-world-shipping-time-an-honest-breakdown","Real-World Shipping Time: An Honest Breakdown",[11,1359,1360],{},"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,1362,1363],{},"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,1365,1366],{},"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.",[15,1368,1370],{"id":1369},"common-bugs-both-stacks-hit","Common Bugs Both Stacks Hit",[11,1372,1373,1374,1378,1379,1382,1383,51],{},"Real launches trip on real bugs. Incorrect JSON-LD can crash hydration — we shipped a page that ",[45,1375,1377],{"href":198,"rel":1376},[49],"returned 200 from curl and 500 in Chrome"," because of source order. Canonical URLs are easy to break in multilingual sites; our blog once ",[45,1380,957],{"href":204,"rel":1381},[49],". And delivery-critical webhooks need careful failure semantics — some failures must throw, some never should, which we unpack in ",[45,1384,1386],{"href":217,"rel":1385},[49],"the GitHub invite is the product",[15,1388,1390],{"id":1389},"who-should-pick-which","Who Should Pick Which",[11,1392,1393,1396],{},[93,1394,1395],{},"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,1398,1399,1402],{},[93,1400,1401],{},"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,1404,1405,1408],{},[93,1406,1407],{},"Don't decide on"," framework popularity or \"faster shipping\" alone. Both hit the same plumbing wall.",[15,1410,1412],{"id":1411},"the-real-lesson","The Real Lesson",[11,1414,1415],{},"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,1417,1418],{},"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":301,"searchDepth":302,"depth":302,"links":1420},[1421,1422,1426,1430,1435,1439,1440,1441,1442,1443,1444],{"id":1121,"depth":305,"text":1122},{"id":1131,"depth":305,"text":1132,"children":1423},[1424,1425],{"id":1143,"depth":302,"text":1144},{"id":1171,"depth":302,"text":1172},{"id":1181,"depth":305,"text":1182,"children":1427},[1428,1429],{"id":1185,"depth":302,"text":1186},{"id":1197,"depth":302,"text":1198},{"id":1211,"depth":305,"text":1212,"children":1431},[1432,1433,1434],{"id":1215,"depth":302,"text":1216},{"id":1225,"depth":302,"text":1226},{"id":1232,"depth":302,"text":1233},{"id":1248,"depth":305,"text":1249,"children":1436},[1437,1438],{"id":1252,"depth":302,"text":1253},{"id":1259,"depth":302,"text":1260},{"id":1273,"depth":305,"text":1274},{"id":1336,"depth":305,"text":1337},{"id":1356,"depth":305,"text":1357},{"id":1369,"depth":305,"text":1370},{"id":1389,"depth":305,"text":1390},{"id":1411,"depth":305,"text":1412},"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":1113,"description":1446},"blog\u002Fshipfast-tech-vs-boiledplate-saas-boilerplate",[1452,342,1453,343],"saas-boilerplate","nuxt","JOhPGmMdHqpb4AXq6DZI6kqDMsQ47_s_iUq70C7tQ14",1789174351815]