Proprietary software, also known as closed-source software, is software whose owner retains exclusive legal control over its use, copying, modification and distribution, and grants users only the limited rights written in a license. In software licensing, it is the counterpart of free and open source software: the user typically receives a right to run the program, not ownership of it, and the source code is usually withheld.
The word proprietary refers to ownership rights, mainly copyright and sometimes patents and trade secrets, not to price. Proprietary software can be expensive, subscription-based or entirely free of charge, as long as the owner keeps the decisive restrictions in place.
How proprietary licensing works
Proprietary software rests on the fact that copyright applies to code automatically. Without permission, nobody may copy, adapt or distribute a program, so the owner grants permission selectively through a license agreement. For consumer products this is usually an EULA, an end-user license agreement accepted at installation; for businesses it is often a negotiated master agreement with order forms.
Several protective layers usually work together. Copyright covers the code and documentation, trade secret law protects unpublished source code and algorithms, contractual clauses forbid reverse engineering where the law allows such a ban, and technical measures such as license keys and activation enforce the terms in practice.
| Aspect | Typical proprietary position | Practical consequence |
|---|---|---|
| Use | Permitted within defined limits | Seat, device or user counts apply |
| Source code access | Not provided | Users cannot inspect or fix the code |
| Modification | Prohibited | Customization only through settings or APIs |
| Redistribution | Prohibited without permission | Copies may not be shared or resold |
| Reverse engineering | Prohibited where legally possible | Limited exceptions for interoperability in some jurisdictions |
| Warranty and liability | Narrowly limited | Remedies often capped at the fees paid |
Common proprietary license models
Proprietary software is sold through several commercial license models, and the model often matters more to a buyer’s budget than the list price. The main question is whether the customer pays once for a perpetual license or keeps paying for continued access.
| Model | How it is charged | Typical fit |
|---|---|---|
| Perpetual license | One payment, optional maintenance fee | Stable desktop or on-premises software |
| Subscription | Monthly or annual fee | Cloud services and continuously updated tools |
| Per-user or per-seat | Fee per named or concurrent user | Office and collaboration software |
| Per-core or per-device | Fee per processor core or machine | Databases and server software |
| Freemium | Free basic tier, paid premium features | Consumer and small-business apps |
| Freeware | No charge, rights still restricted | Utilities and reader applications |
Software delivered as a service blurs the picture, because the customer never receives a copy at all. The SaaS terms of service then play the role of the license, and the provider controls the software completely, including when features change or disappear.
Proprietary software compared with open source and free software
The difference between proprietary and open source software lies in which rights the license grants, not in quality, security or cost. Open source licenses such as the MIT License, Apache License or GPL guarantee rights to study, modify and redistribute the code, while proprietary licenses reserve those rights to the owner.
| Criterion | Proprietary software | Open source software |
|---|---|---|
| Source code | Usually closed | Publicly available |
| Right to modify | Reserved to the owner | Granted to every licensee |
| Support | From the vendor under contract | Community, vendors or in-house staff |
| Vendor dependency | High | Lower, others can maintain forks |
| Cost structure | License fees plus services | Mainly integration and support costs |
The boundary is not always sharp. Under dual licensing, the same code is offered both under an open source license and under a commercial proprietary license. Many proprietary products also embed open source components, which requires the vendor to respect those components’ license obligations, especially the copyleft terms of the GPL family.
A further category, source-available software, sits between the two. The vendor publishes the code for inspection, auditing or limited modification, but the license still restricts commercial use, competing services or redistribution. Licenses of this kind do not meet the Open Source Definition, so the software remains proprietary in legal terms even though anyone can read its code.
License compliance and audits
Proprietary vendors enforce their terms through contractual audit rights, which allow them to verify installations, user counts or processor cores, typically once a year with written notice. An audit compares deployed software against purchased entitlements, and any shortfall is usually billed at list price, sometimes with back-dated maintenance fees.
Organizations manage this exposure with software asset management: an inventory of installations, a record of entitlements and regular reconciliation between the two. Virtualization and cloud migration are common triggers for unintended under-licensing, because some server licenses count all physical cores a virtual machine could run on, not only the cores it actually uses.
Benefits, risks and practical choices
Organizations choose proprietary software mainly for accountable vendor support, integrated features and certification, for example in regulated industries that require a supplier to stand behind a product. The vendor’s control also allows a consistent product roadmap and a single party responsible for fixes.
The main risk is vendor lock-in: data formats, integrations and staff skills become tied to one supplier, and switching costs rise year after year. Buyers reduce that risk with data export guarantees, open file formats, source code escrow for critical systems and clear terms on price increases and end of support.
- Count licenses carefully: per-core or per-user metrics are a frequent source of costly audit findings.
- Read the termination clauses: subscription software may stop working, and data access may end, when payments stop.
- Check transfer rights: many licenses cannot be moved to a new company owner or resold.
- Track open source inside the product when building proprietary software, so that copyleft obligations are met.
A non-technical view
Proprietary software is software that someone else owns, even after you pay for it. Buying it is a little like buying a ticket to a cinema. You may watch the film, but you may not copy it, change it or show it to others.
The company keeps the recipe, meaning the source code, to itself. You get permission to use the program under its rules, and those rules are written in the license you accept when you install or sign up.
A concrete example
A mid-sized engineering firm with 120 staff runs its design work on a proprietary computer-aided design package licensed per named user on an annual subscription. The license allows installation on two devices per user, prohibits reverse engineering and limits the vendor’s liability to the fees paid in the previous twelve months.
During a license review, the IT manager finds 14 inactive accounts still being billed and an internal script that extracted data through an undocumented interface, which the terms prohibit. The firm removes the unused seats, saving more than ten percent of the annual cost, replaces the script with the vendor’s supported API and negotiates a clause guaranteeing full data export in an open format if the contract ends.