Request a demo

Join us at Road Expo Scotland 2026 in Glasgow on 24–25 November 2026

Get involved

Developed for the public sector and kept public: explaining open source licensing

This post is part of our Responsible Tech series, in which we explore open source technology and data privacy, security, and sovereignty. In this update, Chloe Carrington Dunn explains what open source licensing is, how to spot it and what public sector decision-makers need to know about it.

— 

The first post in this series explored the benefits of open and reusable source code. Angela Dixon, our Managing Director, made the case that “if it is the product of public spend, then it should be built to be reused and shared” and busted some of the myths around open source being more vulnerable to maleficent actors or less secure. 

If you didn’t read that first post, the tl;dr was this: publishing open source code can reduce risk, prevent vendor lock-in, and means the benefits of the code can be shared among other public sector entities. 

But not everyone understands what open source means and how to recognise when something is open source. In this blog post, I’ll clear up when open source code is used, what it means to be open, and what this means for the public sector.

Open Source for Closed Software

Open and closed source software are often spoken about as distinct and opposing forces, but this isn’t quite true. 

Not everything large companies use is proprietary. Most use open source software as foundational infrastructure, integrating it deeply into their own tech stacks. Open source is present in over 95% of proprietary software systems, making up around 70% of their codebase on average. 

Think of open source as a great way of solving problems – creators and users benefit from crowd-sourcing solutions. Companies can consider different solutions created by open source projects, identify which one does what they need the best, and adapt them to their own use case. 

Without open source software, everything would have to be built completely from scratch every time. Tech companies can save significant costs by using open source code. In fact, it is estimated that without open source, firms would be spending 3.5 times more on software.

But companies don’t just benefit from open source; sometimes they contribute to it. Tech firms can get the kudos from the developer community. They can also outsource some R&D for free, as they are able to benefit from the hive mind of the OS community. 

Another benefit is that, when hiring, tech firms using open source software can find staff who already know the systems well, reducing training costs. They can also use it to sway market forces, for example releasing open source software that competes with a rival’s.

How to recognise when something is truly open source

Just because something is based on open source software, does not mean that it is truly open, or that you can avoid vendor lock-in.

As noted above, a tech provider may use open source code, add their secret special bits, and sell it as closed and proprietary software. Providers may market the software as open source, but the code may only be source-available (i.e. the source code is publicly available) and the software is not truly open source. 

But these changes are not always permitted by open source creators. Open source licenses are sometimes categorised as “permissive”—allowing users to do whatever they like with the code, including adding closed code on top—or “protective” (AKA copyleft),  requiring that any modified or derivative versions of the software must also be released under the same open-source license. 

At SocietyWorks, our software is the latter: we require any modified versions or changes to also be released under the same open-source terms. 

For public authorities, it is worth considering that protective (copyleft) licenses prevent public code from being taken and tied up again. […] Something paid for by the taxpayer can remain a public good.

What does this mean for the public sector?

There is no right answer when it comes to which type of open source license is better. These arguments have raged for years, and it is not for us to decide which is the best kind of open source. 

A general guide is that permissive open source licences are more pro-business (for better or worse). Protective open source licences can help to prevent proprietarisation. 

For public authorities, it is worth considering that protective (copyleft) licenses prevent public code from being taken and tied up again – “If it is the product of public spend, then it should be built to be reused and shared”. 

This means that once one local authority has procured a service, the code remains permanently open and communal for others to benefit from. Something paid for by the taxpayer can remain a public good.

By basing the open source code on a copyleft license, the local authority avoids becoming dependent on a single software vendor or proprietary ecosystem. Any vendor can compete to maintain or deploy the open infrastructure.  Any changes or improvements made to the open source code – whether by the local authority, a private vendor, or anyone else – cannot be locked behind a proprietary paywall.

It also allows the public sector to foster collaboration. Protective or copyleft licences for open source code encourage local authorities and civic tech communities to pool resources, share bug fixes, and collaboratively improve public-sector tools. This collaboration ensures the services can always be improved on, and saves the taxpayer money.

—

Image: Erik Mclean via Pexels


Schedule your one-to-one demo

Request a demo