Software Licensing in Government

Software licensing in government refers to the process by which government departments legally acquire the right to use software, whether through purchasing perpetual licences, subscribing to Software-as-a-Service (SaaS), entering enterprise licence agreements (ELAs), or adopting open-source software. It is a substantial and growing segment of government IT spending, complicated by the software industry's shift away from perpetual licences toward subscription models.

What is Software Licensing in Government?

Government software procurement is governed by GFR 2017, with MeitY's Policy on Adoption of Open Source Software (2014) creating a specific preference for open-source alternatives where they exist. The policy requires government organisations to evaluate open-source alternatives before procuring proprietary software, and to justify proprietary selection if an open-source alternative is available.

The main modes of software licensing in Indian government are as follows. Perpetual licences are a one-time payment for permanent rights to use a specific version of the software, common for traditional desktop applications and older government IT deployments. Annual subscription licences cover SaaS products, Microsoft 365, Adobe Creative Cloud, Salesforce, and similar, where the government pays annually for current-version access. Enterprise Licence Agreements (ELAs) cover an organisation's entire software estate with negotiated flat-rate pricing for unlimited or defined-volume use, preferred by large organisations like NIC, DGS&D (replaced by GeM for rate contracts), and state IT departments. Open-source software is free to use but may have support and customisation costs.

GeM has a dedicated service category for software procurement, including cloud computing services, where government buyers can procure Microsoft, Oracle, SAP, and other enterprise software through GeM's cloud marketplace. NIC's Government of India Technology Empanelment (GITAM) scheme also creates rate contracts for commonly used software, allowing any government organisation to place orders at pre-negotiated rates without floating a separate tender.

The shift to cloud has created new procurement complexity. A cloud service is not owned, it is rented, and the government must manage data sovereignty, access continuity, and exit terms carefully. MeitY's Cloud Policy mandates that all sensitive government data must be stored on cloud infrastructure physically located in India, either on MeghRaj (the government's own cloud operated by NIC) or on empanelled private cloud providers (AWS India, Microsoft Azure India, Google Cloud India).

Why it matters for bidders

Software companies selling to government must understand that they cannot simply offer standard commercial terms. Government software contracts typically require: perpetual licence ownership (or clear exit mechanisms for SaaS), the right to audit actual usage, government-specific data processing agreements, CERT-In compliance for security patches, and no automatic data transfer to servers outside India.

For Microsoft, Oracle, SAP, and other major software vendors, government is one of the largest customer segments. These companies maintain dedicated government business divisions and negotiate ELAs with NIC for central government deployments, creating volume pricing that individual departments then access through Release Orders.

For domestic software companies, government is an accessible market if their product meets the department's functional requirements. The open-source preference policy and Make in India initiatives create advantages for Indian software companies over foreign ones. State government e-governance applications are frequently developed by domestic IT companies under QCBS tenders.

Example

A state's Revenue Department needs to procure an enterprise GIS (Geographic Information System) platform for digitising land records across all districts. The open-source option (QGIS) is evaluated but found to lack the enterprise-grade data management and multi-user editing capability needed. The department justifies procuring a commercial GIS platform. A QCBS tender is floated. Three vendors respond, ESRI India with ArcGIS, a domestic GIS company, and a Microsoft Azure-based GIS solution. ESRI India scores 88/100 on technical evaluation. The final QCBS score (70% technical, 30% financial) results in ESRI India winning despite a higher licence cost, because the technical quality differential outweighs the price difference.

Key rules / thresholds

MeitY's Policy on Adoption of Open Source Software (2014) mandates that government organisations must first consider open-source alternatives. If an open-source product does not meet the requirements, the decision to go proprietary must be documented and approved. All government software must comply with CERT-In guidelines for software security, including patch management, vulnerability management, and security testing requirements. Software contracts for government systems classified as "critical information infrastructure" must additionally comply with the National Critical Information Infrastructure Protection Centre (NCIIPC) guidelines.