Skip to content

Technology Explained · 6 min read
Open-source software in government, explained plainly

An office buys a records system. Five years later the supplier doubles the yearly fee, or closes, and the office finds that it cannot move its own records anywhere else. Open-source software is one of the ways governments try to avoid that position. It is not free of cost and it is not right for every case, so it helps to know what the term means before a supplier uses it in a proposal.

What open source means

Every program is written as source code, the instructions that people write and a computer follows. With most commercial software the buyer receives only the finished program. The source code stays with the company, and the license, the legal terms of use, says how many people may use the program and for how long.

Open-source software comes with its source code and with a license that lets anyone use, study, change and share it. The Open Source Initiative keeps the definition most of the industry uses. It warns that open source does not just mean access to the source code. The license must also allow free redistribution and modified versions, and must not discriminate against any person, group or field of work.1

Open source describes the license, not the price or the quality. An open-source program may be maintained by a large community or by one person in spare time. The label alone tells an office very little, which is why the questions later in this article matter.

Why governments choose it

The first reason is cost. The United Kingdom's guidance for public bodies lists lower implementation and running costs among the benefits, along with solving common problems using technology that is already available.2

The second reason is control. India's policy on open-source software for government gives two of its objectives as long-term strategic control over e-governance systems and a lower total cost of ownership, meaning what a system costs over its whole life and not only on the day it is bought.3 When an office holds the source code and the right to change it, it can hire a different company to maintain the system. Being unable to leave a supplier without starting again is called lock-in.

The third reason is inspection. Code that can be read can be checked by the office's own staff, by an auditor or by outside experts. The UK guidance notes that publishing code brings suggestions from others on how to improve it and where its security is weak.2 The European Commission's own open-source strategy for 2020 to 2023 makes sharing and reuse a goal and lists "stay in control" among its six principles.4

Policies and examples

India's policy says the government shall try to adopt open-source software in all e-governance systems as the preferred option. Every request for proposals must ask suppliers to consider it and to justify leaving it out. The policy also allows exceptions, including where an office lacks the skills for the technology.3

The Philippines has no national law that gives open source an official preference. A 2023 study prepared for the European Commission found none, although a bill proposing mandatory adoption was filed in the House of Representatives in 2007 and did not pass. The same study records that Republic Act No. 9369 requires the source code of the automated election system to be released to political parties and other stakeholders, and that the Department of Social Welfare and Development has directed its own offices toward open source since 2005.5 The E-Governance Act of 2025, Republic Act No. 12254, does not mention open source. It does make the interoperability of government systems, meaning their ability to work with one another, one of its objectives.6

Open source is also at the center of digital public goods. The Digital Public Goods Alliance describes these as open-source software, open standards, open data, open AI systems and open content collections that respect privacy and applicable laws, do no harm, and help attain the Sustainable Development Goals.7 Its standard has nine indicators, among them open licensing, clear ownership, documentation and a way to extract data.8

One example is close to home. MOSIP, the Modular Open Source Identity Platform, was started in 2018 at the International Institute of Information Technology Bangalore so that countries can build and own their national identity systems. Its website lists the Philippines among the countries using it, and the 2023 study states that the Philippine Identification System is based on it.95

The real costs

No license fee does not mean no cost. The UK guidance says plainly that open source is not completely free, and tells buyers to count the total cost of moving to it, including exit and transition costs.2 In practice an office still pays to install the software, move its records, train staff, host the system and keep it updated.

Support is the largest question. With commercial software, the fee usually buys a helpdesk and regular fixes. With open source, the office must arrange this itself, through its own staff or a contract with a company that knows the software. The UK guidance asks buyers to check how well a project is maintained, whether it receives regular security fixes, and whether its license and warranty suit the organization.2

Skills are the other cost, and India's policy is honest about it by listing lack of expertise as a ground for an exception.3 The UK guidance adds a warning about heavy customization, because a system changed too much becomes hard to update and to keep secure.2 An office with no technical staff and no local support company can end up as dependent on one person as it once was on one supplier.

What an office in the Bangsamoro can ask

We think the label matters less than what the office can do on the day it wants to leave a supplier. We build on open-source foundations ourselves, and we would give the same advice to an office comparing our work with anyone else's. Compare options the way India's policy tells its agencies to, on capability, control, security, lifetime cost and support.3 Then put these questions in writing before signing.

A supplier who answers them clearly, whether the product is open source or not, is giving the office the thing open source was meant to protect, which is the freedom to choose again later.

  • Which parts of the system are open source, and under which licenses?
  • Will the office receive the source code and the documentation for anything built specially for it?
  • Can all our records be exported in a common format at any time, and at what cost?
  • Who provides support and security updates, for how many years, and at what yearly price?
  • Who else maintains this software, and when was it last updated?
  • What training will our staff receive, and could another company take over the system if needed?
  • What will the system cost over five years, including hosting, support, training and the cost of leaving?

Sources

  1. The Open Source Definition. Open Source Initiative, Version 1.9; page last modified 2024-02-16.
  2. Be open and use open source. Government Digital Service and Central Digital and Data Office, United Kingdom, 2017-11-06, updated 2021-03-31.
  3. Policy on Adoption of Open Source Software for Government of India. Department of Electronics and Information Technology, Government of India.
  4. Open source software strategy. European Commission, 2020.
  5. Open Source Software Country Intelligence Report: Philippines. European Commission, Interoperable Europe (research by OpenForum Europe), August 2023.
  6. Republic Act No. 12254, E-Governance Act. The Lawphil Project, Arellano Law Foundation, 2025-09-05.
  7. Digital Public Goods. Digital Public Goods Alliance.
  8. Digital Public Goods Standard. Digital Public Goods Alliance.
  9. MOSIP: Modular Open Source Identity Platform. MOSIP, International Institute of Information Technology Bangalore.
#TechnologyExplained#BARMMTech#MoroTech
Share