[{"data":1,"prerenderedAt":1105},["ShallowReactive",2],{"blog-shipfast-agency-vs-self-serve-automation":3,"related-shipfast-agency-vs-self-serve-automation":331},{"id":4,"title":5,"author":6,"body":7,"category":6,"date":316,"description":317,"draft":318,"extension":319,"image":6,"meta":320,"navigation":321,"path":322,"seo":323,"stem":324,"tags":325,"__hash__":330},"blog\u002Fblog\u002Fshipfast-agency-vs-self-serve-automation.md","ShipFast Agency vs Self-Serve Automation",null,{"type":8,"value":9,"toc":299},"minimark",[10,14,17,22,25,28,31,35,38,49,52,61,65,73,76,79,83,86,115,124,128,131,134,145,154,158,161,187,196,200,203,206,209,213,216,219,223,226,229,233,241,256,260,263,267,287,296],[11,12,13],"p",{},"Search \"shipfast agency\" and you'll find a familiar pitch: AI-powered development shops that promise to build your app \"10x faster and cheaper,\" in weeks not months. It's an appealing model when you're staring at an empty repo. But there's a quieter alternative that changes the math entirely — self-serve automation that hands you the codebase, provisions your services, and never sends an invoice again after the first one.",[11,15,16],{},"This is a comparison between two ways of getting to production: hiring an agency to build your SaaS, or using an agent-native starter that wires the plumbing for you. Both have their place. Here's where each one actually wins.",[18,19,21],"h2",{"id":20},"the-agency-model-what-it-actually-costs","The Agency Model: What It Actually Costs",[11,23,24],{},"Agencies sell calendar time. When someone quotes \"four weeks to launch,\" they're selling four weeks of their availability, not four weeks of your product shipping. The gap between those two things is filled with communication overhead: kickoff calls, scope documents, Slack threads waiting on replies, and the inevitable handoff friction when the people who built it move on to the next client.",[11,26,27],{},"The \"10x faster\" claim is real in one sense — agencies aren't rebuilding the wheel for each client, so they move quickly through the common parts. But speed through boilerplate doesn't mean they've solved the hard parts. The billing edge cases, the refund flows, the consent laws: those still get handwaved, because they're not sexy enough to feature in a portfolio.",[11,29,30],{},"Then there's the ownership question. A retainer at $5,000–$15,000 a month buys you an app you don't fully understand, built by people who leave. Compare that to internal tooling you own forever, and the math shifts fast.",[18,32,34],{"id":33},"the-plumbing-problem-agencies-dont-solve","The Plumbing Problem Agencies Don't Solve",[11,36,37],{},"Agencies build your app. You inherit the maintenance debt.",[11,39,40,41,48],{},"The work that actually eats launch timelines isn't the framework choice — ",[42,43,47],"a",{"href":44,"rel":45},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fhow-to-ship-saas-fast",[46],"nofollow","as we've argued before, the stack picks itself",". It's the wiring between services: webhook idempotency, row-level security design, refund handling, subscription state management. None of it is clever. All of it is endless and slightly different every time.",[11,50,51],{},"Here's the trap: your agency ships it, and six months later your next engineer spends weeks re-learning the billing logic because nobody documented why the webhook handler retries the way it does. The knowledge left with the contractor.",[11,53,54,55,60],{},"That's the problem an ",[42,56,59],{"href":57,"rel":58},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fconventions-for-ai-coding-agents",[46],"AGENTS.md contract"," is designed to solve. Instead of tribal knowledge, you get one documented way to access data and handle secrets — so the logic is repeatable, not mysterious, and the next agent (or human) doesn't have to reverse-engineer it.",[18,62,64],{"id":63},"boiledplate-the-anti-agency-stack","BoiledPlate: The Anti-Agency Stack",[11,66,67,72],{},[42,68,71],{"href":69,"rel":70},"https:\u002F\u002Fboiledplate.ai",[46],"BoiledPlate"," inverts the agency relationship. You keep the code, the database, and the customer relationship. There's no black-box handoff, no \"the agency built it and then vanished\" moment.",[11,74,75],{},"The setup is agent-driven: your coding agent interviews you — name, languages, theme, billing model — then reshapes the codebase with deterministic patches. Because those patches are deterministic, you can audit and modify what changed. Nothing happens that you can't inspect.",[11,77,78],{},"The pricing model is the clearest difference. It's €159 one-time with lifetime updates, versus an ongoing retainer that never stops. At six months of retainer spend, you'd have paid for a senior developer several times over.",[18,80,82],{"id":81},"why-these-specific-tools","Why These Specific Tools",[11,84,85],{},"The stack is Nuxt, Supabase, and Stripe — and each choice avoids a specific \"we picked wrong at month three\" regret.",[87,88,89,97,109],"ul",{},[90,91,92,96],"li",{},[93,94,95],"strong",{},"Nuxt"," gives you a typed, full-stack framework with conventions agents can follow reliably.",[90,98,99,102,103,108],{},[93,100,101],{},"Supabase"," enforces ",[42,104,107],{"href":105,"rel":106},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fpostgres\u002Frow-level-security",[46],"row-level security at query time",", which means your database doesn't trust the frontend or even the webhook for authorization — it's enforced where it can't be bypassed.",[90,110,111,114],{},[93,112,113],{},"Stripe"," is the source of truth for billing state. Your frontend success page never decides whether someone paid.",[11,116,117,118,123],{},"That last point matters more than it sounds. ",[42,119,122],{"href":120,"rel":121},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-webhooks-source-of-truth",[46],"Your checkout success page should not touch your billing state"," — because a user closing the tab, a flaky network, or a double-submit shouldn't corrupt what a customer is entitled to. Stripe's webhooks decide; your app reacts.",[18,125,127],{"id":126},"the-real-speed-bottleneck-wiring-not-writing","The Real Speed Bottleneck: Wiring, Not Writing",[11,129,130],{},"Agencies sell design and features because those are visible. Plumbing is invisible work — you only notice it when it breaks.",[11,132,133],{},"BoiledPlate pre-wires the invisible parts:",[87,135,136,139,142],{},[90,137,138],{},"Stripe webhooks with signature verification and idempotency, so replayed events don't double-charge or double-provision.",[90,140,141],{},"Google sign-in on top of Supabase auth as a single decision in the setup interview, not three weeks of OAuth debugging.",[90,143,144],{},"Transactional email through Resend, already integrated — no separate vendor hunt, no SMTP troubleshooting weekend.",[11,146,147,148,153],{},"This is the leverage. The framework was never the bottleneck; ",[42,149,152],{"href":150,"rel":151},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-supabase-stripe-saas-boilerplate",[46],"wiring four services into something trustworthy"," was.",[18,155,157],{"id":156},"billing-edge-cases-agencies-gloss-over","Billing Edge Cases Agencies Gloss Over",[11,159,160],{},"This is where the gap between \"built your app\" and \"shipped a real product\" shows.",[87,162,163,175,181],{},[90,164,165,168,169,174],{},[93,166,167],{},"EU consent law."," German withdrawal-right waivers have to be encoded into the pay button itself. ",[42,170,173],{"href":171,"rel":172},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-checkout-consent-collection-german-withdrawal-waiver",[46],"BoiledPlate ships that consent collection","; most agencies hand you a Stripe SDK and wish you luck.",[90,176,177,180],{},[93,178,179],{},"Multi-plan subscriptions."," What happens when a customer downgrades mid-month? Proration, entitlement changes, the webhook that keeps your database in sync — these need to be handled, not discovered in production.",[90,182,183,186],{},[93,184,185],{},"Refund idempotency."," Stripe retries. Your webhook handler must survive duplicate calls without issuing duplicate side effects.",[11,188,189,190,195],{},"That last one is subtle enough that we wrote a whole post about it: ",[42,191,194],{"href":192,"rel":193},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-github-invite-is-the-product-building-a-stripe-webhook-where-delivery-throws",[46],"the GitHub invite is the product, a webhook where some failures throw and some never do",". Getting the retry semantics wrong means either lost deliveries or duplicated ones.",[18,197,199],{"id":198},"ai-agents-and-consistency-the-agentsmd-advantage","AI Agents and Consistency: The AGENTS.md Advantage",[11,201,202],{},"Here's a distinction that matters as coding agents become the default. An agency might use Claude once, internally, to move faster. BoiledPlate expects agents to reshape the codebase iteratively — yours, on an ongoing basis.",[11,204,205],{},"That only works if the agent doesn't drift. Deterministic patches beat manual code review for agent output because they're repeatable and auditable. And the AGENTS.md contract gives every agent one documented way to access data, so the next session — or the next agent entirely — doesn't hallucinate your schema or invent a second pattern for the same job.",[11,207,208],{},"This is what unlocks genuine speed: agents that already know your conventions instead of guessing them.",[18,210,212],{"id":211},"deployment-and-delivery-mechanics","Deployment and Delivery Mechanics",[11,214,215],{},"Agencies deliver over Slack and staging links. BoiledPlate delivers over GitHub — instant invite, instant repo. There's no \"wait for the agency to flip the switch\" moment.",[11,217,218],{},"In a single setup session, your agent provisions Stripe products and webhooks, a Supabase database with RLS, and Google sign-in. Production-ready in minutes, not weeks of staging validation.",[18,220,222],{"id":221},"what-agencies-do-better-and-when-to-use-them","What Agencies Do Better (and When to Use Them)",[11,224,225],{},"Being honest about trade-offs: agencies still beat automation at real design and UX work, at complex domain-specific business logic, and any time you need a human to sit with your team and learn edge cases only your industry has.",[11,227,228],{},"If your differentiation is a nuanced interface or a workflow no boilerplate anticipates, a good agency earns its fee. The point isn't that agencies are bad — it's that they're the wrong tool for the plumbing. Use BoiledPlate for the plumbing, agencies for the polish.",[18,230,232],{"id":231},"typescript-seo-and-i18n-as-force-multipliers","TypeScript, SEO, and i18n as Force Multipliers",[11,234,235,236,240],{},"Small things compound. End-to-end TypeScript strict mode catches integration bugs before they reach production. SEO is baked in — JSON-LD, canonical URLs, ",[237,238,239],"code",{},"og:url"," — the details agencies frequently ship broken. A prerendered Markdown blog means nobody has to litigate CMS trade-offs. And four languages ship from day one, so i18n isn't a retrofit later.",[11,242,243,244,249,250,255],{},"We learned some of these the hard way, which is why they're solved now: ",[42,245,248],{"href":246,"rel":247},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Four-blog-canonically-pointed-at-localhost",[46],"our blog once told Google its canonical URL was localhost:3000",", and ",[42,251,254],{"href":252,"rel":253},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fthe-page-that-returned-200-on-the-server-and-500-in-the-browser-a-json-ld-tempor",[46],"a JSON-LD source-order bug returned 200 from curl but 500 in Chrome",". Owning the codebase means you can find and fix these fast, instead of filing a ticket and waiting.",[18,257,259],{"id":258},"the-cost-comparison-boiledplate-vs-retainer-hell","The Cost Comparison: BoiledPlate vs. Retainer Hell",[11,261,262],{},"The numbers are stark. €159 one-time with lifetime updates versus $5,000–$15,000 a month. At six months you've saved the cost of a senior developer. You own the code, so you can hire junior devs to maintain it. And because updates arrive as deterministic patches, they don't silently break your customizations.",[18,264,266],{"id":265},"how-to-choose","How to Choose",[87,268,269,275,281],{},[90,270,271,274],{},[93,272,273],{},"BoiledPlate if"," you have a clear idea, solid dev skills, and want shipping speed over hand-holding.",[90,276,277,280],{},[93,278,279],{},"Agencies if"," you need design collaboration or domain expertise you genuinely don't have in-house.",[90,282,283,286],{},[93,284,285],{},"The hybrid:"," use BoiledPlate as the foundation, hire an agency for the UX layer on top. Three weeks of plumbing you didn't write, plus two weeks of agency design, gets you to market faster than either alone.",[11,288,289,290,295],{},"The future favors this split. As ",[42,291,294],{"href":292,"rel":293},"https:\u002F\u002Fwww.anthropic.com\u002Fengineering\u002Fclaude-code-best-practices",[46],"Anthropic's own guidance on agentic coding"," suggests, the winning pattern is humans making decisions and agents executing deterministically. BoiledPlate is built for exactly that — an agent-native starter Claude can reshape iteratively, so your competitive edge is shipping faster because your agent doesn't hallucinate your codebase.",[11,297,298],{},"That's the real answer to the \"shipfast agency\" question. You don't have to choose between fast and owned. You can have both.",{"title":300,"searchDepth":301,"depth":301,"links":302},"",3,[303,305,306,307,308,309,310,311,312,313,314,315],{"id":20,"depth":304,"text":21},2,{"id":33,"depth":304,"text":34},{"id":63,"depth":304,"text":64},{"id":81,"depth":304,"text":82},{"id":126,"depth":304,"text":127},{"id":156,"depth":304,"text":157},{"id":198,"depth":304,"text":199},{"id":211,"depth":304,"text":212},{"id":221,"depth":304,"text":222},{"id":231,"depth":304,"text":232},{"id":258,"depth":304,"text":259},{"id":265,"depth":304,"text":266},"2026-08-05","Compare hiring a ShipFast agency to build your SaaS vs using agent-native starters. Understand true costs, ownership, and where each approach actually wins.",false,"md",{},true,"\u002Fblog\u002Fshipfast-agency-vs-self-serve-automation",{"title":5,"description":317},"blog\u002Fshipfast-agency-vs-self-serve-automation",[326,327,328,329],"SaaS development","agency vs DIY","automation","product launch","foDbuZy7q1MReuB0PX05tqk6N4oy26SIaY6fzYUM0Uo",[332,654,718],{"id":333,"title":334,"author":6,"body":335,"category":6,"date":642,"description":643,"draft":318,"extension":319,"image":6,"meta":644,"navigation":321,"path":645,"seo":646,"stem":647,"tags":648,"__hash__":653},"blog\u002Fblog\u002Fshipfast-affiliate-program-review.md","ShipFast Affiliate Program: Honest Review vs BoiledPlate",{"type":8,"value":336,"toc":624},[337,344,348,356,359,363,369,374,379,387,391,394,398,409,422,425,429,440,449,453,460,472,476,489,492,499,505,507,515,518,522,538,542,545,549,555,567,573,577,586,592,596,603,607,610],[11,338,339,340,343],{},"If you searched for \"shipfast affiliate,\" you're probably weighing whether ShipFast is worth promoting — or worth buying in the first place. Both questions deserve an honest answer, and both come back to the same overlooked truth: the framework you pick is never the slow part. Wiring services together is. This is a head-to-head between ShipFast and ",[42,341,71],{"href":69,"rel":342},[46],", two SaaS starter kits with very different philosophies, plus a straight look at the affiliate math nobody wants to spell out.",[18,345,347],{"id":346},"the-saas-starter-problem-nobody-talks-about","The SaaS Starter Problem Nobody Talks About",[11,349,350,351,355],{},"Ask ten founders how to ship fast and you get ten stack arguments — Next vs Nuxt, Prisma vs a hosted DB, Stripe vs Paddle. Pick whatever you already know and that debate is over in an afternoon. As we've ",[42,352,354],{"href":44,"rel":353},[46],"written before",", the framework is not what slows you down.",[11,357,358],{},"What slows you down is the plumbing between the pieces: webhook idempotency, row-level security, refunds, EU consent flows. ShipFast positions itself as a \"launch in days\" boilerplate that hands you a working snapshot. BoiledPlate takes a different route: your coding agent interviews you, then provisions the services and reshapes the codebase to your answers. One gives you a template; the other automates the setup itself.",[18,360,362],{"id":361},"head-to-head-stack-and-trade-offs","Head-to-Head: Stack and Trade-offs",[11,364,365,368],{},[93,366,367],{},"ShipFast"," is Next.js on the JavaScript side, typically paired with MongoDB or Postgres and Stripe. If you live in the Next.js ecosystem and deploy to Vercel by reflex, that familiarity is real value.",[11,370,371,373],{},[93,372,71],{}," is Nuxt 4 + Supabase + Stripe + Resend. The Supabase choice changes the entire auth conversation, because security moves into the database via row-level security (RLS) rather than living only in application code.",[375,376,378],"h3",{"id":377},"rls-vs-application-layer-guards","RLS vs. application-layer guards",[11,380,381,382,386],{},"Application-layer guards work until someone adds a new endpoint and forgets the check. RLS is enforced at query time — the database refuses to return rows the caller shouldn't see, no matter which route reaches for them. It's the difference between a rule you must remember and a rule the system enforces. As our ",[42,383,385],{"href":150,"rel":384},[46],"wiring breakdown"," puts it: auth is the fast part, RLS is the part you forget.",[375,388,390],{"id":389},"i18n-and-email","i18n and email",[11,392,393],{},"BoiledPlate ships four languages from day one, so localization isn't a retrofit. Most Next.js boilerplates treat i18n as something you bolt on later. On email, BoiledPlate integrates Resend with transactional templates included; ShipFast generally assumes you'll wire your own provider.",[18,395,397],{"id":396},"the-real-plumbing-webhook-architecture","The Real Plumbing: Webhook Architecture",[11,399,400,401,404,405,408],{},"\"Launch in days\" quietly skips the hardest part: making Stripe webhooks trustworthy. Stripe retries deliveries. Your endpoint will get the same event twice. If your handler isn't ",[93,402,403],{},"idempotent",", a retried ",[237,406,407],{},"checkout.session.completed"," can grant access twice, email twice, or double-count revenue.",[11,410,411,412,416,417,421],{},"BoiledPlate is built around signature-verified, idempotent webhooks — the ",[42,413,415],{"href":120,"rel":414},[46],"source of truth"," for billing state lives server-side, not on a client success page a user might never reach. We wrote a whole post on ",[42,418,420],{"href":192,"rel":419},[46],"a webhook where some failures must throw and some never should",", because getting retry semantics wrong is how you either lose deliveries or duplicate them.",[11,423,424],{},"Refund flows are the same story. A refund is another event that can arrive more than once; without idempotency you risk double-reversing a subscription. This is exactly the kind of edge case a snapshot boilerplate leaves as an exercise for you.",[18,426,428],{"id":427},"billing-edge-cases-that-sink-startups","Billing Edge Cases That Sink Startups",[11,430,431,432,439],{},"If you sell into the EU, you hit consent law fast. German withdrawal-right waivers, for instance, must be encoded into the checkout itself — we documented ",[42,433,435,436],{"href":171,"rel":434},[46],"how to do it with Stripe's ",[237,437,438],{},"consent_collection",". Miss it and you've built a legal problem into your pay button.",[11,441,442,443,448],{},"Multi-plan subscriptions compound every one of these edges: proration, upgrades, downgrades, and refunds all flow through the same webhook pipeline. The ",[42,444,447],{"href":445,"rel":446},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fstripe-subscriptions-nuxt-supabase",[46],"five decisions behind Stripe subscriptions"," on a Nuxt + Supabase stack aren't unique to Nuxt — they're just usually undocumented.",[18,450,452],{"id":451},"agent-ready-code-vs-manual-customization","Agent-Ready Code vs. Manual Customization",[11,454,455,456,459],{},"Here's where the two products genuinely diverge. BoiledPlate ships an ",[237,457,458],{},"AGENTS.md"," contract: one documented way to do data access, where secrets live, and how things are named. That sounds minor until a coding agent touches your codebase and invents a second pattern in a corner you don't review.",[11,461,462,463,466,467,471],{},"BoiledPlate's setup runs on ",[93,464,465],{},"deterministic patches"," — repeatable, reviewable changes that apply your interview answers to the codebase. It's a scaling model for agent work, not a one-time scaffold. We explained the reasoning in ",[42,468,470],{"href":57,"rel":469},[46],"write your conventions for the agent, not the next hire",". ShipFast's structure is clean, but it doesn't ship an explicit agent contract, so consistency depends on prompting discipline — and agent drift is what costs teams weeks, not code quality.",[18,473,475],{"id":474},"the-affiliate-conversation-commission-models-and-reality","The Affiliate Conversation: Commission Models and Reality",[11,477,478,479,482,483,488],{},"Now the keyword question. ShipFast runs a public affiliate program. Their materials and documentation reference ",[93,480,481],{},"30% per sale as a recurring share"," — you earn a cut for as long as the referred customer keeps paying — with a cookie window commonly cited around 90 days. Some ShipFast promotional pages have also advertised higher first-touch rates. Because the exact terms shift and are set by ShipFast, verify the current numbers on their ",[42,484,487],{"href":485,"rel":486},"https:\u002F\u002Fshipfa.st\u002Faffiliates",[46],"official affiliate page"," before you commit.",[11,490,491],{},"The math matters. On a recurring subscription, 30% of a monthly plan compounds if customers stick around — but it also depends entirely on retention. If churn is high, \"recurring\" commission looks a lot like one-off.",[11,493,494,495,498],{},"BoiledPlate is priced differently: ",[93,496,497],{},"€159 one-time, lifetime updates, instant delivery via GitHub."," A one-time product means a simpler affiliate conversation — no retention gamble, no dependence on a customer's subscription surviving month six.",[11,500,501,504],{},[93,502,503],{},"Who benefits from each model?"," A high-volume promoter with an audience that resubscribes will prefer recurring commission. A builder with a small, technical audience often does better recommending a one-time product they can vouch for without tracking whether the buyer stayed subscribed.",[18,506,212],{"id":211},[11,508,509,510,514],{},"ShipFast is a self-hosted deploy path — clone, configure, push to Vercel. BoiledPlate delivers the product itself through a Stripe webhook: buy once, get an instant GitHub invite. The ",[42,511,513],{"href":192,"rel":512},[46],"GitHub invite is literally the product",", which is why its delivery webhook is engineered to never silently fail.",[11,516,517],{},"On first deploy, both get you a running app quickly. The difference is what's already wired: BoiledPlate boots with multi-language, RLS-secured, prerendered defaults, so the plumbing is done before you write your first feature.",[18,519,521],{"id":520},"seo-and-blog-infrastructure","SEO and Blog Infrastructure",[11,523,524,525,527,528,532,533,537],{},"BoiledPlate ships JSON-LD structured data, ",[237,526,239],{}," canonicals, and a prerendered Markdown blog by default — the stuff most starters skip and you retrofit at 2 a.m. We know the failure modes intimately: we've written up ",[42,529,531],{"href":246,"rel":530},[46],"a blog that told Google its canonical was localhost:3000"," and ",[42,534,536],{"href":252,"rel":535},[46],"a JSON-LD bug that returned 200 from curl and 500 in Chrome",". Those posts exist because we hit the bugs and fixed them in the product.",[18,539,541],{"id":540},"auth-typescript-and-multilingual-sessions","Auth, TypeScript, and Multilingual Sessions",[11,543,544],{},"Both starters offer Google sign-in. The distinction is enforcement: BoiledPlate leans on Supabase RLS, so a missing check in a route handler doesn't leak data. Sessions work across the four bundled languages out of the box, and the whole codebase runs in TypeScript strict mode — type safety end to end, not \"types added later.\"",[18,546,548],{"id":547},"honest-trade-offs-when-each-starter-wins","Honest Trade-offs: When Each Starter Wins",[11,550,551,554],{},[93,552,553],{},"Choose ShipFast if:"," you're committed to the Next.js ecosystem, you're comfortable owning your service wiring, and you're not routing work through coding agents.",[11,556,557,560,561,566],{},[93,558,559],{},"Choose BoiledPlate if:"," you want RLS-first security, you're comfortable in Nuxt, you build with Claude and want ",[42,562,565],{"href":563,"rel":564},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fnuxt-saas-boilerplate-for-ai-agents",[46],"agent-ready conventions",", or you need multilingual defaults on day one.",[11,568,569,572],{},[93,570,571],{},"Skip both"," if your product is genuinely unusual — a non-standard billing model or data layer — where a starter's assumptions fight you more than they help.",[18,574,576],{"id":575},"the-cost-of-free-vs-paid","The Cost of \"Free\" vs. Paid",[11,578,579,580,585],{},"There's also ",[42,581,584],{"href":582,"rel":583},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Ffree-nuxt-supabase-saas-boilerplate",[46],"BoiledPlate Lite"," — the same app, MIT-licensed and free, minus the AI tooling that makes the paid version set itself up. Clone it, wire it by hand, ship. It makes sense when you have the time and want zero cost.",[11,587,588,591],{},[93,589,590],{},"BoiledPlate Pro (€159)"," buys back that wiring time: agent-driven provisioning, deterministic patches, lifetime updates, and instant GitHub delivery. Against ShipFast's tiers (publicly listed around the $199–$349 range depending on plan), the ROI question is the same for both — how many weeks of your own plumbing does the price replace?",[18,593,595],{"id":594},"the-case-for-deterministic-patches-over-boilerplate","The Case for Deterministic Patches Over Boilerplate",[11,597,598,599,602],{},"Here's the quiet innovation. Traditional starters are a one-time snapshot: the day you clone, you fork away from upstream forever. BoiledPlate ships semantic, agent-readable release notes and ",[93,600,601],{},"opt-in updates to customized code"," — so you can stay current with Nuxt and Supabase without merge hell or manual rewrites. That's the difference between buying a boilerplate and buying a maintained foundation.",[18,604,606],{"id":605},"conclusion-the-plumbing-philosophy","Conclusion: The Plumbing Philosophy",[11,608,609],{},"Your stack choice isn't the slow part — the plumbing is. ShipFast prioritizes the Next.js ecosystem, fast initial setup, and a large community. BoiledPlate prioritizes agent consistency, RLS-enforced security, multilingual defaults, and agent-driven provisioning that runs the setup for you.",[11,611,612,613,617,618,623],{},"On the affiliate question specifically: ShipFast's recurring model rewards volume promoters who trust retention; BoiledPlate's one-time model rewards builders who'd rather recommend something with a clean, single transaction. Either way, always confirm current terms on the source. And if you want to see what \"the plumbing, already done\" actually looks like, ",[42,614,616],{"href":69,"rel":615},[46],"start here"," or read more on the ",[42,619,622],{"href":620,"rel":621},"https:\u002F\u002Fboiledplate.ai\u002Fblog",[46],"blog",".",{"title":300,"searchDepth":301,"depth":301,"links":625},[626,627,631,632,633,634,635,636,637,638,639,640,641],{"id":346,"depth":304,"text":347},{"id":361,"depth":304,"text":362,"children":628},[629,630],{"id":377,"depth":301,"text":378},{"id":389,"depth":301,"text":390},{"id":396,"depth":304,"text":397},{"id":427,"depth":304,"text":428},{"id":451,"depth":304,"text":452},{"id":474,"depth":304,"text":475},{"id":211,"depth":304,"text":212},{"id":520,"depth":304,"text":521},{"id":540,"depth":304,"text":541},{"id":547,"depth":304,"text":548},{"id":575,"depth":304,"text":576},{"id":594,"depth":304,"text":595},{"id":605,"depth":304,"text":606},"2026-08-04","Compare ShipFast affiliate opportunity with BoiledPlate. Learn the real affiliate math, stack differences, and which SaaS starter kit truly ships faster.",{},"\u002Fblog\u002Fshipfast-affiliate-program-review",{"title":334,"description":643},"blog\u002Fshipfast-affiliate-program-review",[649,650,651,652],"affiliate marketing","saas","shipfast","boilerplate","ba5CKVjkZToypl6G9dabr_-GfiPSEmUlQjAODCKSUIs",{"id":655,"title":656,"author":6,"body":657,"category":6,"date":708,"description":709,"draft":318,"extension":319,"image":6,"meta":710,"navigation":321,"path":711,"seo":712,"stem":713,"tags":714,"__hash__":717},"blog\u002Fblog\u002Fmarc-shipfast-building-saas-empire.md","Marc ShipFast: Building a $90K\u002FMonth SaaS Empire",{"type":8,"value":658,"toc":705},[659,664,667,673,676,680,695,702],[660,661,663],"h1",{"id":662},"review-results","Review Results",[11,665,666],{},"The article is well-written in English with valid markdown heading hierarchy. However, I found one issue:",[11,668,669,670,672],{},"The internal link to \"BoiledPlate Lite\" at the end (",[237,671,582],{},") is not a clickable URL in the text. It should be formatted as a markdown link. Here is the corrected final section:",[674,675],"hr",{},[375,677,679],{"id":678},"where-to-start-choosing-between-boilerplate-approaches","Where to Start: Choosing Between Boilerplate Approaches",[11,681,682,683,686,687,690,691,694],{},"Decide on three axes: ",[93,684,685],{},"stack preference"," (Next.js vs. Nuxt), ",[93,688,689],{},"team size"," (do you want provisioning done for you?), and ",[93,692,693],{},"agent involvement"," (are you building with Claude?).",[11,696,697,698,701],{},"If you want to try before you buy, ",[42,699,584],{"href":582,"rel":700},[46]," is free and MIT-licensed — clone it and wire it by hand. Pro adds the agent-driven setup, instant GitHub delivery, and lifetime updates.",[11,703,704],{},"Marc Lou proved the market. The question now isn't whether a boilerplate is worth it — it's whether you want to keep wiring plumbing yourself, or let an agent do it while you build the product.",{"title":300,"searchDepth":301,"depth":301,"links":706},[707],{"id":678,"depth":301,"text":679},"2026-08-03","Discover how Marc Lou turned ShipFast into a $90K\u002Fmonth SaaS success. Learn his boilerplate strategy, portfolio playbook, and key insights.",{},"\u002Fblog\u002Fmarc-shipfast-building-saas-empire",{"title":656,"description":709},"blog\u002Fmarc-shipfast-building-saas-empire",[651,650,715,716],"indie-developers","next.js-boilerplate","3KdsN0qui3xYvYoskkEJMoSyxDT8ULfilGPiH0pOAaE",{"id":719,"title":720,"author":6,"body":721,"category":6,"date":1094,"description":1095,"draft":318,"extension":319,"image":6,"meta":1096,"navigation":321,"path":1097,"seo":1098,"stem":1099,"tags":1100,"__hash__":1104},"blog\u002Fblog\u002Fmarc-lou-shipfast-github-saas-starter.md","Marc Lou ShipFast GitHub: SaaS Starter Evolution",{"type":8,"value":722,"toc":1077},[723,726,730,733,736,743,747,750,758,766,770,775,780,786,789,793,796,803,806,810,813,821,829,833,836,867,870,874,877,880,884,892,895,899,907,933,936,940,943,972,975,979,990,993,997,1008,1011,1015,1021,1027,1031,1037,1043,1049,1053,1056,1064],[11,724,725],{},"If you searched for \"marc lou shipfast github,\" you're likely mapping the SaaS starter-kit landscape: what ShipFast solved, where it lives on GitHub, and what comes next. This guide covers that lineage and explains why the space is moving toward AI-native starters that provision services instead of handing you a box of parts.",[18,727,729],{"id":728},"what-marc-lou-built-and-why-it-matters","What Marc Lou Built (And Why It Matters)",[11,731,732],{},"Marc Lou popularized the modern SaaS boilerplate with ShipFast, a private GitHub repository you clone after purchase. It bundles payments, a database, login, and battle-tested UI so founders skip weeks of setup. The pitch worked: Marc publicly documented making $250K+ in five months selling it, and the template became a reference point for the whole \"launch in days, not weeks\" category.",[11,734,735],{},"ShipFast's insight was correct and durable: the framework choice is not what slows you down. The wiring between services is. But ShipFast is a manual template. You clone it, read the README, and configure everything by hand.",[11,737,738,739,742],{},"The next generation moves that setup work onto a coding agent. That's the idea behind ",[42,740,71],{"href":69,"rel":741},[46],": an AI-native Nuxt + Supabase starter whose setup runs itself. Your agent interviews you, then provisions Stripe products and webhooks, a Supabase database with row-level security, and Google sign-in in a single session.",[18,744,746],{"id":745},"the-real-cost-of-saas-setup-that-nobody-talks-about","The Real Cost of SaaS Setup (That Nobody Talks About)",[11,748,749],{},"Ask ten founders how to ship fast and you get ten stack arguments — Next vs Nuxt, Postgres vs a hosted DB, Stripe vs Paddle. Pick whatever you already know and that debate is over in an afternoon.",[11,751,752,753,757],{},"What actually eats your launch is the plumbing between the pieces: ",[42,754,756],{"href":44,"rel":755},[46],"webhook idempotency, RLS, refunds, and EU consent",". None of it is clever. It's endless, slightly different every time, and invisible until it breaks in production.",[11,759,760,761,765],{},"Agents change the equation. Instead of you wiring four services by hand, the agent provisions them while you answer questions about your product. The slow part — ",[42,762,764],{"href":563,"rel":763},[46],"bolting the parts to each other"," — moves off your plate.",[18,767,769],{"id":768},"boiledplate-vs-shipfast-vs-building-from-scratch","BoiledPlate vs. ShipFast vs. Building from Scratch",[11,771,772,774],{},[93,773,367],{}," is the manual template that proved the market. You get a complete repo and configure it yourself.",[11,776,777,779],{},[93,778,71],{}," is the agent-driven evolution. It ships an AGENTS.md contract and applies deterministic patches — automated, repeatable code changes that reshape the codebase to your answers.",[11,781,782,785],{},[93,783,784],{},"Building from scratch"," is the DIY trap. \"Just use these libraries\" still leaves you wiring Stripe webhooks against your database, writing RLS policies, and handling refund flows by hand.",[11,787,788],{},"Each approach trades time for control. Scratch gives maximum flexibility and costs the most weeks. ShipFast gives a head start with manual setup. BoiledPlate compresses the setup itself into a session.",[18,790,792],{"id":791},"how-boiledplate-actually-sets-itself-up","How BoiledPlate Actually Sets Itself Up",[11,794,795],{},"The first session is an interview. Your agent asks for the product name, languages, theme, and billing model — then reshapes the entire codebase with deterministic patches.",[11,797,798,799,623],{},"Deterministic patches are not freehand code generation. They're repeatable transformations, so the same answers produce the same result. That reliability comes from the AGENTS.md contract: one documented way to do data access and secrets, so the agent stays consistent instead of ",[42,800,802],{"href":57,"rel":801},[46],"inventing a new pattern every file",[11,804,805],{},"By the end of a session, Supabase RLS, Stripe products, and Google sign-in are provisioned — not stubbed for you to finish later.",[18,807,809],{"id":808},"webhook-architecture-that-actually-works","Webhook Architecture That Actually Works",[11,811,812],{},"\"It worked in testing\" is where most billing implementations die. Stripe retries webhooks. They arrive twice. They arrive out of order. If your handler isn't idempotent, a repeated call duplicates side effects.",[11,814,815,816,820],{},"The correct model treats ",[42,817,819],{"href":120,"rel":818},[46],"Stripe webhooks as the source of truth"," for billing state — not the client-side success page a user might never reach. BoiledPlate builds on this: signature-verified, idempotent webhooks that survive retries and race conditions.",[11,822,823,824,828],{},"Delivery is subtle. In BoiledPlate's own product webhook, ",[42,825,827],{"href":192,"rel":826},[46],"some failures must throw and some must never do"," — because a throw tells Stripe to retry, and retrying the wrong step doubles the damage.",[18,830,832],{"id":831},"billing-edge-cases-that-ship-ready-starters-must-handle","Billing Edge Cases That Ship-Ready Starters Must Handle",[11,834,835],{},"Real billing is more than a checkout button:",[87,837,838,852,861],{},[90,839,840,843,844,848,849,851],{},[93,841,842],{},"EU consent laws."," Selling to Germany means encoding a ",[42,845,847],{"href":171,"rel":846},[46],"withdrawal waiver into the pay button"," via Stripe's ",[237,850,438],{},". Getting this wrong at launch is a compliance problem, not a to-do.",[90,853,854,856,857,623],{},[93,855,179],{}," Single-tier billing doesn't survive customer reality. BoiledPlate ships ",[42,858,860],{"href":445,"rel":859},[46],"multi-plan Stripe subscriptions",[90,862,863,866],{},[93,864,865],{},"Refunds and state drift."," When Stripe says one thing and your app says another, the webhook wins.",[11,868,869],{},"Staging webhooks rarely reproduce production surprises, which is why the architecture has to be defensive from day one.",[18,871,873],{"id":872},"auth-and-security-row-level-security-done-right","Auth and Security: Row-Level Security Done Right",[11,875,876],{},"A valid JWT proves who someone is. It does not stop a query from returning another user's rows. That's the RLS gap — auth is the fast part; RLS is the part you forget until a user sees data that isn't theirs.",[11,878,879],{},"Supabase enforces permissions at query time in the database, not in application code you might bypass. BoiledPlate ships with RLS patterns already in place, which closes the most common and most dangerous class of starter-kit mistakes. RLS isn't the whole story — you still want signature verification, token expiration, and rate limiting — but it's the foundation.",[18,881,883],{"id":882},"product-delivery-as-a-feature-github-invites-and-instant-delivery","Product Delivery as a Feature: GitHub Invites and Instant Delivery",[11,885,886,887,891],{},"Like ShipFast, BoiledPlate delivers code as a GitHub repository, not an email attachment. Buy Pro and you receive GitHub access within seconds, triggered by the same Stripe webhook architecture the product teaches. The delivery mechanism ",[888,889,890],"em",{},"is"," a working example of the plumbing you're buying.",[11,893,894],{},"Pro is €159 one-time with lifetime updates. Updates ship as semantic, agent-readable release notes, so you can opt into changes even in code you've customized — a genuinely hard problem that raw git merges handle badly.",[18,896,898],{"id":897},"the-anti-plumbing-stack-why-these-tools-work-together","The Anti-Plumbing Stack: Why These Tools Work Together",[11,900,901,902,906],{},"The stack settles quickly, and each piece ",[42,903,905],{"href":150,"rel":904},[46],"demands something specific",":",[87,908,909,914,919,924],{},[90,910,911,913],{},[93,912,95],{}," — full-stack framework, minimal magic, agent-friendly.",[90,915,916,918],{},[93,917,101],{}," — PostgreSQL with RLS, fewer moving parts than a managed auth service.",[90,920,921,923],{},[93,922,113],{}," — the webhook standard every SaaS founder learns anyway.",[90,925,926,929,930,623],{},[93,927,928],{},"Resend"," — transactional email that's simple to send and annoying to send ",[888,931,932],{},"exactly once",[11,934,935],{},"Tools like Firebase auth and heavier ORMs were left out deliberately to keep the surface small and the conventions consistent.",[18,937,939],{"id":938},"technical-deep-dives-real-bugs-and-lessons-learned","Technical Deep Dives: Real Bugs and Lessons Learned",[11,941,942],{},"The trustworthy version of this stack is a log of edge cases, and BoiledPlate documents its own:",[87,944,945,953,960],{},[90,946,947,948,952],{},"A ",[42,949,951],{"href":252,"rel":950},[46],"JSON-LD hydration bug"," that returned 200 from curl and 500 in Chrome — because of source order.",[90,954,955,956,623],{},"The blog that ",[42,957,959],{"href":246,"rel":958},[46],"told Google its canonical URL was localhost:3000",[90,961,962,963,971],{},"A peer-dependency conflict where ",[42,964,967,968],{"href":965,"rel":966},"https:\u002F\u002Fboiledplate.ai\u002Fblog\u002Fvercel-web-analytics-nuxt-4-analytics-package-breaks-typecheck",[46],"@vercel\u002Fanalytics broke ",[237,969,970],{},"nuxt typecheck"," under strict mode.",[11,973,974],{},"These are the surprises that separate production from a hobby project.",[18,976,978],{"id":977},"seo-typescript-and-i18n-from-day-one","SEO, TypeScript, and i18n From Day One",[11,980,981,982,984,985,989],{},"BoiledPlate ships a prerendered Markdown blog — no CMS, version control as the source of truth — with JSON-LD and ",[237,983,239],{}," canonicals baked in. That matters because organic discovery and honest debugging posts are how SaaS founders (Marc Lou included) build durable traffic. Read the ",[42,986,988],{"href":620,"rel":987},[46],"BoiledPlate blog"," for the running log.",[11,991,992],{},"The codebase is TypeScript in strict mode, typed end to end across database, API, components, and webhooks. Strictness costs more typing upfront and catches bugs before production. It ships four languages from day one, because adding i18n later breaks routing and forces a refactor you'll resent.",[18,994,996],{"id":995},"pricing-and-positioning-free-lite-vs-pro","Pricing and Positioning: Free Lite vs. Pro",[11,998,999,1000,1003,1004,1007],{},"There are two tiers. ",[42,1001,584],{"href":582,"rel":1002},[46]," is MIT-licensed and free — clone it and wire the services manually. ",[93,1005,1006],{},"Pro"," is €159 one-time with lifetime updates and instant GitHub delivery, and it's the agent-driven setup that provisions services for you.",[11,1009,1010],{},"The value exchange is straightforward: Lite removes the barrier to trying the stack; Pro removes the weeks of plumbing. One-time pricing suits founders who'd rather pay once and own the code than rent a platform.",[18,1012,1014],{"id":1013},"when-boiledplate-is-the-right-choice-and-when-it-isnt","When BoiledPlate Is the Right Choice (And When It Isn't)",[11,1016,1017,1020],{},[93,1018,1019],{},"Good fit:"," you're building on Nuxt + Supabase + Stripe, want multi-plan billing, and work with a coding agent like Claude.",[11,1022,1023,1026],{},[93,1024,1025],{},"Wrong fit:"," you're locked into Rails or Django, you have highly custom payment logic, or your organization can't use agents. You can diverge from BoiledPlate's opinions, but every divergence trades away some of the agent's consistency benefits.",[18,1028,1030],{"id":1029},"common-questions","Common Questions",[11,1032,1033,1036],{},[93,1034,1035],{},"\"Is this just ShipFast renamed?\""," No. ShipFast is a manual template; BoiledPlate is agent-native with deterministic patches and an AGENTS.md contract. The lineage is real, the mechanism is different.",[11,1038,1039,1042],{},[93,1040,1041],{},"\"Can I really deploy in minutes?\""," The setup session is fast, but your final timeline depends on your schema and Stripe configuration.",[11,1044,1045,1048],{},[93,1046,1047],{},"\"Do I need to use Claude?\""," The starter ships agent-ready. Using an agent is optional — Lite is a clone-and-wire template either way.",[18,1050,1052],{"id":1051},"the-bigger-picture","The Bigger Picture",[11,1054,1055],{},"Marc Lou's ShipFast proved that founders will pay real money to skip plumbing, and its GitHub-delivery model set the template for the category. The next move is obvious in hindsight: if the plumbing is the project, and agents can now read conventions and apply patches, then the setup itself should run itself.",[11,1057,1058,1059,1063],{},"That's the bet BoiledPlate makes. The ",[42,1060,1062],{"href":69,"rel":1061},[46],"full product"," is worth a look if you've felt the gap between choosing a stack and actually shipping on it.",[11,1065,1066,1067,1071,1072,623],{},"For deeper background on Marc Lou's work, see ",[42,1068,367],{"href":1069,"rel":1070},"https:\u002F\u002Fshipfa.st\u002F",[46]," and his write-up of the launch on ",[42,1073,1076],{"href":1074,"rel":1075},"https:\u002F\u002Fjustship.it\u002F",[46],"Just Ship It",{"title":300,"searchDepth":301,"depth":301,"links":1078},[1079,1080,1081,1082,1083,1084,1085,1086,1087,1088,1089,1090,1091,1092,1093],{"id":728,"depth":304,"text":729},{"id":745,"depth":304,"text":746},{"id":768,"depth":304,"text":769},{"id":791,"depth":304,"text":792},{"id":808,"depth":304,"text":809},{"id":831,"depth":304,"text":832},{"id":872,"depth":304,"text":873},{"id":882,"depth":304,"text":883},{"id":897,"depth":304,"text":898},{"id":938,"depth":304,"text":939},{"id":977,"depth":304,"text":978},{"id":995,"depth":304,"text":996},{"id":1013,"depth":304,"text":1014},{"id":1029,"depth":304,"text":1030},{"id":1051,"depth":304,"text":1052},"2026-08-02","Explore Marc Lou's ShipFast GitHub template, how it revolutionized SaaS launches, and why AI-native starters are the next evolution.",{},"\u002Fblog\u002Fmarc-lou-shipfast-github-saas-starter",{"title":720,"description":1095},"blog\u002Fmarc-lou-shipfast-github-saas-starter",[1101,367,1102,1103],"SaaS","GitHub","Startup Tools","rFETvBQgWaU8ppz1yTtkXSF7WuFDQU_aJ1ff8-N81v0",1785891129746]