Almost every software product is built on open source code. Open source is free to use, but it is not free of conditions. Each component comes with a licence, and breaking its terms can mean losing the right to use the code, a copyright claim, or a difficult conversation with an investor or acquirer.
In India, open source licences are copyright licences under the Copyright Act, 1957. This guide explains the main licence families, the duties they impose, and how to keep a clean record.
Permissive and copyleft licences
Permissive licences let you use, modify and include the code in proprietary products, as long as you keep the copyright and licence notices. Copyleft licences let you do the same, but require that if you distribute the code or works based on it, you do so under the same licence and make the source code available.
| Licence | Type | Main duties | Watch for |
|---|---|---|---|
| MIT | Permissive | Keep the copyright notice and licence text | Very few conditions |
| BSD (2- and 3-clause) | Permissive | Keep notices; 3-clause bars using contributors' names to endorse your product | Older 4-clause version has an advertising clause |
| Apache 2.0 | Permissive | Keep notices, include the NOTICE file, state significant changes | Express patent licence, which ends if you sue over patents in the work |
| LGPL (2.1, 3) | Weak copyleft | Changes to the library itself must be shared; linking from proprietary code is allowed on conditions | Users must be able to replace or relink the library |
| GPL v2 | Strong copyleft | Distributing a derived work requires source under GPL v2 | Not compatible with Apache 2.0 code |
| GPL v3 | Strong copyleft | As GPL v2, plus a patent licence and installation information for some consumer devices | Compatible with Apache 2.0 in one direction |
| AGPL v3 | Network copyleft | As GPL v3, plus offering source to users who interact with modified code over a network | Applies to SaaS |
The SaaS question and AGPL
GPL obligations are triggered by distribution: shipping software to someone else, such as a mobile app, desktop software, firmware or an on-premise install. If you run GPL code only on your own servers and users reach it through a browser, you are generally not distributing it. This is often called the SaaS loophole.
The Affero GPL (AGPL v3) closes that gap. Section 13 requires that if you modify AGPL software and users interact with it remotely over a network, you must offer them the source code of your modified version. Many companies ban AGPL components in their products, or allow them only after legal review. Be careful also with 'source-available' licences, such as the Server Side Public License or the Business Source License; they restrict commercial or hosted use and are not open source in the usual sense.
Attribution, notices and patents
Even permissive licences have duties. Ship the required copyright notices and licence texts with your product, usually in an 'open source notices' screen or file. For Apache 2.0, include the NOTICE file contents and mark files you have changed. Missing notices are the most common open source defect found in due diligence, and the easiest to fix.
Apache 2.0 and GPL v3 grant users a licence to the contributors' patents that read on the code. Under Apache 2.0, that patent licence ends for anyone who starts patent litigation claiming the work infringes a patent. MIT and BSD say nothing express about patents.
Build an inventory (SBOM)
A software bill of materials lists every third-party component in your product, its version and its licence. Software composition analysis tools can generate one from your repositories and flag licences that conflict with your policy. Keep it current, because dependencies change with every release.
- Write a short open source policy: which licences are allowed, which need review, which are banned.
- Scan every repository, including mobile apps and front-end bundles.
- Record how each component is used: distributed, network-only, or internal tooling.
- Fix missing notices and replace components that conflict with your policy.
- Review the inventory before each funding round or major customer deal.
Contractor code and ownership
Under section 17 of the Copyright Act, the employer owns copyright in work an employee creates in the course of employment, unless they agree otherwise. That rule does not cover freelancers and agencies. Their code belongs to them unless they assign it. Section 19 requires an assignment to be in writing and signed by the assignor. If the assignment does not state its duration, it is treated as five years, and if it does not state its territory, it is treated as limited to India. Contractor agreements should assign all rights worldwide, for the full term of copyright, and require disclosure of any open source the contractor used.
What investors and acquirers ask
- Do you have an SBOM, and when was it last updated?
- Do you use any GPL, LGPL or AGPL code, and how is it used?
- Have you distributed any copyleft code, and complied with source-sharing duties?
- Have you received any licence compliance claims or requests for source code?
- Have all employees and contractors assigned their IP to the company in writing?
- Do you release any of your own code as open source, and under what licence?
How we help
Prodigy Legal writes open source policies, reviews licence scan results, fixes contractor IP gaps and prepares disclosure for investor and acquirer due diligence. The Tech & IP monthly plan covers licensing agreements, IP portfolio management and day-to-day tech and IP questions.
Frequently asked questions
Can I use GPL code in a commercial product?
Yes, but if you distribute the product, the GPL generally requires you to release the source code of the combined work under the GPL. If the GPL code runs only on your servers, the source-sharing duty is generally not triggered, unless the licence is AGPL.
Are open source licences enforceable in India?
Open source licences are licences of copyright, and the Copyright Act, 1957 governs licences of copyright in India. Using code outside the licence terms can be an infringement. Few cases have been decided in India on these licences specifically.
Do I need to show licence notices in a mobile app?
Yes, for most licences. MIT, BSD, Apache 2.0 and the GPL family all require you to pass on copyright and licence notices when you distribute the code. A notices screen in the app settings is the usual approach.
What is an SBOM?
A software bill of materials: a list of the third-party components in your software, with their versions and licences. It helps with licence compliance, security patching and due diligence.
Last reviewed: 2026-11-22. This guide gives general information about Indian law for companies. It is not legal advice, and every matter turns on its own facts.