A first guide to the code beneath the floorboards, and why open technology belongs to everyone.
When most people hear the words open source, they imagine someone in a dark room, typing very fast, surrounded by cables, coffee, and very strong opinions about Linux.
They imagine code scrolling across a black screen. They imagine a world of developers speaking a language that seems designed less to communicate and more to quietly escort everyone else out of the room.
And honestly, fair enough.
The open-source world has not always been good at explaining itself to people outside the technical community. It has built some of the most important infrastructure of the digital age, but it has often described that infrastructure in the language of the workshop, not the language of the street, the classroom, the town hall, the small business, the NGO office, or the public library.
So let us begin again.
Open source is not just about software. It is about a simple and surprisingly powerful question:
Who gets to understand, repair, adapt, improve, and share the tools we all depend on?
That question no longer belongs only to developers. It belongs to the teacher trying to adapt digital learning materials to her students, and to the small firm paying for six subscriptions that do not speak to each other. It belongs to the municipality trapped in a vendor contract it cannot easily leave, and to the parent wondering where their child’s school data is stored.
The truth is simple: we already live inside software.
Software is no longer just something we install on a computer. It has become the architecture beneath our schools, hospitals, workplaces, public services, transport systems, climate tools, democratic spaces, and daily routines. We move through it the way we move through corridors, forms, roads, classrooms, waiting rooms, and public squares. We often notice it only when it breaks.
The password fails. The school platform freezes. The municipal portal refuses the document. The health app speaks in bureaucratic riddles. The online form crashes at the final step. The workplace tool updates overnight and somehow everyone becomes less productive than before. The device cannot be repaired. The data cannot be exported. The system says no, but nobody can explain why.
We call these moments glitches.
But sometimes they are not just glitches. They are tiny cracks in the floorboards: brief moments when the hidden architecture of our digital lives becomes visible.
And beneath those floorboards, there is code.
1. The first myth: “This is not for me”
The first barrier to open source is not technical. It is emotional.
Many people hear the phrase and immediately decide they are not the intended audience. They assume open source belongs to people who write code, run servers, build apps, or enjoy installing operating systems on old laptops. They think: this is useful, maybe, but for someone else.
That self-exclusion is one of the reasons this series exists.
Open source has been treated as a specialist topic for too long. But the systems built with software are not specialist systems anymore. They are ordinary systems. They shape how we learn, how we work, how we communicate, how we access services, how we store memory, how we organize communities, how governments deliver rights, and how institutions make decisions.
The Open Source Initiative, one of the main global bodies defining the term, explains that open source does not merely mean “access to the source code.” A proper open-source license must allow redistribution, provide access to source code, permit modifications and derived works, and avoid discrimination against people, groups, or fields of use. In other words, open source is not just about seeing the recipe. It is about being allowed to use, adapt, share, and build from it under rules that protect those freedoms. It means that technology can behave less like a sealed product and more like shared infrastructure.
And shared infrastructure is never just for specialists.
A bridge is not only for engineers. A school is not only for architects. A public library is not only for librarians. A digital system that mediates rights, education, services, health, work, and participation is not only for programmers.
We do not all need to become developers. But we do need to become more literate about the systems we live inside.
2. We already live inside software
For years, we were taught to think of software as a tool. A thing we used for a task. Word processing. Email. Accounting. Design. Entertainment. A program was something installed on a machine, opened when needed, and closed when finished.
That world is gone.
Today, software is not merely a tool we use. It is the environment through which many parts of life are administered. It decides how easily a citizen can request a service, how a student submits work, how a local authority stores records, how a business tracks customers, how a hospital exchanges information, how a city manages transport data, and how a community organizes itself.
This is why the conversation has changed. When software was just a tool, it made sense to ask whether it was convenient. When software becomes infrastructure, we have to ask whether it is accountable, secure, adaptable, repairable, interoperable, affordable, and governed in the public interest.
There is a reason the European Commission’s 2021 study on open-source software and hardware described open-source software as “mainstream” across the software industry and identified open source as a public good. The same study examined open source in relation to technological independence, competitiveness, innovation, cybersecurity, artificial intelligence, connected cars, high-performance computing, big data, and digital transformation.
That is not the footprint of a hobby.
A Harvard Business School working paper makes the economic scale even clearer. Researchers estimated the supply-side value of widely used open-source software at $4.15 billion, but the demand-side value — what firms would need to spend if they had to recreate or replace the open-source software they rely on — at $8.8 trillion. The same paper found that firms would need to spend 3.5 times more on software than they currently do if open-source software did not exist.
This is the strange invisibility of open source. It is everywhere, but often unnamed. It is essential, but often underfunded. It powers the digital economy, but many people still imagine it as a niche culture of volunteers arguing online.
The floorboards are carrying the house. We just rarely look down.
3. Open source is already inside the walls
To understand how ordinary open source already is, look at the web.
WordPress, one of the most widely used content management systems in the world, is itself an open-source publishing and content management system, and W3Techs lists major public-facing sites using WordPress, including subdomains or pages associated with Microsoft, Archive.org, MIT, Mozilla, and Walmart. This does not mean every site is fully open in every layer, of course. But it shows how open-source foundations can sit quietly beneath familiar digital surfaces.
Education tells an even clearer story. Moodle, the open-source learning management system used by schools, universities, training providers, companies, and public institutions, reports more than 147,000 registered sites, more than 55 million courses, more than 508 million users, and use across 232 countries.
The corporate software world is also deeply dependent on open-source components. Synopsys’ 2024 Open Source Security and Risk Analysis report examined more than 1,000 commercial codebase audits across 17 industries and found that 74% of audited commercial codebases contained high-risk open-source vulnerabilities. That finding is important for two reasons. First, it shows how deeply open-source components are embedded in commercial software. Second, it reminds us that open source is not automatically safe simply because it is open. Governance, updates, maintenance, security review, and responsible stewardship matter.
This is the grown-up version of the open-source conversation.
Open source is not marginal. It is not automatically innocent. It is not magically secure. It is not a charity box from which the world can endlessly take without care. It is infrastructure, and infrastructure requires stewardship.
The lesson is clear: open source is not outside the serious world. It is already inside the serious world. The question is whether we manage it like infrastructure or continue pretending it is someone else’s hobby.
4. The “nerd” stereotype protects the status quo
The idea that open source is “for nerds” may sound affectionate, but it does real damage.
If open source is framed as something only technical people understand, then everyone else stays outside the conversation. Teachers do not ask whether their digital classroom tools could be more adaptable. NGOs do not ask whether their collaboration platforms protect sensitive data. Municipalities do not ask whether public money could fund reusable public code. Funders do not ask whether a digital project will leave behind shared infrastructure or just another subscription. Boards do not ask whether vendor dependency has become a strategic risk. Citizens do not ask whether the systems governing access to services can be inspected, challenged, or improved.
The stereotype keeps the conversation small. And when the conversation stays small, closed systems remain the default.
This does not happen because every closed system is bad or every proprietary vendor is malicious. That would be too simple. Many proprietary systems are useful, polished, secure, and professionally supported. Many open-source systems are difficult, under-designed, or poorly maintained. The world is not a fairy tale of good open tools and evil closed tools.
The real problem is default thinking.
Organisations often choose digital systems because they are familiar, aggressively marketed, already embedded in procurement habits, or recommended by consultants who know the same ecosystem. Public bodies may buy systems because the procurement process rewards low-risk familiarity over long-term autonomy. Schools may use platforms because everyone else does. NGOs may sign up for tools because they need something that works by Monday. Small companies may keep adding subscriptions because each one solves one problem, until the organisation wakes up inside a maze of recurring payments and disconnected data.
Open source asks us to pause and ask different questions.
Who controls the tool? Where does the data live? Can we leave? Can we adapt it? Can we audit it? Can another provider support it? Can public investment be reused? Can local people learn from it? Can the system grow with us, or does it slowly turn our own organisation into a tenant?
These are not questions only a developer can ask. They are questions for managers, educators, funders, municipal leaders, civil servants, boards, parents, citizens, and communities.
The technical details matter. But the democratic imagination has to enter the room first.
5. Case study: when schools build capacity instead of dependency
Education is one of the clearest places to understand open source, because schools reveal the stakes so plainly.
A school is not just choosing software. It is choosing a learning environment. It is choosing what students understand technology to be. Is technology a sealed system that children click through? Or is it something they can explore, question, repair, and shape?
In Valencia, Spain, the regional government developed LliureX, an open-source education software project for schools. The European Commission’s Open Source Observatory describes LliureX as open-source education software developed by the Valencia regional government since 2005, and notes that its LliureX23 version offers an accessible operating system and applications covering most educational needs.
The deeper lesson is not simply “schools can save money.” Cost matters, but it is not the whole story. The more interesting point is that an education system can build a digital environment around public needs: language, curriculum, teacher practice, student learning, local support, and technological independence. Students do not only learn how to click through a finished product. They encounter technology as something made, maintained, translated, and adapted by people.
Kerala, India offers another real example. Kerala Infrastructure and Technology for Education, known as KITE, introduced KITE GNU/Linux 22.04, a free operating system designed specifically for public schools in Kerala and intended to support digital education across about 300,000 school computers.
Again, the point is not that every school everywhere should copy Kerala or Valencia exactly. Context matters. Capacity matters. Support matters. Training matters. But these examples show that open source can move beyond the image of the lone developer. It can become public education infrastructure.
That is a very different story from “free software for nerds.” It is a story about what children learn when the systems around them are more open, more localizable, and more connected to public purpose.
6. Open source is not “free stuff”
One of the most damaging simplifications is that open source means “free software.”
Sometimes it does mean software that is free to download. But if that is where our understanding stops, we will make bad decisions.
Open source is not free like a forgotten chair on the sidewalk. It is free like a public library: open to many, deeply valuable, and still dependent on care, funding, maintenance, rules, people, and love.
A serious open-source system still needs hosting, updates, cybersecurity, accessibility work, user support, migration planning, staff training, documentation, backups, governance, and long-term stewardship. If an organisation adopts an open-source tool without budgeting for those things, it is not practicing digital autonomy. It is practicing wishful thinking.
The financial logic is different from the proprietary model. In many closed systems, money flows into licenses, subscriptions, upgrades, vendor contracts, and the ongoing right to keep accessing a tool. In open systems, money can shift toward capacity: local expertise, configuration, training, maintenance, security, adaptation, integration, documentation, and support.
The question is not simply, “Can we get software without paying?” The better question is, “Would we rather rent access forever, or invest in capacity we can keep?”
This is especially important for NGOs, schools, municipalities, and public bodies. A small NGO may not have the staff to self-host everything, and that is fine. A municipality may need professional vendors, and that is also fine. Open source does not mean rejecting professional services. It means the service is built around tools that are inspectable, portable, reusable, and not entirely controlled by one provider.
A healthy open-source ecosystem includes companies, consultants, developers, public institutions, universities, foundations, and communities. People can and should be paid for support, maintenance, design, integration, training, security, and governance. The difference is that the value does not have to be locked inside a private box. Improvements can circulate. Knowledge can accumulate. Public investment can leave behind public capacity.
This is the adult version of open source. Not “everything is free,” but “the value we create can be shared, inspected, adapted, and sustained.”
7. Case study: when openness creates public value
Open source belongs to a larger family of open technologies and open practices: open standards, open data, open hardware, open educational resources, and civic tech. They are not identical, but they share a common logic. They make systems more reusable, inspectable, adaptable, and participatory.
A useful example is Transport for London’s open data programme. TfL made transport data available to developers, and a Deloitte report noted that more than 600 apps were powered by TfL data and used by 42% of Londoners. The report was commissioned to understand the economic and social value of that open-data approach, including benefits for customers, road users, businesses, and TfL itself.
This is not open-source software in the narrowest sense. But it is part of the same public-interest architecture. A public body releases useful data in a reusable way. Developers build services. Citizens get better information. Businesses create value. The transport network benefits from innovation it did not have to build alone.
That is what openness can do when it is treated as infrastructure.
Barcelona offers another example through Decidim, the free and open-source platform for participatory democracy. As of June 2023, the best-known deployment, decidim.barcelona, had more than 120,000 registered participants, 126 participatory processes, 4,492 public meetings, 31,261 proposals, and 258,866 support votes. More than 14,000 proposals had already become public policies grouped into projects whose implementation could be monitored.
This is where open technology becomes especially powerful for democracy. Decidim is not merely a platform. It is a statement about how public digital infrastructure can be built. The tool itself can be studied, reused, adapted, and improved by other administrations and communities. The democratic process does not disappear into a proprietary black box. It becomes more visible as a shared civic system.
The European Union’s Interoperable Europe Act moves in a similar direction at the policy level. The Act creates a cooperation framework for public administrations, includes mandatory interoperability assessments, establishes an Interoperable Europe Portal as a one-stop shop for shared and reusable solutions, and supports regulatory sandboxes and GovTech cooperation so administrations can test, learn, and scale solutions for reuse.
That may sound bureaucratic, but underneath the language is a simple idea: public digital systems should not be isolated islands. They should be able to connect, travel, and be reused.
8. Why this matters for individuals
For individuals, open source matters because it changes the relationship between people and technology.
Most of us have been trained to experience digital life as consumers. We click “accept.” We update. We subscribe. We forget passwords. We store files somewhere in the cloud. We buy a device and discover, a few years later, that the battery cannot be replaced, the software is no longer supported, or the repair costs almost as much as a new product. We use platforms because everyone else uses them. We hand over data because the system gives us no practical alternative. We learn to treat technology as weather: inconvenient sometimes, powerful often, but ultimately beyond our control.
Open source interrupts that feeling of helplessness.
It does not mean every person must become a programmer. It means ordinary people can begin asking better questions about the systems around them. Can this tool be inspected? Can I leave it without losing my data? Can someone other than the original company repair or support it? Can the system be translated, adapted, or improved for a local need? Is there a community around it? Is it maintained? Does it respect privacy? Does it explain what it does? Does it treat me as a user, a customer, a citizen, or simply as a source of data?
These questions matter because digital dependency often enters our lives quietly. It arrives as convenience. A free account. A school platform. A work tool. A messaging app. A smart device. A subscription. A default setting. None of these things feels political on its own. But together, they shape how much control we have over our communication, memory, privacy, learning, creativity, and participation.
One of the clearest examples is OpenStreetMap. Most of us use digital maps without thinking about the enormous infrastructure behind them. But OpenStreetMap shows another possibility: a map built and maintained by a global community of contributors. Live OSMstats regularly shows mapping activity happening across dozens of countries within the previous hour, a small window into a much larger global commons of geographic knowledge.
A map is never neutral. What appears on it can affect who is visible, who receives services, who can navigate safely, and who is left as a blank space.
During disasters and humanitarian crises, open mapping becomes even more than a convenience. The Humanitarian OpenStreetMap Team reported that, in its 2023–2024 impact year, 685,000 volunteer mappers helped map areas home to 915.8 million at-risk people, trained 9,792 people across sectors, and saw 111,500 data downloads from the Humanitarian Data Exchange.
For an individual volunteer, adding roads, buildings, clinics, water points, or settlements to a shared map may feel like a small act. But in the right context, that small act becomes part of a rescue system, a planning system, a visibility system. It says: this place exists, these people exist, and responders should not have to navigate by guesswork.
Another example is learning. A young person using open educational tools encounters technology differently. Instead of learning only to click through a finished product, they can begin to understand that digital systems are made by people, shaped by choices, and open to improvement. This is one of the quiet civic benefits of open source: it teaches that technology is not magic. It has structure. It has politics. It has values. And because it is made, it can be remade.
Open source can also matter in the most practical sense. It can keep older devices useful for longer, support repair cultures, reduce unnecessary waste, and give people alternatives when commercial software becomes too expensive or too restrictive. A person who installs an open operating system on an old laptop is not only saving money. They are extending the life of a device. A community that uses open hardware sensors to monitor air quality is not only collecting data. It is learning to see its environment with tools it can understand and adapt. A family that chooses privacy-respecting tools is not withdrawing from society. It is making a choice about dignity.
Of course, individuals should not be romanticized as if everyone has equal time, skill, confidence, or resources to manage technology. That is precisely why good open tools, documentation, communities, public institutions, and professional support matter. Open source should not become another burden placed on individuals already overwhelmed by digital life. Its promise is not that everyone must do everything alone. Its promise is that people should not be permanently locked out of understanding the systems that shape them.
This is why open source belongs in civic literacy.
Just as we teach people the basics of media literacy, financial literacy, health literacy, and democratic participation, we need a basic literacy about digital infrastructure. Not because everyone must master the machinery, but because everyone deserves to know when they are being locked in, tracked, limited, excluded, or made dependent.
You do not need to read code to care about open source. You only need to care about whether the tools around you can be trusted, questioned, repaired, and improved.
9. Why this matters for companies, professionals, NGOs, and public organisations
For organisations, open source is not a lifestyle preference. It is a strategic question.
A company, NGO, school, municipality, university, foundation, or public agency does not experience software as an abstract technical object. It experiences software as a budget line, a workflow, a risk, a dependency, a staff training issue, a procurement decision, a data governance question, a cybersecurity responsibility, and sometimes a strategic vulnerability.
Every organisation now has a digital nervous system. It may include email, file storage, project management, accounting, customer relations, learning platforms, websites, databases, analytics tools, meeting platforms, human resources systems, internal documentation, cybersecurity software, and public-facing services. Some of these systems are visible. Others are so embedded in daily work that nobody thinks about them until they fail, become too expensive, change their terms, lose data, stop integrating, or quietly trap the organisation inside a vendor’s ecosystem.
This is why open source should be introduced to organisations not as a moral slogan, but as a management discipline.
The economic evidence is already strong. The European Commission’s open-source impact study estimated that companies in the EU invested around €1 billion in open-source software in 2018, generating between €65 billion and €95 billion in positive economic impact for the European economy. It also projected that a 10% increase in open-source software contributions could generate an additional 0.4% to 0.6% GDP annually and more than 600 additional ICT start-ups in the EU.
Those figures matter because they move open source out of the charity box. Open source is not merely something generous developers give away. It is a productive layer of the modern economy. It reduces duplication, accelerates innovation, allows companies to build on shared foundations, and creates service markets around implementation, hosting, security, integration, support, training, and maintenance.
The business world already knows this, even when it does not always say it out loud. Red Hat is one of the clearest examples. IBM acquired Red Hat in 2019 for approximately $34 billion, explicitly positioning the acquisition around open hybrid cloud and enterprise open-source technologies. IBM’s announcement described Red Hat as a leading provider of enterprise open-source software solutions and linked the acquisition to customer freedom, choice, flexibility, and hybrid multicloud infrastructure.
Red Hat did not become valuable because it “sold free software.” It became valuable because it built trust, support, certification, integration, enterprise reliability, and a business model around open-source systems that organisations needed to run serious infrastructure.
GitLab offers another useful example. GitLab describes itself as an intelligent orchestration platform for DevSecOps, and its investor materials state that more than 50 million registered users and 50% of the Fortune 100 use GitLab to ship software more securely and efficiently. Whether one likes every aspect of the open-core model or not, the lesson is important: open-source-aligned business models can scale, employ people, serve large organisations, and sit at the centre of modern software delivery.
For small companies, this should be freeing. Open source does not mean “there is no business model.” It means the business model often moves away from selling permission and toward selling value: support, trust, reliability, deployment, design, hosting, training, integration, compliance, customization, and long-term partnership. A small company can use open-source foundations to build faster. A consultancy can offer implementation expertise. A local service provider can help schools, NGOs, or municipalities deploy tools in their own language and context. A hardware lab can build repairable devices. A training company can teach open digital skills. The opportunity is not only to consume open source, but to participate in an ecosystem around it.
For NGOs, the organisational stakes are different but just as serious. Civil society organisations often handle sensitive information: beneficiary data, volunteer records, donor lists, advocacy networks, internal strategy, research materials, vulnerable community contacts, and sometimes politically sensitive communications. If these tools are chosen only because they are familiar or free at the point of use, the organisation may unintentionally expose itself to privacy risks, data lock-in, or loss of autonomy. Open-source alternatives do not automatically solve these problems, but they allow a more deliberate conversation: where should our data live, who can access it, who maintains the system, can we migrate later, and are we building capacity or just renting convenience?
For public organisations, the examples are increasingly concrete. The French Gendarmerie case shows one version of institutional autonomy: open-source adoption used to gain independence, flexibility, transparency, and the capacity to choose. Schleswig-Holstein shows another: an administration choosing to move 30,000 PCs toward LibreOffice, Linux, and other open-source systems as part of a digital sovereignty strategy.
Open data also gives organisations a powerful success story. Transport for London’s open data programme shows what happens when an organisation treats data as reusable infrastructure. More than 600 apps were powered by TfL data and used by 42% of Londoners, according to the Deloitte report commissioned by TfL. The professional point is simple: openness can create value outside the walls of the original organisation. By publishing reusable data, TfL enabled developers, businesses, passengers, and the transport system itself to benefit from a shared digital resource.
None of this means every organisation should replace every tool tomorrow. That would be reckless. Open-source adoption requires evaluation, support, security review, training, governance, and a sober understanding of total cost. The Synopsys report is a useful warning here: if organisations are already using open source across their codebases, then the professional question is not whether open source exists inside the organisation. It is whether anyone is governing it properly.
Before choosing a tool, organisations should ask: can we export our data? Can another provider support this system if the current one fails? Are we paying for long-term value or short-term convenience? Can this tool integrate with the rest of our work? Does it respect privacy and accessibility? Is there a community around it? Is it actively maintained? What skills would our team need? Are we becoming more capable, or more dependent?
For companies, open source can mean innovation without building everything from scratch.
For NGOs, it can mean autonomy without isolation.
For schools, it can mean digital literacy with the box opened.
For municipalities, it can mean public money creating public capacity.
For funders, it can mean supporting tools and knowledge that can be reused beyond one project cycle.
For professionals, it can mean learning to see technology not as a mysterious procurement category, but as part of organisational strategy.
Open source is not a shortcut around management. It is a reason to manage technology more intelligently.
10. Why this matters for democracy
Once we see the individual and organisational layers clearly, the democratic layer becomes impossible to ignore.
A democracy is not only a constitution, a parliament, or an election day. It is also the everyday infrastructure through which people access rights, information, services, education, participation, and accountability. That infrastructure is increasingly digital. If the systems that mediate public life are closed, expensive, non-interoperable, uninspectable, and impossible to repair locally, democracy becomes dependent on structures it does not fully control.
Citizens are asked to trust systems they cannot see. Public institutions are asked to govern through tools they cannot adapt. Communities are asked to participate through platforms designed around someone else’s priorities. Public money pays for digital infrastructure that may not be reusable by the public. Over time, this does something subtle but serious: it moves democratic capacity away from the institutions and communities that need it.
Open source does not solve democracy. It does not remove inequality, corruption, bad design, weak institutions, surveillance, or political conflict. It does not guarantee participation. It does not magically make public services kind, accessible, or fair. But it offers a different logic.
It says that the systems we depend on should be more inspectable. More adaptable. More reusable. More accountable. More capable of being localized. More open to public learning. More resistant to silent dependency.
Barcelona’s Decidim platform is one of the clearest examples of this democratic logic. Decidim is a free and open-source platform for participatory democracy, used for consultations, participatory budgeting, assemblies, and citizen proposals. Its best-known deployment, decidim.barcelona, had more than 120,000 registered participants, 126 participatory processes, 4,492 public meetings, 31,261 proposals, and 258,866 support votes as of June 2023. More than 14,000 proposals had already become public policies grouped into resulting projects whose implementation could be monitored.
This matters because democratic participation is not only about inviting people to speak. It is also about building systems where proposals, deliberation, voting, implementation, and accountability can be followed. When the platform itself is open source, other cities and communities can study it, adapt it, translate it, reuse it, and improve it. Democracy becomes not only a process, but a shared civic technology.
Ukraine’s ProZorro procurement system offers another powerful case. After the Maidan reformers from civil society, business, and government created a radically transparent, open-source e-procurement system so public contracts could be conducted electronically and made visible online. The Open Contracting Partnership reports that these reforms decreased corruption, increased competition, and saved $6 billion, while more than 100,000 citizen monitors helped ensure projects were delivered.
ProZorro is especially important because it connects the professional and democratic arguments. Procurement is not glamorous. It is forms, contracts, suppliers, budgets, eligibility, documentation, and oversight. But procurement is also where public money becomes roads, school meals, medicines, technology systems, repairs, infrastructure, and services. When procurement data becomes open and monitorable, democracy gains a practical instrument. Citizens, journalists, businesses, auditors, and watchdog organisations can see patterns that would otherwise stay buried.
Citizen science gives us a more environmental example. After the Fukushima disaster, Safecast emerged as a volunteer-driven effort to collect and publish radiation data. Safecast now maintains what it describes as the largest open dataset of background radiation measurements ever collected, with more than 150 million readings, and releases its data under a CC0 public-domain designation so anyone can use it without licensing restrictions.
That is not just a technical achievement. It is a civic image. People facing uncertainty did not wait only for distant institutions to produce knowledge. They built devices, gathered measurements, published data openly, and made invisible risk more visible. Open technology, at its best, does not simply distribute software. It distributes agency.
This is why open source is not just for nerds.
The world built with software is not just for nerds.
It belongs to the teacher trying to adapt a lesson. The student learning that technology can be opened, not merely consumed. The local official trying to serve citizens with a shrinking budget. The NGO trying to protect sensitive data. The small business trying not to drown in subscriptions. The parent wondering where their child’s information goes. The community trying to monitor air quality, repair devices, map risks, or build something that lasts.
The code beneath the floorboards is already there.
We walk across it every day.
This series is an invitation to look beneath them with curiosity, courage, and civic intelligence. Because beneath the code, there are choices. Beneath the choices, there are values. And beneath those values, there is a question every society eventually has to answer:
Who gets to build the systems we all depend on?
In the next posts, we will begin opening the floorboards one by one: cost, privacy, education, public services, security, open hardware, digital sovereignty, and the practical decisions organisations can make when they want more control over the systems they depend on.
