Indian government mandates that all systems used by its public sector are deployed on open source software
Eileen Yu / ZDNet :
Context & Ripple Effects
In 2015, India required every system used by its public sector to be deployed on open source software — one of the earliest national-level mandates of its kind. The move set a template others quickly picked up: Bulgaria passed its own law requiring custom government software to be open source within two years, and the US released a draft federal open source policy mandating code be shareable across agencies.
India itself applied the principle again during COVID, when it open sourced the Aarogya Setu contact-tracing app on GitHub. But the arc since then complicates the story: the same government has more recently restricted developer services like Supabase and pushed state apps onto private devices, suggesting openness in Indian tech policy has always been selective rather than absolute.
First-order effects
- Vendors selling software into the Indian public sector lose eligibility unless they deploy on open source, forcing proprietary-stack suppliers to rework their offerings or cede the market.
- Public sector IT buyers gain leverage over licensing costs and lock-in, since deployment on open source makes switching between suppliers materially cheaper.
Second-order effects
- Peer governments treat India's mandate as precedent — Bulgaria legislates it outright and the US drafts cross-agency sharing requirements, turning open source procurement from an outlier position into a competitive norm among states.
- Global enterprise software vendors respond by building open source editions and dual-license models as a standard go-to-market requirement for government business, shifting pricing power away from per-seat licensing.
Third-order effects
- If the pattern holds, governments increasingly use source access as a control point rather than an ideology: India's later blocking of Supabase and its push to preload the Sanchar Saathi app show the state asserting power over what runs domestically, whether by opening code or restricting it.
- Procurement rules become de facto industrial policy — whichever country's public sector mandates open deployment shapes where global vendors invest in compliant engineering, making software sovereignty a structural feature of state IT rather than an exception.
The trend: Government technology policy is converging on 'governed openness' — states mandate open source when it serves control and auditability, while reserving blocking orders and forced deployments for when it does not.