Civic Innovation

State and Local Government Open Source Software Adoption Barriers

Institutional habits, not weaker software, keep governments paying for licenses.

Cover illustration for “State and Local Government Open Source Software Adoption Barriers”
Cover illustration for “State and Local Government Open Source Software Adoption Barriers”

State, local, and education (SLED) governments budgeted $138.9 billion for IT in 2024, of which IT services made up $59 billion and software products $13 billion. Total state and local government IT spending is expected to exceed $153.6 billion in 2025, a 6.4% increase over 2024. Software products alone are expected to reach $14 billion, a market large enough that even modest open source software (OSS) substitution would represent hundreds of millions of dollars in savings.

Against that backdrop, OSS remains structurally underutilized. The reason is not a lack of proven alternatives, but institutional forces that keep proprietary software entrenched. The cost evidence shows that OSS is not merely hypothetically cheaper. LocalGov Drupal produces cost reductions of 30-50% on website rebuilds, with councils typically saving £30,000-£90,000 on developer costs (per Open Digital Cooperative figures compiled in a UK Gov technology blog, May 2026). The French city of Toulouse saved roughly €1 million over three years by switching to LibreOffice, and the Italian Ministry of Defense deployed LibreOffice on 150,000 computers, targeting savings of €26-29 million. The gap between what OSS demonstrably saves and what governments actually spend on proprietary licenses is what the rest of this piece examines.

The Custom Development Misclassification

Many government agencies treat open source software as risky custom development rather than as commercial off-the-shelf (COTS) software, a category it legally and functionally qualifies for (per GovLoop). This misclassification matters because COTS procurement pathways are faster, seen as lower-risk, and supported by existing contracting frameworks. OSS routed through custom-development processes faces longer timelines, more scrutiny, and higher internal resistance.

Recent policy touches on this issue. The April 2025 Executive Order "Ensuring Commercial, Cost-Effective Solutions in Federal Contracts" prioritizes COTS. OSS advocates argue this should accelerate OSS adoption because free and open source software (FOSS), or software whose source code is publicly available and may be freely used, modified, and redistributed under its license, legally qualifies as COTS, but only if agencies recognize the classification. The SHARE IT Act, enacted December 23, 2024, requires agencies to share custom-developed source code across government and publish lists of it publicly. That is a step toward reuse, but it does not resolve the upstream classification problem.

The Department of Defense's "Adopt, Buy, Create" policy, which prefers existing government or OSS solutions before buying proprietary ones, is frequently cited as a template SLED agencies could replicate, but few have. Without correcting this foundational misclassification, procurement reform efforts address symptoms rather than the root cause.

Procurement Built for Incumbents

Vendor concentration is well documented. A January 2024 analysis of 24 federal agencies found that 10 vendors accounted for the majority of the most widely used licenses, and 2021 GAO data shows the top three software providers are Microsoft (30%), Adobe (10%), and Salesforce (9%). Government procurement processes are notoriously complex and bureaucratic, and streamlining them to enable open competition without sacrificing efficiency is a significant undertaking (per the Open Contracting Partnership / ODI / AWS 2024 report).

Without targeted guidance, agencies revert to established vendors. This is not because OSS is inferior, but because the procurement system has no built-in mechanism to surface or evaluate it. Even when agencies do adopt OSS, it may contain layers of proprietary technology underneath, a persistent issue noted by Jan Ainali, codebase steward at the Foundation for Public Code (per Computer Weekly).

Multi-year contracts add political and technical lock-in. Proprietary incumbents entrench themselves through long contracts, which makes OSS migration costly in both operational and political terms, so the switching cost is real even when the software cost argument is clear. Genuine procurement reform would replace proprietary favoritism with policies that explicitly welcome OSS competition, including from startups and small businesses (per Tech Policy Press).

Licensing & IP Fog

Licensing and intellectual property (IP) concerns are the most commonly cited barrier to OSS adoption across enterprise organizations in 2025. According to the Linux Foundation's State of Global Open Source 2025 (851 qualified global respondents), 37% of respondents name them as top barriers. Among organizations that want to contribute back to OSS projects, 33% cite fear of leaking IP and 33% cite legal or licensing concerns as blockers, so the same anxieties that limit adoption also limit participation.

In government, the problem is sharper. Federal procurement regulations and OSS licenses can conflict in ways that require specialized IP counsel, which most SLED agencies do not have in-house (per Martensen IP). Even agencies that want to use OSS may find the license landscape, including GPL, AGPL, Apache, MIT, and dozens of others with different obligations, too complex to navigate without dedicated legal resources.

This caution is not irrational. The obligations attached to some copyleft licenses are genuinely non-trivial for agencies that may need to modify and redistribute code. In practice, licensing uncertainty can block adoption even when the technical and cost arguments for OSS are strong, and legal sign-off becomes a bottleneck.

Security: Real Risk or Overstated Fear?

Security concerns rank alongside licensing as a top barrier, with 36% of enterprise organizations citing them as limiting OSS adoption (Linux Foundation 2025). The supply chain risk is real and large. Sonatype discovered 512,847 malicious packages in main open source ecosystems in 2024, a 156% annual increase. Some 96% of all codebases contain open source components, three-quarters contain high-risk open source vulnerabilities, and approaching 7 trillion components were downloaded in 2024.

The XZ Utils backdoor, discovered March 29, 2024 by a Microsoft software developer, became a widely cited example. It was a backdoor hidden in software that is widely bundled with Linux distributions and largely maintained by volunteers (per OpenSSF). The public sector is already a high-value target: in Q4 2024 it ranked among the top three most targeted industries for ransomware attacks.

The comparison with proprietary software is asymmetric, however. Proprietary software carries its own undisclosed vulnerabilities, while OSS at least allows code inspection. The security argument against OSS is strongest when agencies lack the internal capacity to perform that inspection, which is a workforce problem as much as a software problem.

The Biden White House OS3I End of Year Report (January 2024) identified structural OSS security challenges: companies reserving security features for commercial products built on OSS, inconsistent corporate contributions to sustaining OSS projects, and decentralized ownership with varied development processes. CISA's March 2024 finalization of the secure software development self-attestation form, required for developers of software used by the federal government, is one policy attempt to establish a baseline, but it does not resolve the gap for SLED.

This misclassification matters because COTS procurement pathways are faster, seen as lower-risk, and supported by existing contracting frameworks.

The FedRAMP Bottleneck

FedRAMP provides a standardized approach to security assessment, authorization, and continuous monitoring of cloud services, and it is mandatory for federal agency cloud deployments at low, moderate, and high-risk impact levels. The Office of Management and Budget requires all executive federal agencies to use it. State and local governments increasingly look to FedRAMP as a de facto standard even though it is not formally required of them. As a result, SLED agencies frequently apply a framework designed for federal use to procurement decisions where it has no formal mandate, which creates a bottleneck for OSS tools that have not been formally authorized.

The Department of Homeland Security (DHS) categorizes certification and accreditation (C&A) issues as a distinct cluster of government OSS challenges, alongside inertia, quality fears, support concerns, and procurement issues. This confirms it is a recognized problem rather than a peripheral one.

For community-maintained OSS tools that lack a vendor with the resources to pursue FedRAMP authorization, the requirement is effectively exclusionary regardless of the software's actual security quality. The compliance burden falls asymmetrically: large proprietary vendors can absorb authorization costs, while small OSS projects and the agencies that want to adopt them generally cannot.

The Workforce Gap

According to Association for Talent Development research, 76% of talent development professionals believe there is a significant skills gap in the government workforce. Pay makes the problem structurally difficult: federal employees earned 24.72% less than workers in similar private sector jobs in 2024, which hampers recruiting and retaining technical talent. A January 2025 GAO report found that while agencies recognize recruiting and retaining cyber talent as critical, many have implemented fewer than half of the key workforce planning practices needed to address shortages, and GAO recommended 23 improvements (per Federal News Network).

Generational attrition compounds this. "Peak Boomers" occupy roughly 10% of U.S. jobs, and their retirement between 2024 and 2030 is projected to create between 10.8 million and 14.8 million job vacancies across sectors. Government IT stands to lose institutional OSS knowledge precisely when adoption pressure is rising.

Research on OSS adoption points to the same issues. Challenges include cultural resistance, lack of leadership support, competence gaps, and ensuring sustainable maintenance (per an arxiv paper on OSS adoption barriers). A Springer ICSCCW 2024 conference paper on public sector OSS adoption, a case study of Azerbaijan's ASAN service centers, found that attitude toward change is probably the most crucial factor at the initiation stage, and that top management sponsorship is the main facilitator at the implementation stage. Both require capable, informed leadership that the skills gap makes harder to sustain.

The result is a cycle that reinforces itself. Agencies without technical staff cannot evaluate or maintain OSS, so they default to proprietary vendors that bundle support, and they never build the internal capacity to change the pattern.

No Playbook for Vetting OSS

There is currently no formal or standardized process across government for evaluating, recommending, or providing confidence in open source products or components for use in the public sector (per a UK Government technology blog, May 2026). The governance gap is broader than government. The Linux Foundation's 2025 World of Open Source Survey (851 respondents) finds that while OSS has achieved mission-critical status, organizational maturity significantly lags adoption: only 34% of organizations have defined a clear open source strategy, and only 26% have implemented an Open Source Program Office (OSPO).

Large enterprises with 10,000 or more employees are 2.4 times more likely to have an OSPO than small companies (39% vs. 16%). Government agencies, which rarely have the dedicated teams of large enterprises, fall into the less-mature end of this distribution.

Without evaluation frameworks, agencies face decision paralysis. The software may be technically sound, but no institutional process produces a defensible "yes," and in government an indefensible decision is a career risk. The Linux Foundation's 2025 report characterizes this as a paradox: organizations depend on OSS as backbone infrastructure while lacking the governance to manage that dependency safely, creating "significant business risks as organizations depend on foundational technologies they cannot adequately assess." Even OSS that is 55% adopted in operating systems and 49% in cloud and container technologies globally (Linux Foundation 2025) still lacks the institutional processes that would make adoption defensible to a government auditor.

Legacy Lock-In

The UK National Audit Office warned in 2025 that many government systems remain "high risk" due to age, unsupported software, and outdated architecture, a finding with clear parallels in U.S. SLED environments. Replacing these systems is difficult: large public sector upgrades are expensive, operationally risky, and slowed by procurement complexity, and vulnerable systems frequently remain active long after safer alternatives exist (per a Meterian blog analysis, May 2026).

Vendor lock-in is a named risk. Proprietary incumbents entrench through multi-year contracts, and OSS migration is politically costly even when the technical and financial case is clear, since no elected official wants to sponsor a failed migration. DHS has also listed inertia as a distinct government OSS challenge category. It reflects the accumulated weight of sunk costs, cleared approvals, trained staff, and political risk aversion.

Legacy lock-in interacts with every prior barrier. The compliance framework is built around existing systems, the workforce knows the incumbent tools, procurement is set up to renew existing contracts, and legal teams have cleared the existing vendor's licenses. This also connects back to the procurement misclassification problem: if OSS were treated as COTS from the start, migration would be evaluated as a software switch rather than a custom development project, but reclassifying it mid-legacy-cycle is harder than getting it right at the outset.

What Early Adopters Fixed First

Schleswig-Holstein, Germany announced in 2024 that it would switch to OSS office suites, operating systems, cloud, telephony, and additional software categories across its state administration. It cited high costs, digital sovereignty, control over data, and investment in the local economy as motivations (per an arxiv paper on European digital sovereignty, 2026). Denmark's Ministry of Digital Affairs announced in 2025 that it would switch

Sources

  1. Open-Source Software Adoption in Public Sector | Springer Nature Link

    Provided the Azerbaijan ASAN case study on attitude toward change and top management sponsorship.

  2. Adopting open-source in local government – Technology in government

    Provided LocalGov Drupal cost savings and the point that no standard process exists for vetting OSS.

  3. https://digital.gov/resources/requirements-for-achieving-efficiency-transparency-and-innovation-through-reusable-and-open-source-software

    Covers the SHARE IT Act's requirements for sharing custom-developed code across government.

  4. The State of Open Source Software in 2025

    Supplied the survey figures on licensing and security barriers, OSPO and strategy maturity, and global adoption rates.

  5. Searching for European Alternatives: Digital Sovereignty, Digital Patriotism, and the Emerging Geopolitics of Software Adoption

    Source for the Schleswig-Holstein migration and its motivations around digital sovereignty.

  6. In 2024, SLED IT Spending Takes a Whole-of-State Focus

    Contributed the SLED IT spending figures for 2024 and the breakdown of services and software.

  7. https://www.govloop.com/community/blog/free-and-open-source-software-is-cots-affordable-efficient-and-proven/

    Supported the argument that OSS qualifies as commercial off-the-shelf software but is often treated as custom development.

  8. https://waldo.jaquith.org/blog/2025/06/custom-vs-cots/

    Informed the discussion of custom development versus COTS classification and its procurement consequences.

Elodie Reinholt

More in Civic Innovation

← Front page