What is a Software License, and How is it Measured?

Short answer: a software license is permission to use software the owner still owns. Its boundaries live in the grant clause and the license metric, and your software should actually enforce what the agreement says.

Every software company should understand what the term software license actually means.

As a software attorney who tries to keep it simple, let me briefly explain: it is the right or permission to use the software, granted by the owner. The user is not given ownership (that is retained by the owner), but they do receive the right to use the software. Software is protected by copyright, so the owner keeps the exclusive rights and grants you a limited permission to use a copy (see 17 U.S.C. § 117).

Q: What are the boundaries of the right to use software?

A: That depends on what the license agreement says, usually in the GRANT section (e.g., “X grants to Y a non-exclusive, non-transferable license to operate the software on…”). There are literally thousands of possible license metrics (ways to measure usage), so a software company should communicate its license metric inside and outside of the license agreement.

The key things to remember in defining your software license and metrics:

1) Know what your license agreement says, because you are granting users specific legal rights.

2) Grant the users the “correct” usage rights, but not necessarily more, as that is what they are expecting.

3) Your software should operate consistently with those license rights. If the license is limited to one module, do not allow them to use other modules; if limited to one user, do not allow more users access. A counter in the software helps users tell whether they are within their license rights.

The Common License Metrics.

Most disputes about scope trace back to a fuzzy metric, so pick one your customers can understand and your product can count:

• Named user: tied to a specific individual.
• Concurrent user: a number of simultaneous users, regardless of who.
• Device or server: tied to machines or installations.
• Capacity: tied to a unit of consumption (transactions, records, API calls, seats).
• Subscription: time-bounded access to the service, common in SaaS.

Your Metric Is a Revenue Decision, Not Just a Legal One.

The metric you pick is also your pricing model, so it deserves real thought. A good metric tracks the value the customer gets (more usage, more fee) and is something both sides can measure without arguing. A bad metric is one nobody can count, or one that lets usage balloon while your fee stays flat. If your software cannot measure the metric in your contract, you have given away an unenforceable license. Pick a metric your product can actually meter, then make sure the grant language and the meter match.

Make the Software Enforce the License.

The gap I see most often is between what the contract grants and what the product allows. The agreement says “one named user,” but the login is shared across a whole team. The agreement says “module A only,” but every module is unlocked. When the contract and the product disagree, you are leaving money on the table and you have a weak position if you ever need to enforce. Build the limit into the software, surface a usage counter so the customer can self-police, and your license stops being a paragraph nobody reads and becomes a real boundary.

Software License Metrics: Common Questions.

What is a software license? It is permission to use software that the owner still owns. You get the right to use it within the limits set by the grant clause; you do not get ownership of the software itself.

What is a license metric? The unit that measures permitted usage, such as named users, concurrent users, devices, capacity, or a subscription term. It is both your legal limit and your pricing model.

How do I keep a software license enforceable? Pick a metric your product can actually count, match the grant language to that meter, and build the limit into the software so usage cannot quietly exceed what the customer paid for.

This summary only addresses one type of legal definition of a license. There are other legal uses of the term (government license, professional licenses, license to enter property, and so on). If you want help defining your grant and license metrics, that is exactly what a software licensing attorney does, and for the limits you can put on that grant, see Restrictions In License Agreements.

For the foundational decision between a software EULA and a SaaS subscription structure, see SaaS Agreement vs. Software EULA: Which Template Do You Need?

I hope this helps.

Disclaimer:

This post is for informational and educational purposes only, and is not legal advice. You should hire an attorney if you need legal advice, which should be provided only after review of all relevant facts and applicable law.