Short answer: To license a boilerplate for SaaS products, pick a license that fits your business model. Most creators use a commercial license with per-project pricing or a subscription. Avoid open-source licenses like MIT if you want to charge for the boilerplate.
Key takeaways
- Open-source licenses let anyone resell your boilerplate for free.
- Commercial licenses give you control over usage and pricing.
- Per-project licensing is best for one-time sales.
- Subscription models create recurring revenue.
- Include indemnification clauses to limit your liability.
- Always consult a lawyer for your final license text.
What you will find here
So you’ve built a solid SaaS boilerplate. It saves weeks of work for other developers. Now you want to sell it — but you also want to protect your work. The way you license that boilerplate decides everything: who can use it, how much you earn, and whether it ends up for sale on someone else’s store.
This guide covers the practical choices. No legal advice — just what you need to know before you pick a license.
Why You Can’t Just Use MIT or GPL
Many boilerplate creators start with an open-source license because it’s easy. Big mistake. An MIT license lets anyone copy, modify, and resell your code — including your own paying customers. They can strip your name and sell it as theirs.
If you want to charge for your boilerplate, never use MIT, Apache, GPL, or any OSI-approved open-source license. Those are designed for community projects, not commercial products. Instead, write your own commercial license or use a standard one like the PolyForm Noncommercial License (for free personal use) with a separate commercial version.
Commercial License Types for Boilerplates
Here are the three most common approaches:
Per-Project License
The customer pays once and can use the boilerplate in a single SaaS product. They cannot transfer it to another project. This works for one-time sales on marketplaces like Gumroad or CodeCanyon. Price it between $49 and $299 depending on complexity. Be explicit about what constitutes a “project” — for example, a single codebase deployed as one branded product.
Unlimited (Developer) License
One developer can use the boilerplate in any number of their own projects, but not for client work under a separate contract. This is common for agencies that build multiple SaaS tools. Price it 2-5x the single-project cost. Make sure to specify that the license is non-transferable — if the developer leaves the company, the license stays with the company, not the individual.
Extended / Enterprise License
Allows the customer to use the boilerplate in a product they sell to end users, often with no revenue cap. Also covers white-labeling (removing your credits). Price this at least 5-10x the single project cost or set up a custom quote. Include a clause that subsidiaries of the purchasing company are covered only if explicitly listed in the agreement.
Pricing Models: One-Time vs Subscription
A one-time license is simple, but it leaves money on the table. Customers pay once and get updates for life (or you stop supporting). A subscription gives you recurring revenue and lets you fund ongoing development.
Consider a hybrid model: yearly subscription with access to updates and support, but a perpetual license for the version they download during the subscription term. That way, if they cancel, they keep the last version they licensed. This reduces churn risk because customers don’t lose access to what they’ve already paid for.
| Model | Pros | Cons |
|---|---|---|
| One-time payment | High upfront revenue, simple | No recurring income, support burden forever |
| Subscription | Recurring revenue, funds updates | Churn risk, lower upfront |
| Hybrid (perpetual + updates sub) | Best of both | More complex to manage |
Key Legal Clauses to Include
Even if you’re not a lawyer, your license needs these protections:
- Grant of License: Clearly state what the customer can and cannot do. Be explicit: “You may use this boilerplate in one (1) commercial SaaS product.” Avoid vague terms like “personal use” — define it narrowly.
- Restrictions: List forbidden uses — reselling the boilerplate as-is, redistributing it on marketplaces, using it to build a competing boilerplate. Also prohibit using the boilerplate to create a template or theme for resale.
- Indemnification: You’re not liable if the customer’s product gets hacked. Include an “as-is” disclaimer and a limitation of liability. Cap your liability to the license fee paid.
- Termination: If the customer violates the license, you can revoke it. Spell that out. Give them a grace period (e.g., 30 days) to cure the violation before termination takes effect.
- Governing Law: Pick a jurisdiction. Usually where you live or where your business is registered. This matters if you ever need to enforce the license in court.
Common Mistakes and How to Avoid Them
Experienced boilerplate sellers — like the ones you’ll find on TemplateRevenue — often share the same hard lessons:
Mistake 1: Using an open-source license on accident
If you push your boilerplate to a public GitHub repo without a license file, it defaults to “all rights reserved” in some jurisdictions — but that’s not safe. Explicitly add a commercial license file. Even better, keep your boilerplate in a private repo and only provide access after purchase.
Mistake 2: Not defining “project”
Your license says “one project.” The customer builds a monorepo with two SaaS tools in it. Is that one project or two? Define it: a project is a single codebase deployed as one branded product. Also specify that separate staging or development environments count toward the same project if they are for the same product.
Mistake 3: Forgetting about subsidiaries
An enterprise customer with 12 subsidiaries — does each need a separate license? Address this in an enterprise addendum. Offer a “group license” that covers all subsidiaries at a discounted rate, but require a list of entities to be provided at purchase.
Should You Hire a Lawyer?
Yes. This article is not legal advice. A lawyer can draft a license tailored to your boilerplate and your target market. The cost (often $500-$2000 for a simple commercial license) pays for itself the first time a customer tries to resell your code. Ask the lawyer to include an audit clause so you can request records if you suspect misuse.
At minimum, use a reputable template like the PolyForm Perimeter License or the Blue Oak Council License — both are lawyer-reviewed and clear. But remember, templates are not a substitute for advice specific to your situation.
What About Open Source as a Marketing Strategy?
Some creators open-source the core and sell premium plugins or support. That works — but only if your open-source license allows it. Use an SSPL or AGPL variant that discourages commercial use without a paid license. Be ready for people to fork your code and compete with you. If you go this route, make sure the open-source version is noticeably limited — remove key features like authentication, billing integrations, or admin dashboards.
The choice is clear: if you want to build a business on your boilerplate, use a commercial license. If you want a community around it, use open-source. You can’t have both without careful dual-licensing.
How to Enforce Your License
Writing a license is step one. Enforcing it is step two. Start by requiring customers to register with an email and agree to the license at checkout. Send them a copy of the license with their receipt. Periodically check marketplaces like CodeCanyon or Gumroad for unauthorized copies of your boilerplate. If you find one, send a DMCA takedown notice. For serious violations, consult your lawyer about sending a cease-and-desist letter.
Now pick a license, write it down, and go sell your boilerplate. Your time is worth it.
Frequently asked questions
Can I use an MIT license for my paid boilerplate?
Technically yes, but you probably shouldn’t. MIT allows anyone to copy and resell your work for free. You lose control over distribution and pricing. Customers who pay you could simply download a free copy from someone else.
What’s the difference between a per-project and unlimited license?
A per-project license lets the customer use the boilerplate in exactly one SaaS product. An unlimited license lets them use it in any number of their own projects. The unlimited version typically costs more.
Do I need to register my boilerplate license?
No, copyright protection is automatic when you create the work. Registration (e.g., with the US Copyright Office) gives you additional legal benefits like statutory damages but isn’t required for a valid license.
Can I change my boilerplate’s license after selling it?
Existing customers are bound by the license they agreed to when they purchased. You can change the license for future sales, but you can’t unilaterally change terms for past customers unless your license reserves that right.
How do I enforce my boilerplate license?
Start with a cease-and-desist email. If ignored, you can escalate to a DMCA takedown (if the code is hosted online) or pursue legal action. Having clear, written terms makes enforcement much easier.