This is an automated archive made by the Lemmit Bot.
The original was posted on /r/opensource by /u/514sid on 2025-07-13 14:27:38+00:00.
I originally posted this on my blog but thought it fits well here too. I’ve removed mentions of my own service to focus on the main idea.
Since I decided to make my software open source, one question keeps coming up:
Why not just keep the product closed, start earning money, and avoid the risk of someone using your code to build a competing business?
I get it. Open sourcing can seem risky — like handing potential competitors a shortcut. But from the beginning, I accepted that possibility. And honestly, I’m completely okay with it.
Why open source was a deliberate choice
Many tools in my industry today are closed-source, outdated, complex, and expensive. I set out to build something different: a modern, easy-to-use, fully open-source alternative that people can trust and extend.
Choosing a permissive license like MIT allows anyone to use, modify, and build commercial products on top of the software. This encourages experimentation, collaboration, and adoption — without legal barriers.
Open source is more than just sharing code. It’s about building trust, expanding reach, and creating a real community around the project.
It’s more than just code
Having the source code doesn’t automatically create a business.
Running a successful service requires much more: customer support, marketing, operations, infrastructure, trust, security, and long-term commitment.
Anyone can host the software, but turning it into a reliable business people trust and rely on — that’s not easy. And that’s exactly why I’m not worried.
Open source benefits everyone
Some users want to self-host — not to resell, but simply to meet their own needs. These might be small teams, nonprofits, schools, or companies with internal requirements.
Open source gives them a free, flexible, modern solution that avoids expensive software licenses and long-term vendor lock-in.
If a managed service shuts down, users can switch providers or host the software themselves without losing their setup or data.
Also, companies might start with a managed service for a small number of users or devices, but as they grow, costs can increase — prompting them to switch to self-hosting to save money or gain more control. Open source makes that transition smooth without requiring a complete overhaul.
This kind of freedom helps grow the ecosystem and brings valuable real-world feedback that improves the software for everyone.
Final thoughts
Self-hosting isn’t free just because the source code is open. Someone still needs to maintain, update, and secure the software — and that can be a significant responsibility.
For businesses with just a few users or devices, using a managed service is often simpler, more reliable, and ultimately more cost-effective.
That’s why there’s plenty of room for managed services built on top of open source projects — offering convenience and support for those who don’t want to handle everything themselves.
And I’m completely okay with others launching their own managed services based on my open source code.