Template Licenses Explained: What “Single Site” Actually Means
Commercial template licenses limit developer seats and end-user monetization — not domains. Here is how to read the clauses and pick the right tier.
A single-site template license usually does not mean one site. In almost every commercial template license, the limit is the number of developers who touch the code and whether end users pay to access what you build — not how many domains you deploy to. Read those two clauses and you have read 90% of the agreement.
That mismatch between the name and the terms is where most licensing mistakes start. This post walks through what the clauses actually say, which ones matter for your situation, and the three questions that decide which tier you need.
The two clauses that decide everything
Every commercial template license, from ThemeForest to independent shops, is built on the same two axes. Vendors name their tiers differently, but the axes do not change.
1. Developer seats. How many people may work with the source. This is the license's real "size" metric. A seat is a person, not a machine and not a project — one developer with a laptop and a desktop is one seat.
2. End-user monetization. Whether the people using your finished product pay to access it. This is the clause that trips up the most buyers, and it is almost always the difference between the cheap tier and the expensive one.
Notice what is not on that list: the number of sites. Most licenses that market themselves as "single site" are actually single-developer or single-product licenses. Read the terms rather than the tier name.
What "end product" means, and why it matters
The term of art is end product: the thing you build with the template. Licenses draw a hard line between two kinds.
| Free-to-access end product | Paid-access end product | |
|---|---|---|
| Examples | Client site, internal admin tool, portfolio, marketing site, free community app | SaaS with subscriptions, paid member area, a product with a paywall |
| Who pays | The client pays you to build it. End users pay nothing to use it. | End users pay to get in. |
| Typical tier needed | Entry / regular | Extended / SaaS tier |
The distinction is about who pays for access to the end product, not whether money changed hands anywhere. This is the single most misunderstood point in template licensing, so it is worth being precise:
- A client paying you $20,000 to build their marketing site is free-to-access. The client is not an end user; the visitors are, and they pay nothing.
- A $9/month app you built for yourself is paid-access, even though it earns less than the client project.
The fee you collect is irrelevant. What matters is whether the end user is charged.
How this maps to real tiers
Here is the same structure across the two most common models, plus ours, so you can translate between them.
| ThemeForest Regular | ThemeForest Extended | ASoc Single ($39) | ASoc All-Access ($129) | ASoc Full Stack ($249) | |
|---|---|---|---|---|---|
| Developer seats | Not seat-based | Not seat-based | 1 | 3 | 5 |
| Templates covered | 1 item | 1 item | 1 template, every framework edition | Every template, current and future | Every template + the backend |
| Free-to-access end products | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited |
| Charge end users for access | ✗ | ✓ | ✗ | ✗ | ✓ |
| Resell or redistribute the source | ✗ | ✗ | ✗ | ✗ | ✗ |
Two things generalize beyond this table.
Unlimited end products is normal. Nearly every commercial template license lets you build unlimited free-to-access end products. If you are a freelancer shipping client sites, one license genuinely covers all of them. You are not expected to buy one per client.
Redistribution is never allowed. No tier, at any vendor, at any price, lets you resell the template source itself — including bundling it into a "starter kit" or a boilerplate you sell. The license grants you the right to build with the code, not to distribute the code. This is the one clause with no upgrade path.
Three questions that pick your tier
Work through these in order. They resolve almost every real case.
1. Will end users be charged to access what you build? If yes, you need the SaaS/extended tier, and nothing cheaper will do. Stop here. If no, continue.
2. How many developers will touch the source? Count people who open the code, not people on the project. A designer reviewing screenshots is not a seat. A contractor writing components is.
3. Will you build more than one distinct product with it? If you expect two or three projects over a year, compare the single-template price times three against the all-access price. Bundle tiers are usually cheaper at two or more.
That is the whole decision. Everything else in a template EULA — warranty disclaimers, liability caps, governing law — is boilerplate that will not change what you buy.
Cases people get wrong
| Situation | Which side of the line | Why |
|---|---|---|
| Agency builds 12 client marketing sites | Free-to-access | Visitors pay nothing. The client's fee is not end-user access. |
| Internal HR dashboard at a 500-person company | Free-to-access | Employees are not charged. Company size is not a licensing axis. |
| Your side project with a $5/mo Pro plan | Paid-access | End users are charged. Needs the SaaS tier despite tiny revenue. |
| Open-source project using the template's UI | Free-to-access, but check redistribution | The end product is fine. Publishing the template source in a public repo is not. |
| Free app monetized by ads | Free-to-access | Users are not charged for access. Advertisers are not end users. |
| Client wants the source when you hand off | Needs their own license | Transferring the template source is redistribution. Seats are non-transferable. |
| One developer, five different client projects | Free-to-access, 1 seat | Unlimited end products, one person touching the code. |
| Reselling as part of a boilerplate you sell | Never allowed | Redistribution. No tier permits this. |
The handoff case is the one that catches agencies. When you finish a client project and deliver the repository, you are transferring template source to someone who is not licensed for it. The clean answer is that the client buys their own license — most vendors will confirm this is the expected path, and it is cheap relative to the project.
Free editions and MIT
Some vendors, including us, publish free editions under the MIT license. MIT is genuinely different, not a smaller version of the commercial license: it permits redistribution, modification, and commercial use with no seat limits and no end-user restrictions. The only obligation is preserving the copyright notice.
If an MIT edition covers what you need, you do not need a commercial license at all. The commercial tiers exist to fund the work that is not in the free edition — more screens, more components, the backend — not to restrict things MIT already allows.
Check which license applies per product, though. A vendor with both models applies different terms to different items, and the repository's LICENSE file is the authority for the free ones.
Frequently asked questions
Does "single site" mean I can only deploy to one domain? Almost never. In most commercial template licenses, including ours, the limit is developer seats and end-user monetization. Staging, preview, and production deployments of the same product are not separate sites. Read the terms rather than the tier name — but if a specific vendor genuinely does limit domains, that clause will be explicit.
What happens if my free app later adds paid plans? You upgrade to the SaaS tier at that point. Licenses are not applied retroactively — what you already built stays licensed — but charging end users going forward requires the tier that permits it. Budget for it when you plan the paid launch, not after.
Can my client use the template after I hand off the project? They can use the end product you built. They cannot receive the template source under your license, because seats are non-transferable. If they need the source to maintain it, they should buy their own license.
Do I need a new license for each client project? No. Every mainstream template license permits unlimited free-to-access end products. One license, many client sites — provided the seat count covers everyone touching the code and none of the products charge end users for access.
Is a perpetual license really perpetual? For what you have already built, yes — a license is not revoked retroactively, so shipped products stay licensed. What varies between vendors is whether you keep receiving updates. Ours includes lifetime updates on every tier; not all do. That is a separate clause from the grant itself, and worth checking.
The short version
Ignore the tier names. Find the seat count, find the end-user monetization clause, and confirm redistribution is prohibited (it is). Those three answers tell you what you can build and which tier you need, in about two minutes of reading.
Our full terms are on the license page, and the tiers with current pricing are on pricing. If your case is not covered above — and unusual ones do exist — ask us before you buy rather than after. We would rather answer the question than process a refund.