[{"data":1,"prerenderedAt":1560},["ShallowReactive",2],{"blog-ai-boilerplate-why-templates-matter":3,"related-ai-boilerplate-why-templates-matter":400},{"id":4,"title":5,"author":6,"body":7,"category":6,"date":385,"description":386,"draft":387,"extension":388,"image":6,"meta":389,"navigation":390,"path":391,"seo":392,"stem":393,"tags":394,"__hash__":399},"blog\u002Fblog\u002Fai-boilerplate-why-templates-matter.md","AI Boilerplate: Why Code Templates Matter More Than Ever",null,{"type":8,"value":9,"toc":363},"minimark",[10,14,19,31,34,38,41,44,55,59,62,71,80,85,88,92,95,108,114,126,143,149,153,162,190,193,197,200,212,228,234,240,244,247,251,260,264,273,277,280,284,287,291,303,307,327,330,334,337,341,355],[11,12,13],"p",{},"AI can generate a working prototype from a paragraph of specification. So why do boilerplates still matter? If anything, they matter more now than they did before agents could write code. The reason has nothing to do with saving keystrokes and everything to do with constraints.",[15,16,18],"h2",{"id":17},"the-boilerplate-paradox","The Boilerplate Paradox",[11,20,21,22,26,27,30],{},"You'd think AI would kill boilerplates. It's doing the opposite. An agent handles ",[23,24,25],"em",{},"what"," you're building; a good boilerplate handles ",[23,28,29],{},"how"," it's built. That distinction is the whole game.",[11,32,33],{},"Boilerplate was never really about saving time on typing. It's about constraint enforcement — deciding, once, that there is one way to fetch data, one way to handle secrets, one way to verify a webhook. The value isn't \"fast to write.\" It's \"safe to customize.\" Code that an agent can generate in seconds is worthless if the next edit quietly contradicts it.",[15,35,37],{"id":36},"why-ai-struggles-with-boilerplate-and-why-thats-good","Why AI Struggles With Boilerplate (And Why That's Good)",[11,39,40],{},"Consistency requires conventions, not just correctness. An agent can produce a perfectly correct data-fetching function that happens to be the fourth pattern in your codebase. It isn't being dumb — it has no reason to prefer yours. It pattern-matches against everything it has ever seen, and everything it has ever seen includes every bad tutorial on the internet.",[11,42,43],{},"The real problem is drift, not generation speed. Agents excel at adding features and fail at enforcing architectural decisions across many edits. Give one three ways to do a thing and it adds a fourth.",[11,45,46,47,54],{},"BoiledPlate's answer is a shipped ",[48,49,53],"a",{"href":50,"rel":51},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fconventions-for-ai-coding-agents",[52],"nofollow","AGENTS.md contract",": one documented way to do data access, secrets, and conventions, so agent output stays consistent past month three. That's not a nice-to-have. When an agent is writing your code, consistency matters more than flexibility.",[15,56,58],{"id":57},"the-true-cost-of-saas-setup-isnt-the-stack","The True Cost of SaaS Setup Isn't the Stack",[11,60,61],{},"Choosing Nuxt, Supabase, and Stripe takes an afternoon. Wiring them together takes weeks. This is the part every stack argument misses.",[11,63,64,65,70],{},"Most boilerplates scaffold; they don't provision. They hand you a box of parts — auth, a Stripe client, a pile of Tailwind, a landing page — and leave you alone with a README. ",[48,66,69],{"href":67,"rel":68},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-saas-boilerplate-for-ai-agents",[52],"The parts were never the problem",". Bolting them to each other is what ate your weekends.",[11,72,73,74,79],{},"BoiledPlate takes a different route. ",[48,75,78],{"href":76,"rel":77},"https:\u002F\u002Fboiledplate.ai",[52],"Your coding agent doesn't just write the code — it provisions the services",": Stripe products and webhooks, a Supabase database with row-level security, Google sign-in. The setup interviews you (name, languages, theme, billing model), then reshapes the codebase with deterministic patches.",[81,82,84],"h3",{"id":83},"boilerplate-vs-automation","Boilerplate vs. automation",[11,86,87],{},"Traditional boilerplate: clone, delete unused code, wire manually. Automation-first boilerplate: the agent reads conventions and applies deterministic patches — repeatable, auditable, agent-readable customization. And the delivery model matters. The product isn't a ZIP; it's an instant GitHub invite. Provisioning, not a download.",[15,89,91],{"id":90},"the-plumbing-nobody-enjoys","The Plumbing Nobody Enjoys",[11,93,94],{},"Here's what belongs inside a boilerplate because getting it wrong costs real money.",[11,96,97,101,102,107],{},[98,99,100],"strong",{},"Webhook idempotency."," Stripe retries. A webhook that isn't idempotent turns retries into duplicate side effects — ghost charges, double provisioning. The fix is idempotency keys and handlers that safely absorb repeated calls. Stripe's own ",[48,103,106],{"href":104,"rel":105},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks#best-practices",[52],"best practices"," spell this out; most starters ignore it.",[11,109,110,113],{},[98,111,112],{},"Row-level security."," RLS in Supabase is not optional and not easy to retrofit. It's the difference between \"users only see their own rows\" and a user seeing someone else's data. Bolted on after launch, it's a rewrite. Built into the data layer, it's just how queries work.",[11,115,116,119,120,125],{},[98,117,118],{},"Billing state."," The source of truth is Stripe webhooks, not a client-side success page. A ",[48,121,124],{"href":122,"rel":123},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-webhooks-source-of-truth",[52],"checkout success page should not touch your billing state"," — the customer can close the tab, the network can drop, and your database has to be right anyway.",[11,127,128,131,132,137,138,142],{},[98,129,130],{},"Refund and consent flows."," EU consent law is real plumbing. Encoding a ",[48,133,136],{"href":134,"rel":135},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-checkout-consent-collection-german-withdrawal-waiver",[52],"German withdrawal waiver into the pay button"," via Stripe Checkout ",[139,140,141],"code",{},"consent_collection"," is exactly the kind of edge case that never appears in a demo and always appears in production.",[11,144,145,148],{},[98,146,147],{},"Transactional email."," Wired in with Resend, not bolted on later. Password resets and receipts are launch-day requirements, not phase two.",[15,150,152],{"id":151},"why-these-specific-tools-work-together","Why These Specific Tools Work Together",[11,154,155,156,161],{},"The ",[48,157,160],{"href":158,"rel":159},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fhow-to-ship-saas-fast",[52],"anti-plumbing stack"," is chosen for low surface area between the pieces.",[163,164,165,172,178,184],"ul",{},[166,167,168,171],"li",{},[98,169,170],{},"Nuxt + Supabase"," gives type safety end to end, with RLS as part of the framework's data layer rather than an afterthought.",[166,173,174,177],{},[98,175,176],{},"Stripe webhooks"," bring deterministic retry logic — which is exactly why signature verification and idempotent handlers are non-negotiable.",[166,179,180,183],{},[98,181,182],{},"Google sign-in"," is simpler than email\u002Fpassword but has its own traps (redirect URIs, consent screens) that a setup interview can handle once.",[166,185,186,189],{},[98,187,188],{},"Resend"," delivers transactional email reliably without you managing SMTP.",[11,191,192],{},"None of these choices is clever. Together they minimize the connective tissue you have to maintain.",[15,194,196],{"id":195},"real-world-bugs-and-edge-cases","Real-World Bugs and Edge Cases",[11,198,199],{},"Every one of these came out of shipping, not theory.",[11,201,202,205,206,211],{},[98,203,204],{},"JSON-LD hydration crashes."," A page can return ",[48,207,210],{"href":208,"rel":209},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-page-that-returned-200-on-the-server-and-500-in-the-browser-a-json-ld-tempor",[52],"200 from curl and 500 in Chrome"," because of source order in your structured data. SSR makes this class of bug invisible until a real browser hits it.",[11,213,214,217,218,223,224,227],{},[98,215,216],{},"Canonical URLs."," Browser defaults lie. Our blog once ",[48,219,222],{"href":220,"rel":221},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Four-blog-canonically-pointed-at-localhost",[52],"told Google its canonical URL was localhost:3000",". ",[139,225,226],{},"og:url"," and canonicals have to be set deliberately or search and social quietly break.",[11,229,230,233],{},[98,231,232],{},"Webhook retries that create ghost charges."," Idempotency keys are the fix, and testing them means deliberately replaying events, not hoping.",[11,235,236,239],{},[98,237,238],{},"i18n hydration mismatches."," Four languages from day one is a decision. Migrating to multi-locale later means touching the five places every new string has to land.",[15,241,243],{"id":242},"dashboard-theming-solved","Dashboard Theming, Solved",[11,245,246],{},"Preset themes are rarely enough; custom themes are painful to wire by hand. BoiledPlate lets you pick a preset — Warm Studio, Clean SaaS, Midnight Pro, Sharp Enterprise — or describe your own, and the agent maps it onto the codebase. The previews on the homepage are the real dashboard every buyer gets. Theming can't touch everything without breaking components, but the win is shipping a cohesive UI without design churn.",[15,248,250],{"id":249},"billing-that-survives-reality","Billing That Survives Reality",[11,252,253,254,259],{},"Multi-plan Stripe subscriptions mean tiers, add-ons, plan changes, and cancellations — ",[48,255,258],{"href":256,"rel":257},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-subscriptions-nuxt-supabase",[52],"five decisions"," that each ripple through your database. Signature-verified, idempotent handlers are the foundation. Refunds, cancellations, and plan changes need state machines that actually work, plus EU consent flows and audit trails. This is the part that's easy to skip and expensive to skip.",[15,261,263],{"id":262},"seo-and-content-from-day-one","SEO and Content From Day One",[11,265,266,267,272],{},"Most boilerplates ship no content layer. BoiledPlate ships a ",[48,268,271],{"href":269,"rel":270},"https:\u002F\u002Fboiledplate.ai\u002Fblog",[52],"blog"," built on prerendered Markdown — fast, searchable, no database queries for content. JSON-LD structured data and correct canonicals are built in, not retrofitted. You write in Markdown and deploy with your code. Content velocity is a feature.",[15,274,276],{"id":275},"typed-end-to-end","Typed End to End",[11,278,279],{},"\"Strict mode optional\" is a compromise that costs more later. BoiledPlate runs TypeScript in strict mode throughout. Database types come from the Supabase schema — schema drives types, not the reverse. Nitro types your API routes. Type safety in webhook handlers is what prevents silent billing failures, where a shape mismatch fails quietly instead of loudly.",[15,281,283],{"id":282},"deployment-in-minutes","Deployment in Minutes",[11,285,286],{},"\"Minutes\" assumes prerequisites: a Stripe account, a Supabase project, a Google OAuth app. The GitHub delivery model beats downloading a ZIP because it's instant and versioned. Environment variables are validated rather than assumed. You can deploy to Vercel, Netlify, or self-host. Post-deploy, the milestones that matter are your first webhook, first payment, and first email — all working.",[15,288,290],{"id":289},"free-vs-pro","Free vs. Pro",[11,292,293,298,299,302],{},[48,294,297],{"href":295,"rel":296},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Ffree-nuxt-supabase-saas-boilerplate",[52],"BoiledPlate Lite"," is MIT-licensed: source available, clone and wire manually, no agent interview. ",[98,300,301],{},"Pro"," is €159 one-time with lifetime updates, agent-driven setup, and instant GitHub delivery. The real trade-off is your time versus €159. Budget-constrained builders clone Lite; founders shipping weekly buy Pro.",[15,304,306],{"id":305},"the-anti-boilerplate-arguments","The Anti-Boilerplate Arguments",[163,308,309,315,321],{},[166,310,311,314],{},[23,312,313],{},"\"Just use no-code SaaS tools.\""," Costs 10x more over time, with lock-in and less control.",[166,316,317,320],{},[23,318,319],{},"\"Build everything from scratch.\""," Great teacher, three months per SaaS.",[166,322,323,326],{},[23,324,325],{},"\"Use a different framework.\""," Framework choice is easy; plumbing is framework-agnostic.",[11,328,329],{},"Boilerplates are asymmetric: high fixed cost upfront, near-zero marginal cost after. That's exactly why they pay off.",[15,331,333],{"id":332},"reducing-the-real-risk","Reducing the Real Risk",[11,335,336],{},"The genuine fear is lock-in — that a boilerplate makes customization hell. BoiledPlate's answer is semantic versioning, deterministic patches, and readable release notes. Updates are opt-in: you see what changes before you merge, and the agent can read your customizations instead of fighting them. The AGENTS.md contract keeps agents consistent even as your code diverges.",[15,338,340],{"id":339},"getting-started-a-decision-tree","Getting Started: A Decision Tree",[163,342,343,346,349,352],{},[166,344,345],{},"Need multi-plan billing? → You want a real boilerplate, not a scaffold.",[166,347,348],{},"Can you describe your SaaS in an interview? → Agent setup fits.",[166,350,351],{},"Want to customize without breaking updates? → Deterministic patches.",[166,353,354],{},"Is your time worth €159? → Usually yes → Pro. Sometimes no → Lite.",[11,356,357,358,362],{},"The stack was never the hard part. The wiring is. An AI boilerplate earns its place not by writing code faster, but by holding the line on how that code is built — so the agent, and you, can keep shipping without drift. That's the ",[48,359,361],{"href":76,"rel":360},[52],"whole point of BoiledPlate",": buy once, ship product instead of plumbing.",{"title":364,"searchDepth":365,"depth":365,"links":366},"",3,[367,369,370,373,374,375,376,377,378,379,380,381,382,383,384],{"id":17,"depth":368,"text":18},2,{"id":36,"depth":368,"text":37},{"id":57,"depth":368,"text":58,"children":371},[372],{"id":83,"depth":365,"text":84},{"id":90,"depth":368,"text":91},{"id":151,"depth":368,"text":152},{"id":195,"depth":368,"text":196},{"id":242,"depth":368,"text":243},{"id":249,"depth":368,"text":250},{"id":262,"depth":368,"text":263},{"id":275,"depth":368,"text":276},{"id":282,"depth":368,"text":283},{"id":289,"depth":368,"text":290},{"id":305,"depth":368,"text":306},{"id":332,"depth":368,"text":333},{"id":339,"depth":368,"text":340},"2026-09-14","Discover why AI boilerplates are essential for enforcing consistency and architectural decisions in AI-generated code, not just saving time.",false,"md",{},true,"\u002Fblog\u002Fai-boilerplate-why-templates-matter",{"title":5,"description":386},"blog\u002Fai-boilerplate-why-templates-matter",[395,396,397,398],"ai-boilerplate","code-generation","software-architecture","ai-development","MzpqZbpOYENbvFc8Hb2t7pMMYaWIoUk9ofqRg2Y94bM",[401,812,1121],{"id":402,"title":403,"author":6,"body":404,"category":6,"date":800,"description":801,"draft":387,"extension":388,"image":6,"meta":802,"navigation":390,"path":803,"seo":804,"stem":805,"tags":806,"__hash__":811},"blog\u002Fblog\u002Fshipfast-vs-boilerplate-comparison.md","ShipFast vs BoiledPlate: Next.js Boilerplate Showdown",{"type":8,"value":405,"toc":780},[406,409,412,416,419,422,426,429,432,436,444,455,459,467,476,480,492,502,506,509,518,522,525,533,537,540,543,547,554,558,679,683,686,689,693,696,700,703,729,732,736,739,743,746,750,756,762,766,773,777],[11,407,408],{},"Search \"shipfast vs\" and you land in a familiar debate: which Next.js boilerplate ships fastest? ShipFast, LaunchFast, TurboStarter, IndieKit — they all sell the same promise of launching in days. BoiledPlate takes a different position entirely. It's not a faster template. It's an AI-native Nuxt + Supabase starter whose setup runs itself: a coding agent interviews you, then provisions Stripe, Supabase, and Google sign-in in one session.",[11,410,411],{},"This comparison is honest about where ShipFast wins and where an agent-driven, Nuxt-based approach pulls ahead.",[15,413,415],{"id":414},"shipfast-what-it-does-well","ShipFast: What It Does Well",[11,417,418],{},"ShipFast earned its reputation for good reasons. It's a well-polished Next.js boilerplate with Stripe integration out of the box, a large community, and an opinionated stack that kills decision fatigue. If you already live in the React and Next.js world, ShipFast lets you clone a repo and have a landing page, auth, and payments scaffolded quickly.",[11,420,421],{},"Its template ecosystem is genuinely large. For a non-technical founder or a solo dev who wants a proven path, that ecosystem is a real advantage.",[15,423,425],{"id":424},"where-shipfast-falls-short","Where ShipFast Falls Short",[11,427,428],{},"The cracks show once you customize. ShipFast means Next.js lock-in — customizing the framework means fighting its conventions. Services are wired manually; there's no agent-driven setup. Webhook handling doesn't guarantee idempotency, security often lives in your API layer rather than the database, and updates force merge conflicts into code you've already modified.",[11,430,431],{},"Most importantly for 2026: ShipFast has no agent-specific contract. When you point a coding agent at it, the agent has no documented conventions to follow, so its output drifts.",[15,433,435],{"id":434},"boiledplates-core-advantage-agent-native-architecture","BoiledPlate's Core Advantage: Agent-Native Architecture",[11,437,438,439,443],{},"BoiledPlate is built for the way people actually code now — with a coding agent in the loop. As the ",[48,440,442],{"href":76,"rel":441},[52],"homepage"," puts it: your coding agent doesn't just write the code, it provisions the services. Stripe products and webhooks, a Supabase database with RLS, Google sign-in — the plumbing nobody enjoys, done in one session.",[11,445,446,447,450,451,454],{},"The agent's first session interviews you: name, languages, theme, billing model. Then it reshapes the entire codebase to your answers with ",[98,448,449],{},"deterministic patches"," — automated, repeatable changes rather than hand-edits. And it ships with an ",[98,452,453],{},"AGENTS.md"," contract so the agent stays consistent across generations, which is a problem ShipFast never solved because it wasn't designed for agents.",[15,456,458],{"id":457},"the-real-cost-of-saas-setup-plumbing-not-frameworks","The Real Cost of SaaS Setup: Plumbing, Not Frameworks",[11,460,461,462,466],{},"Here's the thing every boilerplate comparison misses. Ask ten founders how to ship fast and you get ten stack arguments — Next vs Nuxt, Postgres vs hosted, Stripe vs Paddle. Pick whatever you know and the debate is over in an afternoon. As we argue in ",[48,463,465],{"href":158,"rel":464},[52],"the stack is easy, the plumbing is the project",", the framework is not what slows you down.",[11,468,469,470,475],{},"What slows you down is the wiring between services: webhook idempotency, row-level security, refund flows, EU consent, transactional email that sends exactly once. Our breakdown of ",[48,471,474],{"href":472,"rel":473},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-supabase-stripe-saas-boilerplate",[52],"what it actually takes to wire up a Nuxt, Supabase and Stripe SaaS"," walks through each service's hidden demands. This is the phase BoiledPlate automates — and the phase ShipFast leaves to you or to a paid done-for-you service.",[15,477,479],{"id":478},"billing-architecture-why-it-matters","Billing Architecture: Why It Matters",[11,481,482,483,487,488,491],{},"Billing is where corner-cutting hurts most. Stripe ",[48,484,486],{"href":122,"rel":485},[52],"webhooks must be the source of truth",", not the client-side success page — because users close tabs, networks drop, and Stripe retries. An ",[98,489,490],{},"idempotent webhook"," handles those retries without double-charging or losing a refund.",[11,493,494,495,498,499,501],{},"BoiledPlate ships a production-ready implementation: signature-verified, idempotent webhooks with real state management. It even handles EU-specific requirements like encoding a ",[48,496,136],{"href":134,"rel":497},[52]," via Stripe's ",[139,500,141],{},". These are the details that don't appear in a \"launch in days\" demo but absolutely appear in a chargeback dispute.",[15,503,505],{"id":504},"database-security-supabase-rls-vs-traditional-auth","Database Security: Supabase RLS vs Traditional Auth",[11,507,508],{},"Next.js boilerplates like ShipFast typically enforce permissions in the API layer — middleware checks before a query runs. Miss one route, and you've leaked data.",[11,510,511,512,517],{},"Supabase ",[48,513,516],{"href":514,"rel":515},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fpostgres\u002Frow-level-security",[52],"row-level security"," enforces permissions at query time, in the database itself. Even if application code has a bug, the database refuses to return rows the user shouldn't see. That's a smaller attack surface and it scales better than scattering middleware checks across every endpoint. BoiledPlate ships RLS policies baked into its deterministic patches, so security isn't an afterthought you bolt on later.",[15,519,521],{"id":520},"ai-agent-consistency-why-agentsmd-exists","AI Agent Consistency: Why AGENTS.md Exists",[11,523,524],{},"Point two agents at the same vague task and you get two different implementations — different data-access patterns, different secret handling, different conventions. That drift is the enemy of a maintainable codebase.",[11,526,527,528,532],{},"AGENTS.md fixes this by documenting one documented way to access data and handle secrets. We cover the philosophy in ",[48,529,531],{"href":50,"rel":530},[52],"write your conventions for the agent, not the next hire",": conventions used to be for onboarding humans; now they keep agents from reinventing your architecture every session. ShipFast has no such contract. BoiledPlate ships AGENTS.md from day one, which is what makes repeatable agent interviews and safe patches possible.",[15,534,536],{"id":535},"customization-philosophy-merges-vs-patches","Customization Philosophy: Merges vs Patches",[11,538,539],{},"Update a ShipFast project you've heavily modified, and you're in merge-conflict territory. Every upstream change collides with your changes.",[11,541,542],{},"BoiledPlate uses semantic, agent-readable release notes and deterministic patches. You opt into updates. You can skip a breaking change or cherry-pick a single feature, and the agent applies the patch consistently — no human line-by-line merging. This is the difference between owning a starter kit and being trapped by it.",[15,544,546],{"id":545},"the-anti-plumbing-stack-nuxt-supabase-stripe","The Anti-Plumbing Stack: Nuxt + Supabase + Stripe",[11,548,549,550,553],{},"Each tool pulls its weight. Nuxt is lightweight and composable and plays well with edge functions. Supabase folds RLS, real-time, and auth into one service, so you integrate fewer things. Stripe's explicit webhook requirements ",[23,551,552],{},"force"," good architecture early — you can't fake billing state and hope. This trio demands you get billing right, and BoiledPlate enforces it rather than papering over it.",[15,555,557],{"id":556},"comparison-table-boiledplate-vs-shipfast","Comparison Table: BoiledPlate vs ShipFast",[559,560,561,576],"table",{},[562,563,564],"thead",{},[565,566,567,570,573],"tr",{},[568,569],"th",{},[568,571,572],{},"BoiledPlate",[568,574,575],{},"ShipFast",[577,578,579,591,602,613,624,635,646,657,668],"tbody",{},[565,580,581,585,588],{},[582,583,584],"td",{},"Framework \u002F language",[582,586,587],{},"Nuxt 4, TypeScript strict",[582,589,590],{},"Next.js",[565,592,593,596,599],{},[582,594,595],{},"Billing \u002F webhooks",[582,597,598],{},"Idempotent, signature-verified, source-of-truth",[582,600,601],{},"Stripe wired, no idempotency guarantee",[565,603,604,607,610],{},[582,605,606],{},"DB security",[582,608,609],{},"Supabase RLS at query time",[582,611,612],{},"API-layer auth",[565,614,615,618,621],{},[582,616,617],{},"Updates",[582,619,620],{},"Deterministic patches, opt-in",[582,622,623],{},"Manual merges",[565,625,626,629,632],{},[582,627,628],{},"Agent-native",[582,630,631],{},"AGENTS.md contract, agent setup",[582,633,634],{},"None",[565,636,637,640,643],{},[582,638,639],{},"Pricing \u002F delivery",[582,641,642],{},"€159 one-time, GitHub delivery",[582,644,645],{},"Paid, clone repo",[565,647,648,651,654],{},[582,649,650],{},"i18n",[582,652,653],{},"Four languages day one",[582,655,656],{},"Add yourself",[565,658,659,662,665],{},[582,660,661],{},"SEO",[582,663,664],{},"JSON-LD, og:url canonicals",[582,666,667],{},"Basic",[565,669,670,673,676],{},[582,671,672],{},"Blog",[582,674,675],{},"Prerendered Markdown, ready",[582,677,678],{},"Varies",[15,680,682],{"id":681},"common-objections-why-not-just-use-shipfast","Common Objections: \"Why Not Just Use ShipFast?\"",[11,684,685],{},"Fair question. ShipFast is faster for a non-technical founder with no coding agent in their workflow. Its template library is larger. BoiledPlate assumes comfort with Nuxt, Supabase, and agent-driven workflows — that's a real prerequisite.",[11,687,688],{},"The choice is honest: pick ShipFast if you want done-for-you UX and a big Next.js ecosystem. Pick BoiledPlate if you want deterministic, updatable plumbing you can regenerate across projects.",[15,690,692],{"id":691},"other-alternatives-worth-naming","Other Alternatives Worth Naming",[11,694,695],{},"LaunchFast is another Next.js boilerplate — same framework lock-in as ShipFast. TurboStarter is production-ready but has no agent-driven setup. CodeConductor plays a different game entirely (prompt-based workflow automation, not a plumbed starter). IndieKit is polished but light on B2B and complex billing. None of them are agent-native in BoiledPlate's sense: interview, provision, patch, repeat.",[15,697,699],{"id":698},"real-world-debugging-lessons-from-production","Real-World Debugging: Lessons from Production",[11,701,702],{},"BoiledPlate exists because we shipped this stack and kept a running log of every edge case. This site runs on it. Some of the bugs we solved so you don't have to:",[163,704,705,713,720],{},[166,706,707,708,712],{},"A ",[48,709,711],{"href":208,"rel":710},[52],"JSON-LD hydration crash"," that returned 200 from curl and 500 in Chrome, caused by source order.",[166,714,707,715,719],{},[48,716,718],{"href":220,"rel":717},[52],"canonical URL pointing at localhost:3000",", quietly telling Google the wrong thing.",[166,721,722,723,728],{},"Webhook signature verification that prevents replay attacks — plus the subtle case of a ",[48,724,727],{"href":725,"rel":726},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-github-invite-is-the-product-building-a-stripe-webhook-where-delivery-throws",[52],"GitHub-invite webhook where some failures must throw and some never should",".",[11,730,731],{},"These ship pre-solved.",[15,733,735],{"id":734},"the-hidden-cost-of-speed","The Hidden Cost of Speed",[11,737,738],{},"\"Launch in days\" often means debt in billing, security, and updates. Proper webhook handling and RLS take time upfront but pay off when real money moves. Agent-driven setup also forces you to document conventions, which prevents the \"custom boilerplate nobody understands\" trap. BoiledPlate amortizes that plumbing cost once, upfront.",[15,740,742],{"id":741},"delivery-model-github-invites-as-the-product","Delivery Model: GitHub Invites as the Product",[11,744,745],{},"ShipFast: clone the repo, wire it, or pay for setup. BoiledPlate Pro: the agent interviews you, provisions services, and delivers to your GitHub in one session — instant delivery via webhooks, no manual handoff. Lifetime updates included, and you choose which patches to accept.",[15,747,749],{"id":748},"when-to-choose-which","When to Choose Which",[11,751,752,755],{},[98,753,754],{},"Choose BoiledPlate"," if you're comfortable with Nuxt and Supabase, you work with Claude or a similar agent, you want billing and RLS done right from day one, and you're shipping multiple products where agents reuse AGENTS.md patterns.",[11,757,758,761],{},[98,759,760],{},"ShipFast still wins"," if you need Next.js specifically for ecosystem or hiring, you're non-technical, your product only needs simple one-time payments, you want the larger community, or you won't iterate on plumbing after launch.",[15,763,765],{"id":764},"getting-started-lite-vs-pro","Getting Started: Lite vs Pro",[11,767,768,769,772],{},"You can try the approach for free. ",[48,770,297],{"href":295,"rel":771},[52]," is MIT-licensed — the same Nuxt 4, Supabase, Stripe, and Resend app, minus the AI tooling, that you clone and wire by hand. Pro is €159 one-time: the agent interviews you, delivers instantly, and includes lifetime updates. No subscription trap; pay once, own the code. If you're shipping more than one SaaS, the ROI compounds.",[15,774,776],{"id":775},"the-future-of-saas-setup-agents-not-frameworks","The Future of SaaS Setup: Agents, Not Frameworks",[11,778,779],{},"The \"shipfast vs\" debate is really a framework debate, and the framework was never the hard part. Agent-driven interviews, deterministic patches, and AGENTS.md-style contracts are becoming the standard way to customize a starter safely and repeatedly. BoiledPlate is built for that future rather than fighting it — which is the real reason to look past the Next.js template shelf.",{"title":364,"searchDepth":365,"depth":365,"links":781},[782,783,784,785,786,787,788,789,790,791,792,793,794,795,796,797,798,799],{"id":414,"depth":368,"text":415},{"id":424,"depth":368,"text":425},{"id":434,"depth":368,"text":435},{"id":457,"depth":368,"text":458},{"id":478,"depth":368,"text":479},{"id":504,"depth":368,"text":505},{"id":520,"depth":368,"text":521},{"id":535,"depth":368,"text":536},{"id":545,"depth":368,"text":546},{"id":556,"depth":368,"text":557},{"id":681,"depth":368,"text":682},{"id":691,"depth":368,"text":692},{"id":698,"depth":368,"text":699},{"id":734,"depth":368,"text":735},{"id":741,"depth":368,"text":742},{"id":748,"depth":368,"text":749},{"id":764,"depth":368,"text":765},{"id":775,"depth":368,"text":776},"2026-09-13","Compare ShipFast and BoiledPlate boilerplates. Explore strengths, weaknesses, and which starter fits your indie hacking needs.",{},"\u002Fblog\u002Fshipfast-vs-boilerplate-comparison",{"title":403,"description":801},"blog\u002Fshipfast-vs-boilerplate-comparison",[807,808,809,810],"boilerplate","nextjs","shipfast","indie-hacking","5EhTPEW-oQ1r4PJB_o14us70Q_4JQXatZUHZhu2cge0",{"id":813,"title":814,"author":6,"body":815,"category":6,"date":1111,"description":1112,"draft":387,"extension":388,"image":6,"meta":1113,"navigation":390,"path":1114,"seo":1115,"stem":1116,"tags":1117,"__hash__":1120},"blog\u002Fblog\u002Fshipfast-twitter-hype-reality.md","ShipFast Twitter Hype vs Reality: What the Template Actually Solves",{"type":8,"value":816,"toc":1082},[817,820,824,827,831,834,838,841,845,852,856,863,867,875,879,882,886,892,896,904,908,911,915,918,922,930,934,942,946,954,958,961,963,966,970,978,982,995,999,1007,1011,1022,1028,1032,1035,1039,1053,1056,1060,1063],[11,818,819],{},"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,821,823],{"id":822},"the-shipfast-phenomenon","The ShipFast Phenomenon",[11,825,826],{},"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.",[81,828,830],{"id":829},"what-shipfast-does-right","What ShipFast Does Right",[11,832,833],{},"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.",[81,835,837],{"id":836},"what-shipfast-doesnt-solve","What ShipFast Doesn't Solve",[11,839,840],{},"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,842,844],{"id":843},"the-hidden-cost-of-saas-plumbing","The Hidden Cost of SaaS Plumbing",[11,846,847,848,728],{},"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. ",[48,849,851],{"href":158,"rel":850},[52],"The framework is not what slows you down",[81,853,855],{"id":854},"stack-choice-takes-hours-wiring-takes-weeks","Stack Choice Takes Hours; Wiring Takes Weeks",[11,857,858,859,862],{},"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 ",[48,860,474],{"href":472,"rel":861},[52],", auth is the fast part and RLS is the part you forget until a user sees someone else's data.",[81,864,866],{"id":865},"why-templates-stop-short","Why Templates Stop Short",[11,868,869,870,874],{},"Every SaaS starter hands you the same box of parts: auth, a database client, a Stripe integration, a pile of Tailwind. Then it ",[48,871,873],{"href":67,"rel":872},[52],"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,876,878],{"id":877},"boiledplate-automation-beyond-the-template","BoiledPlate: Automation Beyond the Template",[11,880,881],{},"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.",[81,883,885],{"id":884},"agent-driven-setup-the-interview-model","Agent-Driven Setup: The Interview Model",[11,887,888,889,891],{},"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 ",[98,890,449],{}," — repeatable, trackable changes rather than manual copy-paste. You describe your dashboard theme in plain language and the agent maps it onto real code.",[81,893,895],{"id":894},"agentsmd-the-consistency-contract","AGENTS.md: The Consistency Contract",[11,897,898,899,903],{},"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 ",[48,900,902],{"href":50,"rel":901},[52],"your agent's output stays predictable across sessions",". Write your conventions for the agent, not just the next hire.",[15,905,907],{"id":906},"billing-that-actually-works","Billing That Actually Works",[11,909,910],{},"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.",[81,912,914],{"id":913},"idempotent-webhooks-the-non-negotiable-foundation","Idempotent Webhooks: The Non-Negotiable Foundation",[11,916,917],{},"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.",[81,919,921],{"id":920},"the-source-of-truth-isnt-your-ui","The Source of Truth Isn't Your UI",[11,923,924,925,929],{},"A checkout success page means the browser reached a URL. It does not mean payment settled. ",[48,926,928],{"href":122,"rel":927},[52],"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.",[81,931,933],{"id":932},"the-consent-problem-german-withdrawal-waivers-and-gdpr","The Consent Problem: German Withdrawal Waivers and GDPR",[11,935,936,937,941],{},"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 ",[48,938,940],{"href":134,"rel":939},[52],"how to do this with Stripe Checkout's consent_collection"," — the sort of detail that fails audits when ignored.",[15,943,945],{"id":944},"multi-plan-subscriptions-and-real-complexity","Multi-Plan Subscriptions and Real Complexity",[11,947,948,949,953],{},"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. ",[48,950,952],{"href":256,"rel":951},[52],"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,955,957],{"id":956},"auth-done-right-rls-and-row-level-security","Auth Done Right: RLS and Row-Level Security",[11,959,960],{},"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,962,546],{"id":545},[11,964,965],{},"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,967,969],{"id":968},"transactional-email-resend-and-the-idempotency-problem","Transactional Email: Resend and the Idempotency Problem",[11,971,972,973,977],{},"Email is simple to send and ",[48,974,976],{"href":472,"rel":975},[52],"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,979,981],{"id":980},"seo-and-real-debugging-stories","SEO and Real Debugging Stories",[11,983,984,985,989,990,994],{},"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 ",[48,986,988],{"href":208,"rel":987},[52],"returned 200 from curl and 500 in the browser",". Another time our ",[48,991,993],{"href":220,"rel":992},[52],"blog told Google its canonical URL was localhost:3000",". Blogs run on prerendered Markdown — static, fast, no headless CMS required.",[15,996,998],{"id":997},"deployment-the-github-invite-as-your-product","Deployment: The GitHub Invite as Your Product",[11,1000,1001,1002,1006],{},"Product delivery is a technical problem. Sending code via email or Slack is a support nightmare. BoiledPlate treats ",[48,1003,1005],{"href":725,"rel":1004},[52],"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,1008,1010],{"id":1009},"lite-vs-pro-free-or-lifetime-updates","Lite vs. Pro: Free or Lifetime Updates",[11,1012,1013,1014,1016,1017,1021],{},"There are two paths. ",[98,1015,297],{}," is ",[48,1018,1020],{"href":295,"rel":1019},[52],"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,1023,1024,1027],{},[98,1025,1026],{},"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,1029,1031],{"id":1030},"real-world-failure-modes","Real-World Failure Modes",[11,1033,1034],{},"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,1036,1038],{"id":1037},"choosing-your-path","Choosing Your Path",[11,1040,1041,1044,1045,1048,1049,1052],{},[98,1042,1043],{},"Clone and wire manually"," when you have strong stack opinions and time to spend. ",[98,1046,1047],{},"Use a standard template"," like ShipFast when you like the stack and are happy wiring services yourself. ",[98,1050,1051],{},"Choose automation"," when billing is critical to your business, you work with coding agents, and you value staying current without rewriting.",[11,1054,1055],{},"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,1057,1059],{"id":1058},"the-bottom-line","The Bottom Line",[11,1061,1062],{},"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,1064,1065,1066,1070,1071,1075,1076,1081],{},"You can ",[48,1067,1069],{"href":76,"rel":1068},[52],"start with BoiledPlate"," or read the ",[48,1072,1074],{"href":269,"rel":1073},[52],"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 ",[48,1077,1080],{"href":1078,"rel":1079},"https:\u002F\u002Fdocs.stripe.com\u002Fwebhooks",[52],"webhook best practices"," documentation is worth the read — it explains, in Stripe's words, exactly why idempotency and signature verification aren't optional.",{"title":364,"searchDepth":365,"depth":365,"links":1083},[1084,1088,1092,1096,1101,1102,1103,1104,1105,1106,1107,1108,1109,1110],{"id":822,"depth":368,"text":823,"children":1085},[1086,1087],{"id":829,"depth":365,"text":830},{"id":836,"depth":365,"text":837},{"id":843,"depth":368,"text":844,"children":1089},[1090,1091],{"id":854,"depth":365,"text":855},{"id":865,"depth":365,"text":866},{"id":877,"depth":368,"text":878,"children":1093},[1094,1095],{"id":884,"depth":365,"text":885},{"id":894,"depth":365,"text":895},{"id":906,"depth":368,"text":907,"children":1097},[1098,1099,1100],{"id":913,"depth":365,"text":914},{"id":920,"depth":365,"text":921},{"id":932,"depth":365,"text":933},{"id":944,"depth":368,"text":945},{"id":956,"depth":368,"text":957},{"id":545,"depth":368,"text":546},{"id":968,"depth":368,"text":969},{"id":980,"depth":368,"text":981},{"id":997,"depth":368,"text":998},{"id":1009,"depth":368,"text":1010},{"id":1030,"depth":368,"text":1031},{"id":1037,"depth":368,"text":1038},{"id":1058,"depth":368,"text":1059},"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.",{},"\u002Fblog\u002Fshipfast-twitter-hype-reality",{"title":814,"description":1112},"blog\u002Fshipfast-twitter-hype-reality",[809,1118,1119,807],"next.js","indie hackers","Ke8c5Jf200Ucs7-Hf2CoelPnFMCo4kuAztgCccoNUEI",{"id":1122,"title":1123,"author":6,"body":1124,"category":6,"date":1549,"description":1550,"draft":387,"extension":388,"image":6,"meta":1551,"navigation":390,"path":1552,"seo":1553,"stem":1554,"tags":1555,"__hash__":1559},"blog\u002Fblog\u002Fshipfast-tutorial.md","ShipFast Tutorial: Build Production-Ready Startups Faster",{"type":8,"value":1125,"toc":1529},[1126,1129,1133,1141,1144,1148,1151,1164,1168,1171,1198,1201,1205,1213,1221,1225,1233,1236,1244,1248,1251,1254,1258,1264,1267,1271,1307,1311,1324,1328,1331,1335,1341,1347,1353,1368,1374,1378,1397,1400,1404,1436,1440,1451,1457,1463,1467,1470,1474,1477,1481,1484,1488,1517],[11,1127,1128],{},"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,1130,1132],{"id":1131},"what-is-boiledplate","What is BoiledPlate?",[11,1134,1135,1136,1140],{},"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: ",[48,1137,1139],{"href":76,"rel":1138},[52],"Stripe products and webhooks, a Supabase database with RLS, and Google sign-in"," — in a single session.",[11,1142,1143],{},"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,1145,1147],{"id":1146},"the-real-problem-boiledplate-solves","The Real Problem BoiledPlate Solves",[11,1149,1150],{},"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,1152,1153,1154,1158,1159,1163],{},"\"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 ",[48,1155,1157],{"href":122,"rel":1156},[52],"your success page should never be the source of billing truth",". We wrote about this at length in ",[48,1160,1162],{"href":158,"rel":1161},[52],"why the stack is easy and the plumbing is the project"," — it's the thesis the whole product is built on.",[15,1165,1167],{"id":1166},"how-boiledplate-actually-works","How BoiledPlate Actually Works",[11,1169,1170],{},"The flow is concrete, not marketing:",[1172,1173,1174,1180,1186,1192],"ol",{},[166,1175,1176,1179],{},[98,1177,1178],{},"The agent interviews you."," Name, languages, theme, billing model, user roles, consent requirements.",[166,1181,1182,1185],{},[98,1183,1184],{},"The agent reads the AGENTS.md contract and applies deterministic patches."," These are repeatable, idempotent code changes — not vibes.",[166,1187,1188,1191],{},[98,1189,1190],{},"Services auto-provision."," Supabase (cloud or local Docker) with RLS policies, Stripe products and webhooks, Google OAuth.",[166,1193,1194,1197],{},[98,1195,1196],{},"A webhook proves billing state landed."," The source of truth is the webhook hitting your database, not client-side confetti.",[11,1199,1200],{},"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,1202,1204],{"id":1203},"the-anti-plumbing-stack-why-nuxt-supabase-stripe","The Anti-Plumbing Stack: Why Nuxt + Supabase + Stripe",[11,1206,1207,1208,1212],{},"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 ",[48,1209,1211],{"href":514,"rel":1210},[52],"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,1214,1215,1216,1220],{},"The trap is mixing them carelessly — trusting a checkout redirect for access, or checking auth in middleware and calling it security. ",[48,1217,1219],{"href":472,"rel":1218},[52],"Wiring these four services correctly"," is precisely the multi-week task BoiledPlate collapses.",[15,1222,1224],{"id":1223},"billing-architecture-that-survives-reality","Billing Architecture That Survives Reality",[11,1226,1227,1228,1232],{},"Stripe and Supabase have a clean division of labor: Stripe owns payment and subscription lifecycle; your database owns access. The ",[48,1229,1231],{"href":256,"rel":1230},[52],"webhook is where subscriptions actually live",". BoiledPlate ships multi-plan subscriptions with signature-verified, idempotent webhook handlers.",[11,1234,1235],{},"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,1237,1238,1239,1243],{},"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 ",[48,1240,1242],{"href":134,"rel":1241},[52],"Stripe Checkout's consent_collection",". No five-minute tutorial touches this.",[15,1245,1247],{"id":1246},"auth-done-right-rls-without-footguns","Auth Done Right: RLS Without Footguns",[11,1249,1250],{},"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,1252,1253],{},"The other footgun is skipping signature verification on webhooks. An unverified endpoint accepts forged events. BoiledPlate verifies signatures before anything touches the database.",[15,1255,1257],{"id":1256},"agent-consistency-the-agentsmd-contract","Agent Consistency: The AGENTS.md Contract",[11,1259,1260,1261,728],{},"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 ",[48,1262,531],{"href":50,"rel":1263},[52],[11,1265,1266],{},"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,1268,1270],{"id":1269},"features-that-ship-out-of-the-box","Features That Ship Out of the Box",[163,1272,1273,1279,1285,1291,1297],{},[166,1274,1275,1278],{},[98,1276,1277],{},"Transactional email (Resend):"," onboarding, receipts, and cancellations wired, not left as an exercise.",[166,1280,1281,1284],{},[98,1282,1283],{},"i18n from day one:"," four languages preloaded; the agent respects translation keys in every patch.",[166,1286,1287,1290],{},[98,1288,1289],{},"A blog ready to write:"," prerendered Markdown with SEO — JSON-LD and canonical URLs — built in.",[166,1292,1293,1296],{},[98,1294,1295],{},"Dashboard theming:"," pick a preset or describe your own; the agent maps it onto the component library. These are real previews every buyer gets.",[166,1298,1299,1302,1303,1306],{},[98,1300,1301],{},"TypeScript strict mode:"," no ",[139,1304,1305],{},"any"," escape hatches, which makes agent-readable types and safer patches.",[15,1308,1310],{"id":1309},"the-seo-foundation-tutorials-usually-miss","The SEO Foundation Tutorials Usually Miss",[11,1312,1313,1314,1318,1319,1323],{},"\"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 ",[48,1315,1317],{"href":220,"rel":1316},[52],"our blog told Google its canonical was localhost:3000",". JSON-LD matters too — and it can bite you. A ",[48,1320,1322],{"href":208,"rel":1321},[52],"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,1325,1327],{"id":1326},"shipping-without-merge-hell","Shipping Without Merge Hell",[11,1329,1330],{},"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,1332,1334],{"id":1333},"setup-walkthrough-zero-to-stripe-webhook-in-one-session","Setup Walkthrough: Zero to Stripe Webhook in One Session",[11,1336,1337,1340],{},[98,1338,1339],{},"Prerequisites:"," a Stripe account, a Supabase org, and a Google OAuth app.",[11,1342,1343,1346],{},[98,1344,1345],{},"Run the interview."," The agent asks about plans, roles, languages, theme, and consent. Answer plainly; there's no framework debate to have.",[11,1348,1349,1352],{},[98,1350,1351],{},"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,1354,1355,1358,1359,1367],{},[98,1356,1357],{},"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 ",[48,1360,1363,1364],{"href":1361,"rel":1362},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fvercel-web-analytics-nuxt-4-analytics-package-breaks-typecheck",[52],"package can break ",[139,1365,1366],{},"nuxt typecheck"," — we documented the fix.)",[11,1369,1370,1373],{},[98,1371,1372],{},"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,1375,1377],{"id":1376},"boiledplate-lite-vs-pro","BoiledPlate Lite vs. Pro",[163,1379,1380,1391],{},[166,1381,1382,1385,1386,1390],{},[98,1383,1384],{},"Lite (MIT, free):"," clone the repo and ",[48,1387,1389],{"href":295,"rel":1388},[52],"wire services yourself",". Good for learning the patterns or a custom stack.",[166,1392,1393,1396],{},[98,1394,1395],{},"Pro (€159 one-time, lifetime updates):"," agent-driven setup, instant delivery via GitHub, semantic opt-in updates.",[11,1398,1399],{},"Honest trade-off: Pro is faster; Lite is more flexible if you don't use Nuxt or want to understand every wire yourself.",[15,1401,1403],{"id":1402},"common-pitfalls-boiledplate-prevents","Common Pitfalls BoiledPlate Prevents",[163,1405,1406,1412,1418,1424,1430],{},[166,1407,1408,1411],{},[98,1409,1410],{},"Retry loops that double-charge"," — idempotency keys make repeated events safe.",[166,1413,1414,1417],{},[98,1415,1416],{},"RLS policies that expose other tenants"," — generated policies carry the tenant ID.",[166,1419,1420,1423],{},[98,1421,1422],{},"Canonical URL drift"," — prerendering plus verification, born from real pain.",[166,1425,1426,1429],{},[98,1427,1428],{},"JSON-LD hydration crashes"," — documented Nuxt SSR source-order patterns.",[166,1431,1432,1435],{},[98,1433,1434],{},"Peer dependency hell"," — Stripe, Supabase, and Resend versions pinned and tested together.",[15,1437,1439],{"id":1438},"real-debugging-youll-actually-hit","Real Debugging You'll Actually Hit",[11,1441,1442,1445,1446,1450],{},[23,1443,1444],{},"\"Webhook arrived but didn't update my database.\""," Run the signature-verification checklist; the ",[48,1447,1449],{"href":725,"rel":1448},[52],"GitHub-invite webhook post"," explains which failures should throw and which should never.",[11,1452,1453,1456],{},[23,1454,1455],{},"\"RLS is blocking my own query.\""," Test policies against a non-production role; check that your policy references the right claim.",[11,1458,1459,1462],{},[23,1460,1461],{},"\"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,1464,1466],{"id":1465},"why-agent-driven-setup-changes-the-game","Why Agent-Driven Setup Changes the Game",[11,1468,1469],{},"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,1471,1473],{"id":1472},"when-boiledplate-isnt-the-right-fit","When BoiledPlate Isn't the Right Fit",[11,1475,1476],{},"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,1478,1480],{"id":1479},"the-philosophy","The Philosophy",[11,1482,1483],{},"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,1485,1487],{"id":1486},"getting-started","Getting Started",[163,1489,1490,1496,1507],{},[166,1491,1492,1495],{},[98,1493,1494],{},"30 minutes:"," skim the conventions and decide if agent-driven setup appeals to you.",[166,1497,1498,1501,1502,1506],{},[98,1499,1500],{},"2 hours:"," ",[48,1503,1505],{"href":295,"rel":1504},[52],"clone Lite",", wire one service by hand, and feel where the weeks go.",[166,1508,1509,1501,1512,1516],{},[98,1510,1511],{},"Ready to ship:",[48,1513,1515],{"href":76,"rel":1514},[52],"get Pro",", run the interview, deploy, and write your first real feature instead of your fortieth webhook handler.",[11,1518,1519,1520,1524,1525,1528],{},"For deeper reading, the ",[48,1521,1523],{"href":269,"rel":1522},[52],"BoiledPlate blog"," documents each edge case with the real bug and the real fix — and Stripe's own ",[48,1526,1080],{"href":1078,"rel":1527},[52]," are essential even when a starter handles the hard parts for you.",{"title":364,"searchDepth":365,"depth":365,"links":1530},[1531,1532,1533,1534,1535,1536,1537,1538,1539,1540,1541,1542,1543,1544,1545,1546,1547,1548],{"id":1131,"depth":368,"text":1132},{"id":1146,"depth":368,"text":1147},{"id":1166,"depth":368,"text":1167},{"id":1203,"depth":368,"text":1204},{"id":1223,"depth":368,"text":1224},{"id":1246,"depth":368,"text":1247},{"id":1256,"depth":368,"text":1257},{"id":1269,"depth":368,"text":1270},{"id":1309,"depth":368,"text":1310},{"id":1326,"depth":368,"text":1327},{"id":1333,"depth":368,"text":1334},{"id":1376,"depth":368,"text":1377},{"id":1402,"depth":368,"text":1403},{"id":1438,"depth":368,"text":1439},{"id":1465,"depth":368,"text":1466},{"id":1472,"depth":368,"text":1473},{"id":1479,"depth":368,"text":1480},{"id":1486,"depth":368,"text":1487},"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":1123,"description":1550},"blog\u002Fshipfast-tutorial",[809,1556,1557,1558],"tutorial","startup-boilerplate","stripe-integration","tDZYFFDL49lAdCZJNAP9-tOsrJ4PCoW-berk9aTYAg0",1789347118413]