LICENCES AND PRICING

Free, open source, freemium: what the labels on software really mean

Free of charge, free software, open source, freemium and free trial are different things. Learn how to read them and avoid surprises.

By the Software Alternative editorial team · Published 2026-09-30

Why the labels matter

Software listings use a handful of words that sound alike and mean different things. Mixing them up leads to real problems: a team builds a workflow on a free tier that is later capped, or assumes an open-source project is free to host at any scale. Knowing what each label promises, and what it does not, makes comparisons more honest.

Free of charge is a price, not a licence

A tool is free of charge when you can use it without paying. That says nothing about whether you may modify it, redistribute it or use it commercially. Some free-of-charge software is closed, and its terms can change. Always look for a statement about commercial use if you are a business or a freelancer, because personal-use-only terms are common.

Visual Studio Code is a useful example. Its core editor is free for private and commercial use, yet the Microsoft-distributed binary is under Microsoft's own licence terms, which are different from the MIT licence that covers the source code. So the same name can carry more than one set of rules depending on what you download.

Open source and free software describe rights

Open source and free software (in the sense of freedom) describe what you are allowed to do with the source code: inspect it, change it and share it, subject to a licence. GIMP is distributed under the GNU General Public License, which is one such licence. Others, like MIT, are more permissive. The specific licence tells you what conditions apply if you modify or redistribute the software.

Open source does not automatically mean no cost, and it does not mean the company behind a hosted version is free of charge. It also does not guarantee a project is well maintained. It means the code is available under terms that allow certain uses.

Derived builds and what changes

VSCodium shows how a build can differ from its source. It supplies community-built binaries from the Visual Studio Code source, distributed under the MIT licence with telemetry disabled. That does not mean every Microsoft service or extension will work unchanged, and its own record advises checking compatibility and licensing for each extension you need. When you choose a derived build, you are choosing a different distribution with its own support arrangements.

Freemium, free plans and trials

Freemium means a free tier exists alongside paid ones. The free tier is designed to be useful and to make you consider upgrading. Dropbox's Basic plan, for example, offers a small storage allowance with paid plans adding capacity and recovery options. Read the limits: storage, history length, collaborators, export options and AI allowances are the usual ceilings.

A free trial is different. It lets you use paid features for a period, then expects payment or reverts. A free plan continues indefinitely but with limits. Confirm which one you are getting, and whether a card is required at the start.

Obsidian shows a common hybrid: the application itself is free, including for commercial use, while optional Sync and Publish are separate paid services. The core promise and the add-ons have different prices.

Telemetry, data and what the software sends home

Licence and price are only part of the picture. Applications can also collect usage data, send crash reports or connect to cloud services by default. Some projects document this clearly and let you switch it off; others make it harder to find. VSCodium’s own description highlights that telemetry is disabled in its distribution, and Visual Studio Code’s record notes that AI features can be disabled when you do not need them.

If privacy or compliance matters to you, look for a settings page or documentation that lists what is collected and how to turn it off. Then check again after major updates, because defaults can change.

Commercial use and business risk

Personal use is rarely the problem; business use is. Before adopting a tool for a company, confirm that its terms allow commercial use, that any extensions or plug-ins you need carry compatible licences, and that you understand what happens if the vendor changes its terms. Open-source licences reduce some of this risk because you can keep using a version you already have, but they do not remove the need to read the conditions.

For hosted products, also ask what happens to your data if the company is acquired or the free tier disappears. A written export plan is the practical answer.

Questions to ask before you rely on a label

Use the questions below as a quick filter when a product page says “free”.

  • Free for whom: personal use, students, nonprofits, businesses?
  • Free until when: forever, for a trial period, or until a usage cap?
  • Which parts are free: the app, the cloud service, the AI features?
  • What licence covers the code, and does it differ from the binary?
  • What happens to my data if I stop paying or the plan changes?
  • Who maintains it, and how are security fixes delivered?

Why our catalogue says “unknown”

When we cannot confirm a licence or a price from an official source, we record it as unknown instead of guessing. An unknown is honest information: it tells you to check before relying on the product for that point. Our methodology page explains how unknown values affect match scores.

This guide gives general advice and is not a hands-on review. Product details come from the official sources recorded in our catalogue and can change, so check each vendor's current terms before you decide. See our methodology for how we handle unknown information.