What Does OSS Mean in Software?

OSS stands for open source software, software whose source code is published under a license that lets others view, modify, and distribute it. That is the answer in one line. Everything else is about what that definition actually guarantees and what people commonly confuse it with.

The term was formalized by the Open Source Initiative in the late nineties. The OSI published ten criteria that a license must meet to be called open source: free redistribution, source code available, permission to create derived works, no discrimination against people or fields of endeavor, and a few more. The practical core is simple. Open source means the code is readable and reusable, not just free to download.

Most people get two things mixed up with open source. The first is freeware. Freeware is software you can use without paying, but you get no source and no rights to modify or redistribute it. WhatsApp is freeware. You use it, that is all. Open source is freeware plus rights. You can even sell open source software, so "free" and "open" are not the same axis. Some software is both free and open source, like most of Linux. Some is paid and open source, which is how Red Hat built a business.

The second confusion is public domain. Public domain means the author has abandoned copyright entirely, so no license is needed at all. Most open source does not work that way. MIT, GPL, and Apache keep the author's copyright and grant you permission under explicit terms. The license is the legally precise thing that makes the openness real. No license file, no rights, even if the code is sitting in a public GitHub repo.

The examples you already know are mostly OSS. Linux and Git are GPL. Node.js and React are MIT. Kubernetes is Apache 2.0. PostgreSQL has its own permissive license. Firefox is Mozilla Public License. The list covers operating systems, compilers, databases, browsers, and the front end of half the web. The odds are high that your stack already depends on more open source code than you realize.

Why does the label matter in practice? When a client or a procurement team writes "must be open source" into a requirement, they usually mean one of three things: no vendor lock-in, the ability to inspect code, or no licensing fees. The first two are guaranteed by the definition. The third is not. Freeware gives you the "no fees" part and nothing else, so the term separates "cheap" from "open".

Here is the failure mode I have seen. A Bangalore consultancy bids on a government RFP that states all delivered software must be open source. The team reads that as "must be free", proposes a proprietary product with a free tier, and the bid dies in compliance review. Had they read it as "source available under an OSI-approved license", they could have proposed building on open components and shown the exact license on every dependency. Same product, different reading of four words.

For how the rights actually work in practice, including which licenses let you build commercial products, read the licensing guide. If you are looking for projects to start with, the beginner's guide to finding open source projects is a better next step.