Types of software licenses determine who may use software, how it may be deployed, and whether its code may be modified or distributed. Understanding the categories helps you buy software, select terms for your own product, and avoid compliance problems.
Key Takeaways
- Proprietary, open-source, freeware, and shareware describe legal rights or distribution approaches.
- Perpetual, subscription, and usage-based licensing describe payment or access duration, not ownership of the code.
- User-based, device-based, concurrent, server, and site licensing measure the permitted scope of deployment.
- Open-source licenses may be permissive or copyleft, with different conditions for modification and distribution.
- Freeware, open-source software, and public-domain software are not interchangeable terms.
- The governing agreement controls support, updates, transfer rights, audit procedures, and remedies for violations.
Types of Software Licenses: Families vs. Licensing Models
There is no single authoritative number of software license types. Lists vary because they often combine several different classification systems. A useful analysis starts by separating license families from commercial and deployment models.
A license family addresses your legal rights in the software. Proprietary licenses usually keep the source code closed and give you limited usage rights. Open-source licenses permit access to source code and grant rights to use, modify, and distribute it, subject to the specific license. Freeware and shareware describe ways software may be offered, but they do not necessarily give you source-code rights.
A payment or duration model explains when and how you pay. Examples include perpetual, subscription, and usage-based licensing. A perpetual license can still be proprietary, while an open-source product may also have paid support or commercial editions.
A deployment metric defines the units covered by the license. Common metrics include named users, devices, concurrent users, processors, servers, sites, and enterprise-wide access. Channel restrictions, such as OEM, educational, and not-for-resale terms, may add another layer.
This distinction explains why one application can carry several labels at once. For example, a product could use a proprietary license, charge by subscription, assign access by named user, and limit deployment to a particular business entity. The agreement, including any order form and usage rules, determines how those layers work together.
Software License Types and Models Compared
The following table shows what common categories generally control. Actual rights vary, so review the governing agreement rather than relying on the category name alone.
| Type or Model | What It Controls | Modification or Redistribution | Common Use | Terms to Check |
|---|---|---|---|---|
| Proprietary | Use of closed-source software | Usually restricted | Commercial applications | Users, copies, transfer, audit |
| Permissive open source | Use of source code with limited conditions | Generally allowed | Libraries and commercial products | Notices, attribution, patent terms |
| Copyleft open source | Use and distribution of open code | Allowed with license obligations | Open-source projects | Source disclosure and distribution triggers |
| Freeware | No-fee use of software | Often restricted | Utilities and readers | Commercial use and installation limits |
| Shareware | Trial or limited use | Usually restricted | Product evaluation | Trial period, features, payment |
| Perpetual | Duration of use | Depends on license family | On-premises software | Version, maintenance, support |
| Subscription | Time-limited access | Depends on license family | SaaS and regularly updated tools | Renewal, termination, data access |
| User or device based | Number of users or machines | Usually unrelated | Workplace applications | Reassignment and shared access |
| Enterprise or site | Organizational or location scope | Usually unrelated | Large deployments | Affiliates, locations, contractors |
These classifications overlap. A perpetual license does not automatically allow redistribution, and a subscription does not necessarily mean the software is hosted by the vendor. Read the definitions in the contract and order documents.
Proprietary, Freeware, Shareware, and Public-Domain Software
A proprietary license allows you to use software while the publisher retains ownership of the code and related intellectual property. The license may prohibit copying, reverse engineering, modification, sublicensing, or resale. Microsoft Windows is a familiar example of proprietary software, although the exact rights depend on the applicable Microsoft product terms and purchase channel. For a closer look at typical restrictions, see this explanation of a proprietary software license.
Freeware is proprietary software made available without a license fee. Free access does not place the software in the public domain or provide permission to modify its code. A freeware license may limit commercial use, redistribution, installations, or bundled distribution.
Shareware generally permits evaluation for a limited period or with limited features. Continued or expanded use may require payment. Businesses should track shareware installations because an employee's trial can become unauthorized use after its permitted period ends.
Public-domain software is different. Copyright restrictions may not apply because the work is no longer protected or the rights holder has attempted to dedicate it to the public. A public-domain dedication is not the same as an ordinary software license, and its legal effect may depend on applicable law. Businesses should still assess warranties, security, provenance, patent issues, and third-party components.
The word "free" can therefore refer to price, legal freedom, or copyright status. You should identify which meaning applies before using software in a commercial product or business environment.
Open-Source Licenses: Permissive vs. Copyleft
Open-source licenses make source code available and grant rights to use, modify, and distribute it under stated conditions. Open source does not necessarily mean free of obligations or unavailable for commercial use. The applicable license text controls.
Permissive licenses, including the MIT, BSD, and Apache 2.0 licenses, generally allow broad reuse with limited conditions. These conditions may require preservation of copyright notices, attribution, or license text. The Apache 2.0 license also contains express patent-related provisions. Developers often use permissively licensed components in proprietary products, but they must still satisfy the stated notices and other requirements.
Copyleft licenses, including the GNU General Public License, seek to preserve specified freedoms when covered software is distributed. Depending on the license and how code is combined or conveyed, obligations may include providing corresponding source code, retaining notices, and licensing covered derivative work under the same terms. Not every use or internal modification creates the same obligations, so review the exact version and distribution method.
Weak copyleft and network-focused licenses can produce different results from strong copyleft licenses. Avoid assuming that all licenses using the "GPL" label operate identically. Your review should identify each component, its license version, how it interacts with your code, and whether you distribute software or provide it over a network.
ChooseALicense.com can help explain common license features, but the official license text remains controlling. Creative Commons licenses generally target creative works rather than software code, and Creative Commons advises using an established software license for software.
Perpetual, Subscription, Usage, and Deployment Models
A perpetual license grants the right to use a covered software version for an indefinite period, subject to the agreement. It does not automatically include indefinite support, maintenance, updates, new versions, cloud hosting, or compatibility services. Those benefits may have separate terms and fees. Businesses evaluating financial treatment can review considerations for perpetual software license accounting.
A subscription license provides access for a defined term, often with recurring fees. The agreement should explain renewal, price changes, suspension, termination, data export, and what happens when the subscription ends. Hosted software may also involve service levels, privacy, security, and availability terms. A SaaS software license agreement often addresses these issues alongside access rights.
Usage-based licensing calculates fees using consumption, such as transactions, storage, processing, or another defined unit. Check how the vendor measures usage, resolves disputed calculations, applies overages, and changes rates.
Deployment models establish who or what may access the software. Named-user licenses follow designated individuals. Device licenses cover specified machines. Concurrent licenses limit simultaneous users. Server or processor licensing measures infrastructure. Site and enterprise licenses cover defined locations or organizations. An OEM license may bind software to particular hardware, as explained in this overview of OEM software license agreements.
Compare models using your actual workforce, shared devices, expected growth, remote access, contractor use, and technical architecture. The least expensive headline price may not fit your deployment.
Choosing a License for Software You Will Distribute
If you create software, start with your commercial and distribution goals. A proprietary license may fit a product whose source code and modification rights you want to control. A permissive open-source license may encourage adoption and allow broad commercial reuse. A copyleft license may fit a project intended to remain open when distributed in modified form.
Review ownership before selecting terms. Confirm that employees and contractors have assigned necessary rights and that third-party components permit your planned distribution. Maintain a component inventory recording license names, versions, notices, and source-code obligations. A convenient license label cannot cure missing ownership or incompatible third-party terms.
Dual licensing allows the same software to be offered under alternative licenses. MySQL, for example, is available under the GPL and under commercial licensing arrangements. A user selects the route appropriate to its intended use and obligations. Hybrid models may combine open-source components with proprietary modules, paid features, hosted services, or support. "Source available" is another distinct approach: users may inspect source code, but restrictions can prevent the license from qualifying as open source.
Your customer agreement should define permitted users, environments, copies, modifications, integrations, backups, and transfers. It should also address ownership, confidentiality, warranties, liability, termination, support, and dispute procedures. Use a software license agreement checklist to organize the review, but tailor the terms to the product and delivery model.
If your company is selecting distribution terms, combining third-party code, negotiating enterprise rights, or responding to a suspected violation, you can post your legal need on UpCounsel's marketplace. An attorney can analyze license compatibility, identify source-code, redistribution, and deployment duties, and draft or negotiate the governing agreement. Responses typically arrive within a day, helping you address the issue before release, renewal, or escalation.
Software License Compliance Checklist
Software license compliance requires more than recording what your company paid. You must compare actual users, devices, installations, environments, and consumption with the rights your organization purchased.
- Collect the governing documents. Keep the signed agreement, order forms, product terms, amendments, renewal notices, and proof of purchase together.
- Record license metrics. Document users, devices, servers, processors, locations, affiliates, contractors, and usage limits covered by each license.
- Track installations and access. Reconcile deployments with entitlements. Remove accounts for departed workers and review shared credentials or unapproved installations.
- Control open-source intake. Require developers to identify third-party components and preserve required notices. Review distribution plans before release.
- Calendar contract events. Monitor renewal windows, notice requirements, maintenance periods, usage reviews, and termination procedures.
- Review changes. Recheck licensing when you move software to the cloud, add affiliates, use contractors, virtualize servers, replace hardware, or launch a customer-facing product.
Pay special attention to audit clauses. They may establish notice procedures, recordkeeping requirements, verification rights, confidentiality protections, and responsibility for audit costs. Do not assume a vendor's initial interpretation is correct. Compare any claimed shortfall with the contract definitions and deployment records.
If you discover a possible overdeployment or prohibited use, preserve relevant records and limit further expansion while you assess the issue. Unlicensed copying or distribution can create contractual and intellectual property exposure. This overview of software license violation penalties explains why early review matters.
Frequently Asked Questions
What Are the Most Common Software Licenses?
The most common categories are proprietary licenses and open-source licenses, including permissive and copyleft forms. Businesses also frequently encounter freeware, shareware, subscription, perpetual, named-user, device, concurrent-use, and enterprise arrangements. These labels answer different questions, so one product may fall under several categories at the same time.
What Are the Four Main Types of Software Licenses?
There is no universally accepted set of four software license types. A simplified list may identify proprietary, open-source, freeware, and shareware, while another list may separate permissive, copyleft, public-domain, and proprietary software. The correct classification depends on whether the list addresses source-code rights, price, duration, or deployment.
What Are the Six Types of Creative Commons Licenses?
The six Creative Commons licenses are CC BY, CC BY-SA, CC BY-ND, CC BY-NC, CC BY-NC-SA, and CC BY-NC-ND. They combine attribution, share-alike, no-derivatives, and noncommercial conditions in different ways. Creative Commons licenses are commonly used for creative content and are not the default choice for licensing software code.
How Can I Tell What Type of License Software Uses?
You can identify the license by checking the purchase agreement, order form, product terms, EULA, in-product notices, repository files, or accompanying documentation. For open-source components, look for files named LICENSE, COPYING, or NOTICE. Do not rely only on a sales page, because separate terms may govern particular versions, features, or distribution channels.
Can Open-Source Software Be Used in a Commercial Product?
Yes, open-source software can generally be used for commercial purposes, subject to its license conditions. Commercial use is different from unrestricted redistribution. Depending on the license and product design, you may need to retain notices, provide license text, disclose covered source code, document modifications, or offer required installation information to recipients.
