We are platform-agnostic on purpose, and we mean something specific by it. We do not resell anyone’s software, and we take no referral fees. That matters because it removes the reason most technology advice is quietly compromised. We have no incentive to steer you toward the tool that pays us instead of the tool that serves you.
Often the tool that serves you best is open-source software you host yourself. That is not a fashionable answer, and no vendor is buying ads for it, which is exactly why you rarely hear it. So here is the honest version.
What “host it yourself” actually means
Self-hosting sounds technical and a little intimidating. In practice it means the software runs on infrastructure you control, under your account, instead of on a vendor’s platform under theirs. The application itself is often free and open-source. What you pay for is the server it runs on and the work of setting it up and keeping it healthy.
You do not have to run it yourself, hands on the keyboard. Someone can manage it for you. The point of self-hosting is not that you become a system administrator. The point is that the arrangement is yours: you can move it, change who manages it, and keep it running no matter what happens to any single vendor.
When renting is the right call
We are not against software as a service. For a great many jobs, a good hosted product is the correct, boring, cost-effective answer, and we will tell you so. Renting makes sense when the tool is not central to your operation, when the monthly cost is genuinely low for the value, and when you have no particular need to own the data or the workflow.
Honest counsel cuts both ways. Sometimes the answer is: just pay for the subscription and get on with your work. We would rather say that than build you something custom you did not need.
When owning your stack wins
The calculation changes when the software becomes central to how you operate, when subscription costs climb with every user or record, or when the data inside it is the thing that actually matters. In those cases a self-hosted, client-owned stack tends to win on three fronts:
- Cost over time. Rent never stops rising, and it rises fastest exactly as you grow and can least afford surprises. Owned infrastructure has a floor.
- Continuity. A hosted product can be discontinued, acquired, or repriced out from under you. Open-source software you host cannot be taken away, because no one owns the off switch but you.
- Control of your data. When the system runs under your account, your data stays yours by default, not by the terms of a policy that can change next quarter.
The catch, stated plainly
Self-hosting is not free of trade-offs, and we will not pretend it is. Someone has to keep the server patched, backed up, and running. That is real work. The difference is that it is work you can hire, direct, and control, rather than a dependency you cannot influence at all. For software that matters to your operation, most clients decide that trade is worth making. Some do not, and that is a legitimate choice too.
What we will always do is show you the real comparison for your situation, including the parts that argue against our own involvement. When the right answer is a stack you host yourself, we will say so, set it up that way, document it, and make sure your people can run it. Best tool for you, not the tool that pays us. That is the whole idea.
Written by
Miles Bassett
Founder and principal craftsman at Prairie Code. He writes and speaks on deliberate AI adoption for small businesses and institutions.