Software licensing types, explained simply
"Software license" covers a wide range of very different arrangements, from a one-time purchase of shrink-wrapped software to a subscription that only grants access for as long as payments continue. Picking the wrong category — or not realizing which category a piece of code you're using actually falls into — is one of the more common ways small businesses create legal exposure without meaning to.
Proprietary and commercial licenses
A proprietary license is the traditional model: the software owner keeps all rights and grants the customer a limited, defined right to use the software under specific conditions — a certain number of seats, a particular installation, a time period, or a specific use case. The customer never owns the underlying code and typically can't modify, redistribute, or reverse-engineer it. Most commercial desktop software, enterprise tools, and custom-built business software fall into this category.
Open-source licenses: permissive vs. copyleft
Open-source licenses grant much broader rights — to view, modify, and often redistribute the source code — but they come in meaningfully different flavors, and the difference matters a lot more than most people assume when they're just trying to ship a product.
- Permissive licenses (like MIT or Apache-style licenses) — generally allow the code to be used, modified, and incorporated into proprietary products with minimal obligations, often just preserving a copyright notice
- Copyleft licenses (like GPL-style licenses) — generally require that products built using the licensed code, or that incorporate it in certain ways, also be released under the same or a compatible open license
Both categories include real variation within them, and the exact obligations of any specific license depend on its precise terms — this is a general orientation, not a substitute for reading the actual license text of a component before shipping it.
SaaS and subscription licensing
When a business sells access to software as a service, customers typically aren't licensing the software itself at all — they're licensing ongoing access to a hosted service for as long as they keep paying. There's usually no copy of the software changing hands, no installation, and no residual rights once a subscription lapses. This distinction matters for how a SaaS agreement should actually be written: terms around uptime, data handling, and what happens to a customer's data after cancellation matter more here than the kind of usage restrictions that dominate a traditional software license.
White-label and reseller licensing
White-label licensing lets another business rebrand and resell software as if it were their own product, usually for a fee, a revenue share, or both. A reseller license is closely related but typically keeps the original branding intact — the reseller is distributing the product, not relabeling it. Both arrangements need clear terms about who owns the underlying code, what support obligations exist, how revenue is split, and what happens to the reseller's or white-label partner's customers if the underlying agreement ends.
Why picking the wrong license type causes real problems
The most common and most expensive mistake is incorporating a copyleft-licensed open-source component into a proprietary product without realizing what that license actually requires. Depending on the specific license and how the component is integrated, that can create an obligation to release parts of an otherwise proprietary codebase under the same open license — a consequence that's often discovered only during due diligence for a funding round or acquisition, at which point unwinding it is far more disruptive than checking license terms up front would have been.
A second common problem is a mismatch between the license type and how customers actually use the product — for example, licensing terms written for a single-installation desktop tool being applied unchanged to a multi-tenant SaaS product, leaving gaps around data ownership, uptime, and account termination that a traditional software license was never designed to address. The fix in both cases is the same: match the license type to what's actually being distributed and how it's actually being used, rather than defaulting to whatever template is easiest to find.
Choosing the right structure matters whether you're licensing your own software to a customer, licensing someone else's technology into your product, or setting up a white-label arrangement with a partner.
Free IP licensing agreement template
Software built around a genuinely novel technical mechanism sometimes raises the separate question of whether that mechanism itself is patentable, which is a different kind of protection from any license.
What is a patent, and does your business need one?
Frequently asked questions
Can I use open-source code in a commercial product?
Often yes, but it depends entirely on the specific license attached to that component. Permissive licenses generally make this straightforward; copyleft licenses can impose real obligations on the rest of the product, so it's worth checking before code from an unfamiliar license ends up shipped.
What's the real difference between a license and selling software outright?
Selling software outright transfers ownership of the code itself. A license, even a broad or permanent one, grants a defined right to use the software while the underlying ownership stays with the licensor — the two look similar day-to-day but behave very differently if a dispute ever arises.
Do I need a different license for each customer?
Not usually — most businesses use one license template with variables (seats, term, price, use case) filled in per customer, rather than drafting a new agreement from scratch for each deal.
What happens to a customer's license if my company is acquired?
That depends on the assignment terms written into the original license agreement — well-drafted licenses address this directly, which is exactly why relying on a solid template rather than an ad hoc agreement matters.
Why teams start with Docracy
“Docracy is a great product that I have tested and am using. It is easy to use, has good tools, is always up to date, and implements new features. Highly recommended.”— DACH Advisory
Also: Compare e-sign pricing · Free mutual NDA template
No account required for up to 2 signers.