Blog · 16 November 2026 · 6 minute read
SaaS boilerplate or launch automation: which one do you need?
Boilerplates give you code. Launch automation gives you live infrastructure. What each solves, and how to choose now that AI writes most of the code.
Two different problems
Getting a product live has two halves. One is the code every product needs: sign-in, payments, email, a landing page. The other is the infrastructure that code runs on: a domain, hosting, a database, a verified sending domain, a payment account wired to a webhook.
A boilerplate solves the first half. Launch automation solves the second. They are often compared as if they competed, but they answer different questions.
What a boilerplate gives you
A boilerplate is a ready-made codebase you buy or download and build on. Well-known examples, such as ShipFast for Next.js, come with authentication, payment code, email templates and page components already written. You skip the weeks of writing things every product has.
What you still do yourself is everything outside the code: create the accounts, buy the domain, set the DNS, verify the email domain, create the payment product and copy each key into place. The boilerplate documents these steps. It does not perform them.
What changed
The value of a boilerplate was the code it saved you from writing. That value has dropped, because an AI coding tool now writes a sign-in flow or a checkout page in minutes, in whatever framework you ask for, shaped to your product instead of to a template.
The setup has not got any faster. The dashboards are the same, the DNS still takes its time, and the keys still have to be copied by a person. For someone building with AI, the slow half is now the infrastructure.
What launch automation gives you
Launch automation does the account-side work: it registers the domain, creates the DNS records, the repository, the hosting project and the database, verifies the sending domain, creates the payment product and webhook, and stores each key where the app reads it. The result is not code. It is a live, empty product on your own domain, ready to be built on.
It does not write your application. That stays with you and your coding tool.
How to choose
- You write code by hand and want to skip the common parts: a boilerplate saves you the most.
- You build with an AI coding tool: the code is cheap, so automate the setup.
- You launch one product a year: either works, and doing the setup by hand once is fine.
- You launch often, to test ideas: the setup is your repeated cost, so remove it.
- You want a specific framework and structure enforced: a boilerplate gives you that.
- You want to own every account and avoid lock-in: check that whichever tool you pick creates things in your accounts, not theirs.
Can you use both?
Yes. They do not overlap. You can launch the infrastructure first and then build on a boilerplate, or point launch automation at an existing repository. The only thing to check is that the variable names the code expects match the ones the launch creates.
Where Shipyard sits
Shipyard is launch automation. It runs on your computer, uses your own provider accounts, and sets up the infrastructure for each new product in about an hour once your accounts are connected. Then it writes a build prompt that tells your coding tool exactly what exists. It deliberately ships no application code: that is the part AI already does well.
Launch in an hour, not a weekend
Shipyard connects your accounts once, then sets up the domain, hosting, database, email and payments for every new product.
See how it works