Open source, and what it means when nobody is selling it to you

Open-source software has no licence fee because no single company owns the open-source project behind it. That same fact is the reason nobody is contractually obliged to support your particular installation of that software. Those two things are not separate features of open source software. They are one fact about open source, seen from the cost side and the accountability side at once — and understanding them together prevents most of the disappointment people report with open-source platforms.

What “open source” actually means for source software

The software’s source code is publicly available, and anyone may inspect it, modify it and redistribute it, generally under an open source licence that permits commercial use. A large, distributed community of developers contributes to the open-source software — fixing bugs, adding features, publishing extensions — with no central company deciding the roadmap. WordPress is the dominant open source example in the website world, and the same open-source pattern applies to countless other source software projects underneath it.

Why “free” is a partial description of open source software

No licence fee is real and genuinely valuable. It is also only one line item in the total cost of running the software. Hosting, a competent theme, extensions for anything beyond the basics, and — the item this whole cluster keeps returning to — ongoing maintenance, all cost money regardless of whether the core open source software itself is free. “Open source” describes the software’s licence, not the total cost of a working website built on open-source software.

Who is accountable when something goes wrong

This is the part that catches people out. There is no company to call, no support contract that comes bundled with the software itself, and no guaranteed timeline for a bug to be fixed, however serious it is. Some open-source projects have large, active communities that respond to serious security issues quickly and reliably. Others — particularly individual plugins within a larger ecosystem — may be maintained by one volunteer, sporadically, or not at all. The software being open source tells you nothing, by itself, about how well any specific piece of it is currently maintained. Check that project by project, plugin by plugin.

The commercial layer built on top of open source

A large commercial ecosystem exists precisely because open-source software has no vendor of its own. Hosting companies specialising in it, developers who build and maintain sites on it, premium themes and plugins sold by companies who are not the software’s original authors, and support services sold entirely separately from the software itself. None of this is a contradiction of “open source”. It is the market that forms specifically because nobody else is providing that accountability by default. The business decision is really about which parts of that commercial layer to buy.

What this means for choosing a plugin or theme

Because there is no central vendor vouching for quality, the diligence shifts to the buyer. Checking when a plugin was last updated, how many active installations report using it, whether its support forum shows responses from the developer, and whether it has a track record of prompt security fixes: these are the practical substitutes for the vendor guarantee a hosted platform’s own built-in features would otherwise carry. A plugin last updated years ago, with no visible support activity, is a real risk regardless of how well it currently appears to work.

Why this is not an argument against open source

The trade genuinely favours a business willing to either build the diligence and maintenance capability described above, or fund someone else to. In exchange, it gets software with no ongoing fee, a functional ceiling set only by what can be built rather than by what one company’s roadmap includes, and no risk of a vendor discontinuing the product entirely and forcing a migration on someone else’s timeline — the risk covered in what happens when a platform is discontinued.

Why open source is not the same claim as “free to run”

The absence of a licence fee is genuinely valuable, and it is easy to let that single fact stand in for a broader claim that open-source software is cheap to operate overall. It is not, once hosting, a competent theme, any commercial extensions genuinely needed, and — the largest and most consistently underestimated line — ongoing maintenance labour are added up. The honest comparison against a subscription-based hosted platform prices all of that in, rather than comparing a hosted platform’s all-in fee against only the open-source software’s licence cost of zero.

Contributing back, briefly, and why it matters to the ecosystem’s health

Large open-source projects like WordPress rely on a mix of volunteer contributors, sponsoring companies and paid core contributors to keep the software itself maintained. A business does not need to contribute code to benefit from the ecosystem, but understanding that the “free” software is produced by real, ongoing human effort — not a static, finished product — helps explain why some parts of the ecosystem are excellent and well maintained while others, particularly smaller or less-used plugins, can be neglected entirely by a single volunteer who has moved on.

Forking, briefly, as the ultimate open-source safety net

Because the code is open, if a project’s stewardship ever genuinely failed, another group could in principle take the existing code and continue it independently — a “fork.” This has happened with other open-source software historically and is a real, structural safeguard against a project simply vanishing overnight, even though it is a slow, disruptive process rather than a smooth continuation, and not something a small business should plan around as a realistic contingency for its own site.

Licence, license, copyleft, free software and proprietary software: the Open Source Initiative’s actual terms

“Open source” is a specific, defined term, not a loose synonym for “free software” in general. The Open Source Initiative maintains the formal open source definition most open-source licences are checked against, made public and openly revisable itself. Not every free-to-download program meets the open source definition. Some free software works under stricter terms that still count as open source, and some free downloads are not open source at all despite the marketing language borrowing the term. Australian content on this topic almost always writes “licence”; most global source material about open source, including the Open Source Initiative’s own site, uses the American spelling “license” — both spellings, and their plural forms licences or licenses, mean the same thing here.

What “copyleft” actually means for WordPress

WordPress itself is released under the GPL, a “copyleft” licence. Anyone can use, modify, edit and redistribute the source code, but a derivative work built on GPL code generally has to be released under compatible licence terms too, rather than turned into closed, proprietary software. Copyright still exists and is still held by the people who wrote each piece of the code. Open source is a licence granted over that copyright, not an absence of it.

Why this rarely matters day to day, but sometimes does

This detail rarely matters day to day, but it is why a WordPress theme or plugin marketplace works the way it does, and why proprietary hosted platforms like Wix or Squarespace, built on closed source code a business cannot inspect or fork, sit on the opposite side of this specific licence question from WordPress. Open source, in other words, is a specific legal and technical arrangement around source code and software licensing — not a vague marketing claim that software is somehow more open in spirit than its proprietary competitors. The open-source software running underneath a WordPress site is open in this precise, checkable sense, and that is the whole of what the word promises.

Source code access, licenses generally, and what it actually buys a business that never reads proprietary software’s code

Very few small-business owners, or even most developers working on a site day to day, ever personally read WordPress’s own source code, and that is fine — the practical value of source availability is that someone, somewhere, independent of any single vendor, can inspect it when something needs checking, which is a structural property of the licence rather than something an individual business has to exercise itself. Proprietary software offers no equivalent option regardless of how good its own internal security review process is, because nobody outside the vendor can verify the claim independently.

Where to go from here

What this specifically means for WordPress, the dominant example, is set out in what WordPress actually is. And the practical consequence of nobody being contractually obliged to maintain the software is the entire subject of maintenance.