The self-hosted ecosystem has a duplication problem, and that's killing the projects you depend on

Published Aug 21, 2026, 2:00 PM EDT Beginning his professional journey in the tech industry in 2018, Yash spent over three years as a Software Engineer. After that, he shifted his focus to empowering readers through informative and engaging content on his tech blog – DiGiTAL BiRYANi. He has also published tech articles for MakeTechEasier. He loves to explore new tech gadgets and platforms. When he is not writing, you’ll find him exploring food. He is known as Digital Chef Yash among his readers because of his love for Technology and Food. Self-hosting gives me something I don't get with most mainstream software: control. I can choose where my data lives, decide which services run on my hardware, and build a setup around the way I actually work. That freedom is a big reason I keep coming back to it. But the more time I spend self-hosting, the more complicated the ecosystem starts to feel. There are countless applications, containers, and alternatives competing for attention. Finding a tool is easy. Knowing which one is worth trusting with my data is much harder. Open source doesn't have a shortage of ideas It has a shortage of maintainers I don't think the self-hosted ecosystem has an idea problem. If anything, I think we have the opposite problem. Every time I look for a tool to solve a specific problem, I find several projects trying to approach it in slightly different ways. That's one of the things I love about open source. Someone can look at an existing application and think, "I can make this better." Maybe they want a cleaner interface, a simpler setup, fewer features, or a completely different approach. I've done the same thing when looking for tools for my own setup. The result is an ecosystem full of interesting ideas. There is always something new to test, another GitHub repository to bookmark, or another Docker container that promises to improve a part of my workflow. But having more ideas doesn't automatically make the ecosystem stronger. At some point, the number of projects matters less than what happens to them after the initial excitement wears off. The "reinventing the wheel" cycle Forking and reinventing the wheel can leave everyone maintaining the same software I keep seeing the same pattern in self-hosting. A new project appears, and after looking at it, I realize it does almost the same thing as an app I already know. The interface may be different, or it may add a few extra features, but the basic idea is often the same. Building from scratch can sometimes feel easier than changing someone else's code. But this can create a cycle where we keep building the same types of apps again and again. I don't think every new project is unnecessary. Some are genuinely better or solve a different problem. But when the differences are small, I wonder if we're creating more software than the community can realistically support. Vibe coding has made it worse The GitHub repo is easy; five years of maintenance isn't. Vibe coding has made it much easier to turn an idea into a working self-hosted app. I can see why that's exciting. Someone with a good idea can now use AI to build something useful without spending months writing every part of it. But I think this is also making the problem bigger. As observed by Adam Conway from XDA, projects such as BookLore show how quickly AI-assisted development can produce a large amount of code, while raising questions about how well that code is tested and maintained. That's what concerns me about vibe coding. Creating another project is becoming easier, but keeping it healthy isn't. AI can help me build features quickly, but it can't replace years of testing, security work, updates, and maintenance. New doesn't always mean better The projects I depend on are the ones I don't want to replace I don't switch to self-hosted apps overnight. When I find something interesting, I usually test it with a smaller amount of data for a few weeks. I want to see how it fits into my workflow before moving everything over. I recently did this with PDF tools. I was using Stirling-PDF for my PDF work, but I decided to give BentoPDF a proper try. I started with a smaller set of files instead of moving everything at once. After a few weeks, I found BentoPDF simpler and better suited to how I work. Once I was confident, I moved my PDF workflow over completely. This is how I prefer to handle self-hosted apps now. I don't want to keep jumping between projects just because something new looks interesting. I want to test it, use it for a while, and then decide whether it's actually worth the switch. Once an app becomes part of my workflow, replacing it takes time. That's why I now care more about finding something I can stick with than constantly chasing the newest project. I don't think we need to stop building new self-hosted apps. New ideas are important. But every project should have a reason to exist beyond simply being another alternative. For me, the focus should be on building tools that solve real problems and are worth sticking with. A smaller number of strong, useful projects would be more valuable than endless alternatives that users constantly have to replace.