Software Licenses Types Explained
A software license defines what you are permitted to do with software. Depending on the license, you may be able to run a program, inspect its source code, modify it, and redistribute copies. A separate commercial agreement may govern how long a product or service is available to you, how many users can access it, and which features are enabled.
For networking students, the distinction matters. Open-source, source-available, and proprietary licensing describe different permissions and restrictions on software. Terms such as perpetual, subscription, floating, and metered describe commercial access and entitlement models. A product can involve both types of terms, but the rules for a hosted service or proprietary add-on do not remove the permissions already granted under an open-source license.
In this tutorial, I'll explain the main software license families, show how seat and feature licensing work, and demonstrate commands that help you inspect license information on Linux and Cisco devices.
What Is a Software License?
A software license grants rights under copyright and, in some cases, other intellectual property laws. It does not normally transfer ownership of the software's copyright. For example, purchasing a perpetual license for a network management tool may let you keep using a specified version, but it does not automatically authorize you to modify its source code or redistribute copies. The exact rights depend on the agreement.
Installed commercial software often uses an End-User License Agreement (EULA). Cloud platforms may use Terms of Service (ToS) or a subscription agreement. Open-source projects generally publish license terms alongside their source code. Similar marketing labels do not guarantee identical legal conditions, so always check the applicable license and contract.
Two Layers of Software Licensing
To understand how a product is licensed, ask two questions:
- What may you do with the software or source code? An Open Source Initiative (OSI)-approved open-source license grants rights to use, inspect, modify, and redistribute the covered software, subject to license conditions. It cannot prohibit commercial fields of use. Proprietary licenses commonly limit source-code access, modification, or redistribution. Some source-available licenses disclose code but impose restrictions that do not meet the Open Source Definition.
- How is access to a commercial product or service managed? Vendors may apply subscription periods, named-user or concurrent seats, consumption charges, and feature entitlements. These terms can govern proprietary products, hosted services, support offerings, and commercial add-ons.

The bottom banner illustrates how a commercial product may combine these layers. OSI approves licenses, not individual pieces of software code. Access limits imposed by a hosted service or separate commercial agreement should not be confused with restrictions written into the OSI-approved license for covered open-source code.
Open-Source, Source-Available, and Public Domain
Open source does not necessarily mean free of charge. You can sell copies of open-source software, and recipients still receive the permissions required by its license. Open-source licenses also carry conditions, especially when you distribute modified or combined software.
The following spectrum is a simplified teaching aid, not a universal legal ranking. License obligations differ in more than one dimension. For example, the GNU GPL permits commercial use even though it imposes copyleft conditions on the distribution of covered works.

Public Domain, CC0, and Creative Commons
Public domain is a copyright status, not a license. A work can enter the public domain when copyright expires, when it is not eligible for copyright protection, or when a valid dedication or waiver applies. Rules differ by jurisdiction.
Creative Commons Zero (CC0) is a public-domain dedication tool. It attempts to waive copyright and related rights where legally possible and provides fallback permissions where a complete waiver is not possible. CC0 does not grant patent rights, and CC0 itself is not an OSI-approved software license. Check any relevant patent, trademark, and third-party rights separately.
Other Creative Commons (CC) licenses, including CC BY and CC BY-SA, are useful for tutorials, documentation, diagrams, and other creative material. Creative Commons recommends software-specific licenses for program code because its standard CC licenses do not address source-code and object-code distribution in the same way.
Permissive Licenses: MIT, BSD, and Apache 2.0
Permissive licenses generally let you use, modify, and redistribute code, including in proprietary products. You can usually keep your own separate additions under another license, provided you meet the conditions of the original license.
- MIT License: Retain the required copyright notice and license text in copies or substantial portions of the software.
- BSD Licenses: Preserve the notices required by the particular BSD variant. The three-clause BSD license also restricts using contributors' names to endorse derived products without permission.
- Apache License 2.0: Include required license and notice information, identify modifications to covered files, and comply with its express patent-license and patent-termination provisions.
Permissive does not mean obligation-free. You must still preserve the notices required by the license you received.
Weak Copyleft Licenses: GNU LGPL, MPL 2.0, and EPL 2.0
Weak copyleft licenses require you to preserve specified freedoms for covered components, but their scope differs. You cannot treat LGPL, MPL, and EPL as three versions of the same file-level rule.
- GNU Lesser General Public License (LGPL): Commonly used for libraries. A separate application can often link to an LGPL-covered library without adopting the LGPL for the whole application, provided the applicable conditions are satisfied. When distributing a combined work, you may need to supply notices, the library's corresponding source, and a way for recipients to replace or relink a modified version of the library. A suitable shared-library mechanism may satisfy some of these obligations. Static linking commonly requires additional relinking materials. Details depend on the LGPL version and distribution method.
- Mozilla Public License 2.0 (MPL 2.0): Uses file-level copyleft. Modifications to MPL-covered files, and new files containing covered MPL code, remain subject to MPL requirements when distributed. Separate files that do not contain MPL-covered code can generally use another license in a larger work.
- Eclipse Public License 2.0 (EPL 2.0): Defines a covered Program, Contributions, and Modified Works. Its source-availability obligations apply according to those definitions, not merely according to whether a filename is new or existing. A separate work may have its own license, but you must examine whether it incorporates covered EPL material.
For an exam or a real deployment, I recommend remembering the principle first: look at the boundaries of the covered component and the license's definition of a derivative or modified work. A proprietary application does not automatically become open source just because it uses a weak-copyleft dependency. The conditions still matter.
Strong Copyleft Licenses: GNU GPL and GNU AGPL
Strong copyleft licenses generally require that a covered combined or derivative work, when conveyed to recipients, be licensed under the applicable copyleft terms and accompanied by access to its corresponding source code. The scope of the covered work must be assessed in the circumstances. Merely placing separate programs on the same storage medium does not necessarily make them one covered work.
- GNU General Public License (GPLv2 and GPLv3): Distribution or conveying a covered work activates source-code and redistribution obligations. The Linux kernel is licensed under GPLv2-only terms. GPLv3 adds more explicit patent provisions and, in specified cases involving covered software conveyed in a User Product, requirements to provide installation information needed to run modified versions. This is narrower than a blanket rule against all hardware locking.
- GNU Affero General Public License (AGPLv3): Contains GPLv3-like distribution rules plus a requirement addressing certain modified versions used to interact with users over a computer network. Those users must be offered access to the corresponding source of the modified version as the license requires, even if no software copy is transferred to them.
License compatibility is a separate issue. Apache License 2.0 code can generally be incorporated into a GPLv3-covered combined work, but Apache 2.0 is not compatible with GPLv2-only code in that way. Check whether a GPL project permits use under a later version before combining code.
Exam Alert — Distribution Versus Internal Use: Ordinary GPL obligations do not require you to publish private modifications simply because you use the software within your organization. Distribution changes the analysis. The AGPL additionally addresses qualifying network interaction with modified AGPL software. Neither rule means that every private change must be published to the entire public.
Source-Available Licenses and the No-License Trap
Source-available software lets you view code but may restrict activities such as competing hosted services. A license that discriminates against a commercial field of use does not satisfy the OSI Open Source Definition. The exact restriction depends on the license.
For example, HashiCorp adopted the Business Source License 1.1 (BSL 1.1) for specified Terraform-related releases, while MongoDB uses the Server Side Public License (SSPL) for relevant releases. BSL can impose an additional-use restriction until a specified change date. SSPL imposes separate obligations when the licensed program is offered as a service. They are not interchangeable rules.
Redis needs a version-specific explanation: Redis Community Edition 7.4 was offered under source-available RSALv2 and SSPLv1 terms. Redis Open Source 8 and subsequent versions offer AGPLv3 as an OSI-approved option alongside RSALv2 and SSPLv1. Do not classify every current Redis version as exclusively source-available.
Exam Alert — No License: If code is publicly visible but does not carry a license or another applicable grant of permission, normal copyright protections still apply. On GitHub, the platform's Terms of Service permit certain activities such as viewing and forking public repositories. They do not give you unrestricted permission to copy, modify, and redistribute that code in your own product. Check the license before reuse.

Software Permission Families at a Glance
| Category | Examples | Practical rule to remember |
|---|---|---|
| Public domain or dedication | Public-domain works, CC0 | Verify the status or dedication and check third-party rights. CC0 is not an OSI-approved software license. |
| Permissive open source | MIT, BSD, Apache 2.0 | Preserve required notices and comply with license-specific conditions. |
| Weak copyleft | GNU LGPL, MPL 2.0, EPL 2.0 | Meet obligations for covered libraries, files, programs, or contributions as each license defines them. |
| Strong copyleft | GNU GPLv2/v3, GNU AGPLv3 | Covered combined works carry copyleft obligations when conveyed. AGPLv3 also addresses qualifying network interaction with modified software. |
| Source-available, non-OSI | BSL 1.1, SSPL | Source may be visible, but license-specific restrictions prevent OSI approval. |
| Proprietary or no express reuse license | Commercial EULA, code with no license grant | The rights holder controls permitted copying, modification, and redistribution, subject to applicable law and any other permission. |
Proprietary Access and Enforcement Models
Commercial licensing commonly combines three dimensions: duration, assignment, and usage or features. These are practical ways to organize entitlements, not mutually exclusive legal license families. A five-seat subscription, for instance, has both a duration limit and an assignment or concurrency rule.
1. Duration: How Long You Can Use the Product
- Perpetual license: Grants ongoing rights to use the covered software under the agreement, sometimes for a particular version or edition. Upgrades, patches, and support may be sold separately.
- Subscription or term license: Grants rights or service access for an agreed period. Renewal and expiration terms vary. Some products retain limited functionality after expiration, so do not assume every subscription stops working in the same way.
- Trial or evaluation license: Provides restricted-duration or restricted-feature access for evaluation. Some trials prohibit production use, while others allow it under defined conditions. Read the vendor's evaluation terms.
2. Assignment: Who or What Can Use It
- Named-user license: Assigns a seat to an identified person. A seat does not usually become available to somebody else just because the assigned user is temporarily offline. Reassignment rules depend on the contract.
- Device-based license: Associates the entitlement with a device or another defined machine identifier. It is different from a named-user license even when both use fixed assignments.
- Floating or concurrent license: Limits how many eligible users or sessions can use the product simultaneously. A license server may manage the pool, although the exact enforcement design varies.
Suppose 10 engineers share five concurrent seats. Users 01 through 05 have active sessions, so all seats are occupied. When User 06 attempts to connect, the product may queue or deny that session until a seat becomes free. With five named-user seats assigned to Users 01 through 05, User 06 normally cannot borrow an unused assignment, even when Users 04 and 05 are offline.

The diagram illustrates one possible enforcement policy. Queuing behavior, grace periods, reassignment rights, and license-server handling are product-specific.
3. Usage, Features, and Eligibility
- Metered or consumption-based licensing: Charges or limits use according to a measurable quantity, such as API requests, gigabytes processed, or compute hours.
- Use-time licensing: Measures actual time of use or processing time instead of only a calendar subscription period. Some vendors treat it as a type of metered licensing.
- Feature-based licensing: Enables designated capabilities or editions, such as advanced telemetry, security, or automation features.
- Academic or educational licensing: Limits eligibility or permitted activities to qualifying students, educators, institutions, or educational work. Exact verification and commercial-use rules vary.
Quick Comparison of Commercial Access Models
| Model | Typical limit | Example |
|---|---|---|
| Perpetual | Rights under a specified product agreement | Continue using a purchased software version after support ends. |
| Subscription or term | Contract period | Annual access to a hosted network-monitoring platform. |
| Trial or evaluation | Time, features, or permitted purpose | Time-limited software test under the vendor's evaluation terms. |
| Concurrent or floating | Simultaneous use | Five active seats shared among 10 engineers. |
| Named user | Assigned person | Five accounts licensed to five specific administrators. |
| Device based | Assigned device | An entitlement associated with one appliance or host. |
| Metered or use-time | Requests, data, or active hours | API-call allowance or consumed processing hours. |
| Feature based | Enabled capabilities | Advanced analysis enabled in a higher product tier. |
| Academic | User eligibility or purpose | A discounted edition for verified students. |
How Both Layers Work in Production
You can encounter open-source code permissions and commercial entitlements in the same environment. Two examples are especially useful for networking administrators.
Example 1: Red Hat Enterprise Linux Package Licenses and Subscriptions
Red Hat Enterprise Linux (RHEL) includes many individually licensed open-source packages. On a particular system, RPM metadata may list licenses such as GPL-3.0-or-later for bash, MIT for expat, or MPL-2.0 for nss. The precise license strings depend on the package builds and RHEL release. In particular, OpenSSL licensing differs between older and newer OpenSSL versions, so do not assume that every RHEL release reports Apache-2.0 for openssl.
Red Hat also supplies enterprise subscription services, updates, repositories, and support under its commercial terms. These do not cancel the open-source licenses of the individual packages. An EULA file may be present on an installed RHEL system, but its location can vary.

The screenshot demonstrates how RPM package metadata identifies the licenses associated with installed software. The rpm -q command queries the four specified packages, while the second command displays an excerpt from the locally installed Red Hat EULA.
# Query licenses for four installed RPM packages
rpm -q --qf '%-16{NAME} %{LICENSE}\n' bash openssl expat nss | sort
# Review a local RHEL EULA if this file is installed
head -n 8 /usr/share/redhat-release/EULA
# Confirm the registration identity of a RHEL system
subscription-manager identity
# Inspect enabled Red Hat content repositories
subscription-manager repos --list-enabled
rpm -q reads package metadata. It does not establish whether your organization has an active support subscription. Similarly, subscription-manager identity checks registration, not the number of paid subscriptions held by the organization. In environments using Simple Content Access (SCA), subscription-manager status may report Disabled even when the system is registered and entitled to access configured content. Use registration, repository, and account-level information together when investigating subscriptions.
Example 2: Cisco IOS Feature and Evaluation Licensing
On some older Cisco IOS platforms, the show license feature command lists technology-package features and columns such as Enforcement, Evaluation, Subscription, Enabled, and RightToUse.

show license feature lists feature and licensing capabilities, while show license detail confirms a permanent ipbasek9 license and an active securityk9 evaluation license. The detail output is cropped after securityk9.In this Packet Tracer example, ipbasek9 and securityk9 show Enabled: yes, while datak9 and uck9 show Enabled: no. The feature-summary values alone cannot prove an active evaluation. However, the accompanying show license detail output reports License Type: Permanent and License State: Active, In Use for ipbasek9, and License Type: Evaluation and License State: Active, In Use for securityk9. The displayed evaluation period of 208 weeks and 2 days is simulated and should not be presented as the typical duration of an evaluation license on physical Cisco equipment. Actual license states and expiration behavior depend on the platform and software release.
! Legacy Cisco IOS platform with technology-package licensing
show license feature
show license detail
show license all
Commands and output differ by platform and release. This Packet Tracer screenshot illustrates legacy IOS licensing behavior and is not a universal description of Cisco licensing today.
Modern Cisco IOS XE: Smart Licensing Using Policy
On supported Cisco Catalyst 9000 switches running relevant IOS XE 17.x releases, Smart Licensing Using Policy (SLP) manages license usage and reporting. A common licensing structure pairs a perpetual Network Essentials or Network Advantage base tier with a term-based Cisco DNA Essentials or Cisco DNA Advantage entitlement. Available tiers, names, and reporting requirements vary by product and software version, so do not apply this exact model to every IOS XE router or every newer release.
Cisco also documents a unified Cisco Switching Licensing model starting with IOS XE 26.2.1 on Catalyst 9000 switches, using Essentials and Advantage tiers. This newer model should be distinguished from the 17.x base-license and DNA add-on structure described above.
Useful verification commands on platforms that support them include:
show license summary
show license all
Review the output alongside the hardware model, software release, and the relevant Cisco licensing guide. A feature being enabled is not always equivalent to proof of purchased entitlement or completed licensing reporting.
Key Takeaways
Software licensing becomes much easier to understand when you separate rights in the code from terms governing commercial product or service access.
- Open-source permissions: MIT, BSD, and Apache 2.0 are permissive. LGPL, MPL 2.0, and EPL 2.0 impose narrower copyleft obligations, but their definitions and boundaries differ. GPL and AGPL apply stronger copyleft rules to covered works, with AGPL also addressing specified network interaction.
- Other categories: Public domain is a legal status. CC0 is a dedication tool, not an OSI-approved software license. Source-available code is not automatically open source, and code without a license grant is not automatically free to reuse.
- Commercial access: Perpetual, subscription, concurrent, named-user, device-based, metered, feature-based, and academic terms answer different questions. Vendors may combine several in one offering.
- Verification: Use
rpm -qto inspect Linux package license metadata,subscription-manager identityto check RHEL registration, and platform-appropriateshow licensecommands to investigate Cisco licensing. Never treat one field or command as definitive proof of every entitlement.
Official References
The following sources are useful when you need to check the exact wording of a license or verify platform-specific behavior:
- Open Source Initiative — The Open Source Definition
- Creative Commons — Frequently Asked Questions
- Mozilla — MPL 2.0 FAQ
- Eclipse Foundation — EPL 2.0 License
- GNU Project — Frequently Asked Questions about the GNU Licenses
- Apache Software Foundation — Apache 2.0 and GPL Compatibility
- Redis — Current Open Source Licensing Options
- GitHub Docs — Licensing a Repository
- RPM Project — rpm(8) Manual
- Red Hat — Simple Content Access
- Cisco — Catalyst 9000 Licensing White Paper
Author Laxmi Goswami Updated on 2026-11-21