When you install Microsoft Windows or Adobe Photoshop, you’re operating under a strict set of rules – you cannot look at how the software is built, you cannot modify it, and in most cases, you cannot even share it. On the other hand, when you use Linux or LibreOffice, you’re free to examine, tweak, and redistribute the software as you please. This fundamental divide between free software and proprietary software is not just a technical distinction – it is a deeply philosophical and legal one, with significant implications for users, developers, businesses, and governments alike, including in India.
Table of Contents
- What does “free” actually mean in free software?
- What is proprietary software?
- The core differences: a side-by-side view
- Source code access
- Licensing framework
- User control and vendor dependency
- Cost structure
- Security and transparency
- The philosophical divide
- Free software and proprietary software in the Indian context
- Hybrid models and practical reality
What does “free” actually mean in free software?
The word “free” here is routinely misunderstood. As the Free Software Foundation (FSF) clearly states, free software is a matter of freedom, not price. The FSF, founded by Richard Stallman in 1985, defines free software around four essential freedoms:
- Freedom 0: The freedom to run the program for any purpose.
- Freedom 1: The freedom to study how the program works and adapt it to your needs – which requires access to the source code.
- Freedom 2: The freedom to redistribute copies so you can help others.
- Freedom 3: The freedom to improve the program and release those improvements to the public, so the whole community benefits.
These four freedoms, as documented by Britannica, are what legally and philosophically define software as “free.” A program that denies even one of these freedoms to its users is, by this definition, non-free. Importantly, free software can be sold commercially – charging money for it does not make it proprietary. What matters is whether the user has these freedoms, not the price tag.
What is proprietary software?
Proprietary software – also called closed-source software – is software where the creator retains exclusive legal control over it through copyright, patents, and restrictive licensing. As Wikipedia explains, proprietary software grants its creator a legal monopoly that excludes users from freely sharing or modifying it. The source code is kept secret, and users interact only with the compiled, executable version of the software.
Common examples include Microsoft Windows, macOS, Adobe Creative Cloud, and Oracle Database. Users of these products never see the underlying code. They cannot alter how the software works, cannot legally redistribute it to others, and have no recourse if the software does something they don’t want – except to stop using it entirely.
The core differences: a side-by-side view
Source code access
This is the most fundamental difference. Free software requires that the source code be made available to users – Freedoms 1 and 3 both depend on it. Without source code, studying or modifying software is practically impossible. Proprietary software deliberately withholds source code. As summarised by Shiksha, the source code of proprietary software is kept secret, which allows the owner to control how it is used, distributed, and modified.
Licensing framework
The legal instruments governing these two types of software reflect their opposing philosophies. Free software is typically released under licenses like the GNU General Public License (GPL), which use copyright law in a creative inversion – rather than restricting use, the GPL legally guarantees the four freedoms. It also includes a copyleft provision, which means any modified version of the software must also be distributed under the same free terms. This prevents anyone from taking free software and converting it into something proprietary.
Proprietary software, by contrast, uses End User License Agreements (EULAs) that spell out what users cannot do. These agreements typically restrict the number of devices on which the software can be installed, prohibit reverse engineering, ban redistribution, and allow the vendor to modify terms unilaterally. As ETB Law notes, violating these terms can result in serious legal and financial consequences for individuals and businesses.
User control and vendor dependency
Free software places control firmly with the user. If a program doesn’t meet your needs, you can modify it yourself or commission a developer to do so. If the original developer abandons the project, the community can “fork” the code – take it in a new direction independently. This is why Linux, for example, has remained continuously developed for over three decades without depending on any single company.
Proprietary software creates what economists call vendor lock-in. Relia Software explains that once an organization deeply integrates a proprietary solution into its operations, switching to another platform becomes prohibitively expensive – both financially and operationally. If the vendor discontinues the product, raises prices, or changes its terms, users have very limited options.
Cost structure
The cost comparison is not as straightforward as it may seem. Free software usually involves no upfront licensing fees – but customization, integration, and support may still carry costs. Proprietary software often has significant upfront costs (purchase price or subscription fees), though these typically include vendor support and maintenance. Heavybit’s analysis points out that around 45% of all software tools used by companies today are still proprietary, suggesting that the cost structure of proprietary software continues to offer value in specific contexts – particularly where dedicated vendor support is essential.
Security and transparency
Free software allows anyone to audit the source code for vulnerabilities, which means bugs are often caught and fixed rapidly by a large developer community. However, this same transparency means that attackers can also study the code for weaknesses. Proprietary software operates as a “black box” – its code is not publicly visible, which reduces certain exposure risks, but also means users must trust the vendor entirely when it comes to security practices and data handling.
The philosophical divide
Beyond the technical and legal differences lies a fundamental divergence in philosophy. The free software movement, led by the FSF, treats software freedom as an ethical imperative – a matter of social justice and user rights. As the FSF articulates, distributing software under restrictive terms gives those with source code power over those without it, creating an inherent imbalance. Free software is the movement’s answer to that imbalance.
Proprietary software, on the other hand, operates on a commercial model where the source code is the core business asset. Companies like Microsoft argue that per-copy fees and protected code maximize the investment available for research and development, resulting in more polished, stable, and feature-rich products for end users. Both positions have legitimate arguments – the debate ultimately comes down to whether you prioritize user autonomy or product quality and vendor support.
Free software and proprietary software in the Indian context
For Indian students of law and IPR, this distinction has direct policy significance. Under the Indian Copyright Act, 1957 (as amended), software is protected as a literary work. This means that both free and proprietary software are subject to copyright – the difference lies in how that copyright is exercised. Proprietary developers use copyright to restrict use; free software developers use it to guarantee freedoms through copyleft licensing.
India’s government has taken a clear position in favour of free and open-source software in public administration. According to a Press Information Bureau release, the Government of India issued a Policy on Adoption of Open Source Software in 2015 under the Ministry of Electronics and Information Technology (MeitY), directing all government organizations to prefer free and open-source solutions over proprietary ones when building e-governance systems. Major national projects such as Aadhaar and UPI were built using FOSS infrastructure. MeitY has also launched the #FOSS4GOV Innovation Challenge to further accelerate the adoption of open-source technologies in health, education, agriculture, and urban governance.
The rationale behind this policy preference is not merely financial. Research by the Centre for Internet and Society India highlights that proprietary software creates dependency on foreign vendors, which poses risks to data sovereignty – India’s ability to keep control of its citizens’ data within national jurisdiction. Free software, by contrast, allows full auditing of how data is handled and eliminates dependence on vendors subject to foreign legal obligations.
Hybrid models and practical reality
The real-world software landscape is rarely a clean binary. Many software products use dual licensing – releasing code under both a free software license and a commercial proprietary license, giving developers options. MySQL is a well-known example. There is also the category of freeware – software that is free of charge but not free in the FSF sense, as it remains proprietary and does not give users access to source code or modification rights. Confusing freeware with free software is a common mistake with real legal consequences, particularly when choosing tools for institutional or legal work.
The GNU Project’s categorization of software types makes clear that non-copylefted free software can actually be incorporated into proprietary products – meaning that the absence of copyleft does not automatically protect software freedom across all derivative works. This is precisely why the GPL’s copyleft clause was designed the way it was: to ensure that freedom, once granted, cannot be taken away in subsequent redistributions.
What do you think? Given India’s policy preference for free and open-source software in government systems, should Indian courts adopt stronger enforcement mechanisms for copyleft license violations under the Copyright Act, 1957? And from a user empowerment perspective, do you believe that the four freedoms defined by the FSF are sufficient to address all ethical concerns around modern software – or does the growing role of AI and data processing demand a redefinition of what “software freedom” means today?
References
- https://www.gnu.org/philosophy/free-sw.en.html
- https://www.britannica.com/science/free-software
- https://en.wikipedia.org/wiki/Proprietary_software
- https://www.shiksha.com/online-courses/articles/difference-between-open-source-software-and-proprietary-software-blogId-153109
- https://www.etblaw.com/open-source-vs-proprietary-software/
- https://reliasoftware.com/blog/difference-between-open-source-and-proprietary-software
- https://www.heavybit.com/library/article/open-source-vs-proprietary
- https://www.fsf.org/bulletin/2019/fall/building-ethical-software-based-on-the-four-freedoms
- https://www.pib.gov.in/PressReleasePage.aspx?PRID=1713452
- https://cis-india.org/openness/files/state-of-openness-in-indias-e-governance
- https://www.gnu.org/philosophy/categories.en.html
Leave a Reply