Open source requires more than a licence
Open source is receiving a lot of attention. Organisations want greater control over their digital infrastructure and less dependence on a handful of major vendors. But software with freely available source code is not automatically free to maintain or develop. Digital autonomy therefore depends not only on technology, but also on a healthy ecosystem of people and organisations.
Many organisations already use open source, often without explicitly realising it. Linux, PostgreSQL and Kubernetes are examples of technologies that play an important role in modern IT environments. Commercial products often contain open source components too.
The strategic question is not simply whether an organisation uses open source, but whether it knows which components it relies on, how they are maintained and what dependencies they involve. That insight helps organisations assess risks and make informed choices.
Autonomy means having choices
Open source can give organisations more freedom to use and adapt software, or move it to another service provider. This can help reduce vendor dependence. But choosing open source does not automatically make an organisation digitally autonomous. Dependence can also arise from a particular cloud environment, custom extensions or the provider responsible for managing the software.
Autonomy does not mean that you have to build or manage everything yourself. It means understanding where your dependencies lie and having enough options to make changes when needed. Open standards, portable systems and multiple suitable service providers can all help.
Free software does not develop itself
A common misconception is that open source requires no investment. The software may be freely available, but development, security, documentation and maintenance all take time and money. That work is often carried out by developers, companies and communities that contribute to the project.
This also applies to technologies that organisations depend on heavily. The news about the financial pressure on the foundation behind PHP highlights how important it is to ensure the continuity of maintenance and development. Our contribution to the NRC article (Dutch article in Dutch newspaper) emphasises the importance of this funding.
Organisations that see open source only as a way to save on licence fees are missing a crucial part of the picture. They can contribute by providing expertise, time or financial support, or by purchasing solutions from providers that invest in the software and the communities behind it.
Professional support matters
Organisations using open source still need clear agreements on support, responsibilities and continuity. In larger IT environments in particular, it is important to know who to contact when something goes wrong. Collaboration between specialist companies can help: the customer may have a single point of contact and one contract, while several experts work together behind the scenes.
CIOs and IT managers should therefore look beyond the software itself and consider the services around it: who maintains the solution, how are updates handled, and how easily can the organisation switch providers if circumstances change?
A practical agenda for CIOs and IT managers
Start by mapping open source components and critical dependencies. Then assess how actively projects are maintained, what support is available and how easily systems can be transferred. Include the funding and governance of essential projects in your assessment. This helps make open source more than a standalone technical choice: it becomes part of a broader strategy for resilience and digital autonomy.
The key takeaway is that digital autonomy is built together. It requires transparent choices, professional services and investment in the software and communities organisations rely on. Read more in our interview with Business Meets IT (Dutch article in maagazine).
