License Types for Code Templates Explained (Single, Multi, Agency)

A template license explained in one line: it is a contract about domains and deployments, not about the code itself. Buying a theme, a Figma kit, or (soon) a Next.js starter almost never transfers copyright — it grants you permission to install and run that code on a specific number of live sites. Single-site licenses cover one production domain. Multi-site (or "developer") licenses cover a bundle of domains, usually under one owner. Agency licenses cover deploying the same purchased template across multiple different clients' domains, which single and multi-site licenses explicitly forbid. Confusing these three is the single most common way buyers end up violating a license without meaning to.

This distinction matters more for code templates than it does for, say, stock photography, because code gets redeployed in ways images don't. A designer might reuse a photo across a moodboard without thinking twice; a developer reusing a purchased Shopify theme or Figma UI kit across five unrelated client projects is doing something categorically different, and most marketplaces price and license for exactly that difference. This guide breaks down what each license type actually permits, where the gray areas sit, and how to buy the right tier the first time.

The Three License Tiers, Plainly

Single-site (or single-use) license

A single-site license permits you to deploy the template on one live production domain (plus, typically, unlimited staging/dev copies of that same domain). This is the default tier for most theme and starter-kit purchases, and it is priced for someone building one store or one product — a founder, a solo store owner, an in-house team shipping their own brand's site. If you buy a single-site license for a theme and later launch a second, unrelated brand, that second site is not covered — you need a second license (or a multi-site tier), even if the two sites never overlap in traffic or ownership.

Multi-site (or "developer") license

A multi-site license raises the domain cap — commonly to 3, 5, or "unlimited" depending on the vendor — but it is almost always still scoped to one purchasing entity. In practice: if you personally or your single company own five different stores under the same license holder, a multi-site license is built for exactly that. What it does not cover, even though the name invites the confusion, is deploying the same license across five separate paying clients. The "multi" refers to how many of *your own* sites you can run, not how many customers you can resell the deployment to.

Agency (or extended/client) license

An agency license is the tier built for freelancers and agencies who build sites *for other people*. It permits deploying the purchased template to a client's domain, where that client — not the license purchaser — owns and operates the resulting site. This is the tier you need the moment your business model is "I build this for other companies," even if you only ever do it once. Agency licenses are usually priced meaningfully higher than single-site, because the vendor is licensing an entire class of end customers rather than one site, and because the agency itself typically isn't the one paying for hosting or running the business behind the final site.

Why This Distinction Exists at All

Template pricing works on a simple principle: the license price should scale with the *economic value extracted* from the template, not with the hours spent customizing it. A single founder building one store gets a fraction of the value that an agency gets from reusing the same purchased asset across ten paying client engagements — the agency is effectively reselling the template's design work ten times over inside its service fee. License tiers exist to make that value gap show up in price, rather than relying on buyers to voluntarily pay more because it feels fair.

This is also why "I only used 20% of the template's code before heavily customizing it" is not a defense that changes which license applies. Licenses are triggered by deployment to a domain, not by how much of the original code survives in the final build. A theme that's been restyled beyond recognition, if it started life as one purchased template deployed to five different client domains under a single-site license, is still a licensing violation — the modification doesn't retroactively unlock multi-domain rights.

Common Situations and Which License They Actually Need

• Freelancer building a client's Shopify store, one-off: needs an agency/client license even for a single project, because the domain will be owned and operated by the client, not the freelancer.
• Founder running three separate DTC brands personally: a multi-site (developer) license fits, since all three domains sit under one owner — assuming the license terms count "owner" as the purchasing entity rather than the number of storefronts.
• In-house dev team building the company's main site plus a regional subdomain-style microsite: often single-site is enough if the license explicitly counts subdomains of the same root domain as one site — but check the fine print, since vendors differ here.
• Design agency delivering Figma files to a client, who then hands them to their own developer: still an agency/client license situation, because the license needs to cover the client's eventual use, not just the agency's internal work.
• Template reseller or marketplace flipping the same purchased asset to multiple end buyers: not covered by any standard license tier — this is redistribution, and it needs an explicit resale/redistribution license, which most vendors don't sell at all.

Reading a License Before You Buy

Three questions cut through most license confusion before you commit to a purchase:

1. Who owns the domain the code will run on? If it isn't you or your own company, you almost certainly need an agency/client license, not single or multi-site.
2. How many separate production domains will actually run this code? Count real domains, not subdomains or staging copies — most vendors don't count those against the cap, but confirm rather than assume.
3. Will the code, or a derivative of it, ever be handed to someone else to operate independently? If yes, that's the agency case even if you built the whole thing yourself.

If the answer to any of these is ambiguous, the safer and cheaper move is almost always to ask the vendor directly before buying, rather than guess and hope the lower tier holds up. Most legitimate template vendors will answer a pre-sale licensing question quickly, because a clear answer prevents a support dispute later. Buying the wrong tier upfront costs less than an eventual license upgrade demanded mid-project, and it avoids the awkward position of explaining to a client why their site needs to be re-licensed after launch.

How This Applies as You Move Into Code, Not Just Design

Licensing gets more consequential, not less, as you move from a design file to shipped code. A Figma kit misused across client projects is a contract problem; a Next.js storefront or headless commerce starter misused the same way is a contract problem plus a live production dependency — the client's actual checkout, actual customer data, and actual uptime are riding on code whose license terms may not cover the deployment it's running on. As buyer-education content, the same three questions above apply directly to evaluating any commercial Next.js starter or headless commerce boilerplate: confirm who owns the domain, count the real number of production deployments, and confirm whether client hand-off is covered before you build a client engagement around a single-site license.

Polo Themes currently sells Figma UI kits and Shopify themes under these same single/multi/agency conventions — see our Figma kits and Shopify themes catalogs for the specific terms attached to each product. We're also building toward production-grade Next.js and headless commerce starters as a stated direction for the catalog, and when those ship, they'll carry the same clear single-site/multi-site/agency structure described here rather than a novel licensing scheme — consistency across a catalog is worth more to buyers than a clever new tier. Until then, the guidance above applies to evaluating any Next.js starter on the market today, ours or otherwise.

Frequently Asked Questions

Can I use a single-site license for a staging or dev copy of the same site?

Almost always yes — staging/dev environments of the *same* production domain are conventionally included, but this varies by vendor, so confirm rather than assume for any specific purchase.

Does heavily customizing a template change which license I need?

No. License scope is determined by how many domains the code is deployed to and who owns them, not by how much of the original template's code or design survives after customization.

I'm a solo freelancer doing one client project — do I really need an agency license for just one site?

Yes, if the client will own and operate the resulting site. Agency/client licensing is triggered by who owns the end domain, not by the size of your business or how many projects you've done.

What happens if I use the wrong license tier?

Outcomes vary by vendor, but typically range from a required license upgrade (paying the price difference after the fact) to takedown requests for non-compliant deployments. Asking before buying is cheaper than resolving a dispute after a client site is already live.