Recommended Free Tools
Software licensing is not one decision. A product can be proprietary or open source, installed locally or delivered as SaaS, licensed per person or device, and paid for upfront, periodically, or by consumption. The safest way to compare options is to separate four questions: what legal rights you receive, where the software runs, what is counted, and when or how you pay.
This guide explains those layers, the cost and compliance consequences, and the questions to ask before buying, building, embedding, or redistributing software. Contract language and legal results vary by product, jurisdiction, and transaction, so treat this as practical education rather than legal advice.
As an Amazon Associate I earn from qualifying purchases.
What is a software license?
A software license is permission from a copyright owner or other rights holder to use, copy, modify, distribute, access, or embed software under stated conditions. A buyer normally receives defined rights, not ownership of the copyright or unrestricted ownership of the software itself.
- Owning a laptop or server does not grant rights to run every program on it.
- Owning a purchased copy does not necessarily grant rights to redistribute, reverse engineer, or modify it.
- Access to a hosted application is usually a contractual service right, not possession of the server-side software.
- Source-code access does not automatically include permission to commercialize or redistribute the code.
The agreement may also control user counts, devices, locations, affiliates, upgrades, support, activation, audit rights, termination, and data export. Read the actual product terms for high-value, regulated, embedded, or redistribution use.
The four dimensions of software licensing
Most modern products combine several dimensions rather than fitting one neat category.
| Dimension | Typical choices | Question answered |
|---|---|---|
| Legal rights | Proprietary, open source, source-available, public-domain-like dedication | What may you use, modify, copy, or distribute? |
| Delivery | Desktop, on-premises, self-hosted, SaaS, embedded | Where does the software run? |
| Entitlement metric | Named user, device, concurrent user, site, server, core, tenant, organization | What is counted? |
| Payment and meter | Perpetual, subscription, maintenance, usage, capacity, tier | When and according to what activity do you pay? |
For example, Microsoft 365 is commonly a per-user SaaS subscription, while an on-premises product might be a perpetual license measured by processors and covered by annual maintenance. An open-source project can be free to download while charging for hosting, support, certification, or enterprise features. Microsoft distinguishes subscriptions, licenses, accounts, and tenants, and describes many Azure charges as resource-consumption based: Microsoft’s licensing overview.
Proprietary or commercial licensing
Under a proprietary license, the publisher controls the source code and grants limited contractual rights. Common restrictions prohibit unauthorized copying, redistribution, sublicensing, competitive use, or use above a stated user, device, installation, or location limit. Reverse-engineering restrictions may be limited by local law.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhy buyers choose it
- Vendor accountability, product roadmaps, and commercial support.
- Centralized security updates and administration.
- Possible indemnity, service levels, and contractual remedies.
- A procurement path familiar to finance, legal, and IT teams.
Main risks
- Renewal increases, vendor lock-in, or dependence on activation and identity systems.
- Audit exposure if contractors, former employees, virtual machines, or affiliates are counted incorrectly.
- Limited portability of data, customizations, or integrations.
- Unclear rights after cancellation or product discontinuation.
Adobe says named-user licensing is its default and most common enterprise deployment method: Adobe enterprise licensing.
Perpetual versus subscription licensing
| Issue | Perpetual license | Subscription license |
|---|---|---|
| Payment | Usually a larger one-time fee | Monthly or annual recurring payment |
| Use after cancellation | Often continued use of the defined version, subject to contract and activation | Access commonly ends when the term ends |
| Upgrades | May require paid upgrades or maintenance | May be included, but verify terms |
| Infrastructure | Customer often hosts, patches, backs up, and secures it | Vendor often operates the service, especially with SaaS |
| Best fit | Stable workloads, offline or isolated environments, long-lived systems | Changing headcount, current features, lower initial cost, outsourced operations |
| Key risk | High upfront cost and compatibility responsibility | Renewal increases, continuing payments, and exit dependency |
“Perpetual” normally means indefinite use of a specified version, not free upgrades, support, cloud access, transferability, or compatibility forever. JetBrains documents products that combine a perpetual right to a particular version with an upgrade subscription: JetBrains licensing information.
SaaS licensing: access rather than possession
Software as a Service is primarily a delivery and operating model. The provider hosts and operates the application; customers receive a right to access it. Pricing may be per seat, active user, tier, transaction, API call, storage, data volume, or organization.
Questions to ask before signing
- Can users work offline, and how often must they authenticate?
- Can you export complete, structured data including attachments, metadata, permissions, and audit logs?
- What are the service-level, backup, security, and incident-notification commitments?
- Are APIs rate-limited, and can automated jobs create overage charges?
- May the vendor change features, prices, hosting regions, or data-use practices during the term?
- What happens to production data and backups after cancellation?
Adobe, for example, says named-user licenses require initial activation and connection to Adobe servers at least once every 30 days: Adobe’s licensing documentation. Cloud delivery therefore does not automatically mean uninterrupted offline use.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
User, device, and infrastructure metrics
Named-user or seat licensing
A named-user entitlement is assigned to a person or account, whether or not that person is logged in at every moment. It suits dedicated employees, personalized workspaces, SSO, and accountable audit trails. It can be wasteful for seasonal staff or occasional users, and “user” may include administrators, contractors, guests, or read-only accounts.
Atlassian states that its licenses are based on named users rather than concurrent users; anyone permitted to log in counts, and shared logins are prohibited: Atlassian licensing FAQ.
Device-based licensing
A device license follows a workstation, terminal, kiosk, classroom computer, or other machine. It can suit shared workstations, call centers, laboratories, manufacturing terminals, and public-access computers. Clarify whether virtual machines, pooled desktops, remote access, and replacement hardware count as separate devices. Microsoft identifies device-based licensing for shared and open-access scenarios: Microsoft 365 Apps licensing modes.
Rank #3
- Used Book in Good Condition
Concurrent or floating licensing
A concurrent license limits simultaneous users rather than the total registered population. Twenty seats could serve 100 occasional users if no more than 20 use the software at once. It can reduce cost when peak demand is low, but license-server outages, peak-time contention, disconnected sessions, and remote access complicate operations. Availability is vendor-specific; Atlassian explicitly does not offer concurrent-user licensing.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Site, enterprise, organization, and tenant licensing
These arrangements may cover a site, legal entity, employee population, tenant, or enterprise. “Unlimited” rarely means unlimited in every respect: installations, affiliates, locations, revenue, transactions, or usage may still be capped. Define subsidiaries, contractors, acquisitions, and geographic boundaries. Atlassian Data Center, for example, uses user tiers and product-specific limits.
Server, processor, core, instance, and capacity licensing
Infrastructure metrics attach rights to physical processors, virtual cores, servers, virtual machines, clusters, hosts, storage, or capacity. Virtualization, cloud migration, failover, backups, disaster-recovery systems, and test environments can change the count. Check product-specific terms and Microsoft’s licensing resources: Microsoft commercial licensing portal.
Usage-based and consumption licensing
Metered pricing charges for API requests, compute time, storage, bandwidth, transactions, documents, active minutes, data records, builds, or deployments. It aligns payment with activity and lowers the entry barrier, but forecasting is harder.
- Set budgets, rate limits, alerts, and approval thresholds.
- Measure automated jobs and retry behavior, not just human activity.
- Separate production, test, and disaster-recovery usage.
- Confirm whether overages are blocked, throttled, or billed automatically.
A per-seat plan is predictable but may charge for inactive users. A usage plan can be efficient at low activity yet become expensive when automation, traffic, or data volume grows unexpectedly. Microsoft describes Azure as commonly using resource-consumption pricing: Microsoft cloud licensing overview.
OEM, embedded, white-label, and redistribution licenses
OEM and embedded
OEM software is bundled with hardware; embedded software is incorporated into a device, vehicle, appliance, or industrial system. Terms may set per-device royalties, volume commitments, field-of-use limits, minimum annual royalties, patch obligations, and restrictions on transfer. Clarify who supports customers and who owns modifications.
White-label and redistribution
White-label rights permit rebranding, while redistribution rights permit delivery to your own customers. Confirm ownership of underlying intellectual property and customer data, modification rights, territories, support duties, resale restrictions, and whether the original vendor may sell directly to your customers.
Open-source licensing
Open source concerns legal permissions and obligations, not simply price. The Open Source Initiative says compliant software is accessible, usable, modifiable, and shareable, and may be used commercially: OSI FAQ. Source code that is visible but restricted from commercial use or competing services is not automatically open source; OSI’s definition prohibits restrictions on fields of endeavor: Open Source Definition.
Permissive licenses
MIT, BSD, and Apache-style licenses generally permit broad use, modification, and redistribution while requiring notices and preserving copyright information. Patent, attribution, notice, and trademark provisions differ, so do not treat them as interchangeable. A permissive license may allow a proprietary derivative.
Copyleft licenses
Copyleft requires specified redistributed or modified versions to retain corresponding freedoms. Strong, weak, and network copyleft impose different conditions. The GNU Project explains the principle: GNU copyleft explanation.
Best Value
Private modification is not the same as distribution. The GNU GPL FAQ explains that private modified GPL software need not be released, while distributing a modified version triggers source and licensing obligations under the GPL: GNU GPL FAQ. AGPL analysis depends on the licensed code and how it is used; it does not automatically apply to every web application.
Identify licenses accurately
Check each dependency’s license file, notices, exceptions, and compatibility. SPDX provides standardized identifiers, texts, and canonical URLs: SPDX License List. Trademarks, hosted services, documentation, and data can have separate terms.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Dual licensing and source-available software
Dual licensing offers the same code under two legal regimes, often an open-source license and a commercial license for customers needing proprietary redistribution, different warranty or indemnity terms, or vendor support. It is not the same as offering two subscription tiers; the legal rights must differ.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteSource-available or “fair-code” licenses may publish code while prohibiting competing hosted services, resale, production use without payment, or other commercial activity. Verify the exact restrictions before calling the software open source.
Freemium, freeware, trials, and public-domain dedication
- Freemium: a free tier limited by users, storage, features, support, integrations, retention, or security controls. It usually grants no modification or redistribution rights.
- Freeware: no purchase price, but it may remain proprietary and prohibit copying, modification, or commercial use.
- Trial: time-, feature-, user-, data-, or production-limited evaluation. Do not deploy it in production without checking evaluation terms and export rights.
- Public-domain dedication: attempts to relinquish copyright rights where law permits. Its treatment and warranty consequences differ by jurisdiction and are not identical to an open-source license.
How to choose a licensing model
Choose based on operating reality
- Perpetual: stable workloads, offline or isolated operation, and capacity to run infrastructure.
- Subscription: frequent changes, current-version requirements, lower upfront spending, and acceptance of renewal risk.
- Named user: dedicated people, SSO, and accountability.
- Device: many occasional users sharing a small number of machines.
- Concurrent: a large potential pool, low peak demand, and a vendor that supports true floating seats.
- Usage-based: activity varies substantially and the meter tracks business value transparently.
- Open source: source access, modification, and vendor independence matter and you can meet maintenance obligations.
Total cost of ownership
Compare the full cost rather than the headline price. Your worksheet should include:
- Initial purchase, setup, or migration.
- Recurring subscriptions, minimum commitments, and renewal increases.
- Premium support, implementation, training, customization, and integrations.
- Hosting, infrastructure, administration, security, compliance, backups, and disaster recovery.
- Inactive, seasonal, guest, contractor, or peak users.
- Usage overages, taxes, regional pricing, and currency changes.
- Data migration, export testing, exit assistance, replacement, and reimplementation.
- Audit, true-up, open-source compliance, and remediation exposure.
For a fair comparison, model the same workload under 50 named users, 10 shared devices, 20 concurrent users, and a metered workload. Use the contract’s actual prices and definitions; do not assume that a lower first-year bill is cheaper over the intended life.
Quick Recap
License compliance and exit checklist
- Inventory products, versions, dependencies, installations, users, devices, tenants, and environments.
- Record purchase documents, license keys, notices, exceptions, renewal dates, and usage reports.
- Remove former employees and review contractors, guests, read-only accounts, and shared logins.
- Classify production, development, test, standby, backup, and disaster-recovery systems.
- Review automatic renewal, price-change, audit, suspension, and termination clauses.
- Test a complete data export before you need it, including metadata, relationships, permissions, logs, and attachments.
- For open-source code, maintain a software bill of materials, preserve notices, and check license compatibility.
- Document exceptions and assign an owner for remediation.
Questions to ask before signing
- Exactly what is counted: users, devices, simultaneous sessions, cores, servers, tenants, transactions, storage, or revenue?
- Do affiliates, contractors, guests, acquisitions, and subsidiaries qualify?
- What survives cancellation: a version, data, backups, support, or nothing?
- Are upgrades, security fixes, implementation, training, and premium support included?
- Can the vendor change price, features, usage metrics, hosting region, or data practices during the term?
- What are the export format, API limits, deletion deadlines, backup-retention period, and migration-assistance obligations?
- Are offline use, virtualization, failover, testing, and disaster recovery expressly permitted?
- For open-source components, what notices, source offers, attribution, patent, and redistribution duties apply?
Comparison at a glance
| Model | What is measured or granted? | Best for | Main benefit | Main risk | Typical exit concern |
|---|---|---|---|---|---|
| Perpetual | Right to a defined version | Stable or isolated environments | Potential continued use without renewal | Upfront and infrastructure cost | Activation and compatibility |
| Subscription | Time-limited access | Changing teams and current versions | Lower initial cost | Renewal dependency | Access ends and prices may rise |
| SaaS | Hosted service access | Organizations outsourcing operations | Vendor-managed infrastructure | Provider and identity dependency | Data portability |
| Named user | Assigned people or accounts | Dedicated employees | Clear governance | Inactive-seat waste | User and data offboarding |
| Device | Workstations or terminals | Shared computers | Many users per machine | Multiple-device cost | Reassignment and virtualization rules |
| Concurrent | Simultaneous sessions | Occasional specialist users | Capacity-based savings | Peak contention | License-server dependence |
| Usage-based | Requests, storage, compute, or transactions | Variable workloads | Pay for activity | Bill shocks | Export and metering disputes |
| Open source | Rights to use, modify, and share under license terms | Technical teams seeking control | Flexibility and vendor independence | Compliance and support burden | Migration, maintainership, and notices |
| Dual license | Choice between distinct legal regimes | Commercial embedding and open communities | Flexible distribution rights | Complex compatibility and contributor ownership | Which license applies to each use |
| OEM/embedded | Devices, units, royalties, or field of use | Manufacturers and product vendors | Integrated distribution | Long-term obligations and support | Device lifecycle and patching |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
