Open-source software is free. Running it isn't. Here's how to tell if it's worth it
"If it's free, why would I pay anyone?" It's the obvious question when someone suggests an open-source tool instead of a paid one. It's a fair question, and the honest answer is that it isn't always cheaper.
The software is free. Running it properly isn't. Whether you come out ahead depends mostly on one number: how many people use it.
What you're actually paying for now
Most business software is priced per person, per month. Two examples, checked today on the vendors' own pricing pages:
- Slack Pro is £5.75 per user a month "when paying annually", or £7 paying monthly.
- 1Password Business is $8.99 per user a month, billed yearly. That's about £6.80.
Together that's roughly £12.55 a person a month, or about £150 a year each. Not much for one person. For a team of 20 it's around £3,000 a year, for chat and passwords alone, before files, email or anything else.
It grows every time you hire someone, and whenever the supplier decides it should.
What "free" software actually costs
Swap those for open-source tools (Zulip for chat, Vaultwarden for passwords, say) and the licence fees go to zero. But four costs take their place.
A server. Something has to run it. For a small team that's usually a modest virtual server in a UK data centre. It isn't nothing, and server prices have gone up this year as memory has got more expensive.
Setting it up. Installing it, locking it down, and moving your data across from the old service. For something small this is quick. My own visitor stats tool, Umami, took about an hour. A password manager the whole team relies on deserves rather more care than that.
Keeping it updated. Open-source tools get security fixes just like paid ones. The difference is that nobody applies them for you. Someone has to notice the update, test it and install it. Every month, for as long as you use it.
Backups that work. With a paid service, backups are their problem. On your own server, they're yours. And a backup only counts if you've tried getting something back.
Whether you do all that yourself or pay someone, it adds up to a fixed cost. Roughly the same each month whether five people use it or fifty.
The break-even sum
That's the whole trick. Paid tools cost a bit for every person. Self-hosted tools cost a fixed amount for everyone.
So the sum is simple. Add up what you pay a year for the tools you'd replace. Then get a yearly figure for running the alternatives: server, setup spread over a few years, and the time or fee for looking after them. Compare the two.
A made-up example. Say running Zulip and Vaultwarden properly costs you £1,500 a year all in. With Slack Pro and 1Password at about £150 a person, you'd need around ten people before you break even. At five people you're paying double. At 30 you're saving around £3,000 a year, and every new starter after that is free.
Your numbers will differ. The shape won't.
When I'd tell you not to bother
You're three people. The per-user fees are small and the fixed costs aren't. Pay the subscription and spend your time on something else.
Nobody will look after it. An open-source tool installed once and then forgotten is worse than the paid version. In a year it'll be out of date, and in two you'll be scared to touch it.
The paid tool is wired into everything. If your chat talks to your helpdesk, your calendar and three other apps, moving it is a bigger job than the price comparison suggests. Count that work in the sum.
When it's worth it even if the money is close
Sometimes the numbers roughly match and it's still the better choice. If you want your data in the UK, on a server you control. If you're hiring and don't want every new starter to put the bill up. Or if a supplier has already put its prices up on you once, and you'd rather not be there again.
And if the project ever changes its licence, your copy and your data stay yours.
If an open-source tool nearly fits but not quite, it can usually be changed. That's the sort of job the team at Dev Partners take on with custom software, rather than building the whole thing from scratch.
What to do this week
Open your bank statement or card bill and list every software subscription that's charged per person. Write down what each costs a year and how many people actually use it.
Then pick the biggest one and look it up in my list of open-source alternatives. Each page shows what the paid tool costs and what the open-source option does and doesn't do.
If the sum comes out close, it's worth a conversation. If it doesn't, keep paying, and at least you'll know why.
Liked that? Get the next one by email
When a security flaw lands that could affect your server, I'll email you what it means and what to do. Plus the odd opinion piece. Not often, no spam.