Start here
Open source in plain English, and how to use this site. No technical background needed.
What is open source?
Most software is a sealed box. You use it, but you cannot see how it works inside. Open source software is the opposite: the code is public. Anyone can read it, use it, and in most cases change it and share it.
It is usually free to use. It is often built by a community of people, sometimes by a company that also sells a paid version or a hosting service.
Does free mean worse?
Not always, and not always better either. Some free tools are as good as the paid ones for what you need. Some are rougher, younger, or need more setup. That is why every tool here has a "The catch" box. We tell you where it falls short.
What the labels on this site mean
The license lets you use, change and share the code. Examples of license names you will see: MIT, GPL, Apache, AGPL, MPL.
You can read the code and use it, but the license adds limits, for example on reselling it. It is free to use, but not open source in the strict sense.
Most of the code is open, but some parts are under separate terms, often paid or enterprise features. Check which parts you need.
How you will actually use these tools
There are three common ways. Each tool page says which fits.
- Download an app. You install it like any other program. Easiest. Example: OBS Studio.
- Use it in the browser. No install. Example: Excalidraw.
- Host it yourself. You run it on your own server so your data stays with you. It needs some technical comfort, and you handle updates and backups. Many of these tools also offer a paid hosted version if you prefer not to do that.
Hosting it yourself? Use Docker
If a tool says "self-host", the cleanest way to run it is usually Docker.
What is a Docker container?
A container is a sealed box that holds one program together with everything it needs to run: its settings, its libraries, the right versions of things. You start the box and the program just works, the same way on any computer.
The name comes from shipping containers. A shipping container fits any ship, truck or train because the outside is always the same, whatever is inside. A software container works the same way: your computer does not need to know what is inside, it only needs Docker to run the box.
- Image: the recipe or template. It is downloaded once from the project's official page.
- Container: a running copy of that image. You can start it, stop it and delete it.
- Docker: the program on your computer that runs the containers.
It is not a full second computer (that would be a virtual machine). A container is lighter and starts in seconds, and it shares your computer's engine while keeping the program apart from your other files.
Why Docker helps
- One setup for everything. Most self-hosted projects publish an official Docker image, so you do not install databases and dependencies by hand.
- Easy to try and easy to remove. If you do not like a tool, stop the container and delete it. Your system stays clean.
- Easier updates. Pull the new version and start it again.
- Separation. The tool runs apart from the rest of your computer, which is a sensible default.
What to know before you start
- Your data is not in the box. It lives in a "volume" or a folder you choose. If you delete that, the data is gone, so back it up.
- A container is not a security guarantee. It is a good habit, not a shield. Keep the tool updated.
- Do not open it to the whole internet by accident. Run it on your own machine or home network first. Put a login and HTTPS in front of it before you share it.
- It needs a one-time setup. You install Docker first. If you use it for a business, read Docker's terms for your company size.
Where to find the steps: open the tool's official site or source code link on its page and look for "Docker" or "Docker Compose" in the install guide. Follow that guide, not a random video.
Is it safe to try?
- Only download from the official site or the source code link on the tool page.
- Look at the last code update. A project that was updated recently is being looked after.
- Do not put your real passwords, photos or business data into something you have not checked. Try with test data first.
How to read a tool page
- Replaces
- The paid software this can stand in for, fully or for some tasks.
- License
- The rules for using the code. See the labels above.
- GitHub stars
- How many people bookmarked the project. A sign of popularity, not a measure of quality.
- Last code update
- The last time the code changed. Recent is a good sign.
- Paid version costs about
- An approximate price of the paid tool, with what it is based on. Prices change, so check the vendor.
- The catch
- Where the tool falls short or what to know before you switch.
How the savings counter works
Tick the tools whose paid version you use today. The counter adds up the approximate monthly prices and shows a yearly total. It is a rough guide, not a quote. Your ticks are saved only in your own browser. Nothing is sent to us.
Where do the tests come from?
The hands-on tests are on Instagram. Today the library shows what we verified at the source: license, activity and price. A tool gets a "Tested" mark only after we ran it ourselves. More on how we check.