Is self-hosting worth it? An honest look at time, money and risk

Short answer: it is worth it when you value control over data, have a steady need, enjoy or can spare the maintenance time, or the subscription cost grows with users or usage. It is not worth it when the service is business-critical and you cannot guarantee backups, security updates and someone to fix it at 2 a.m. The cost of self-hosting is mostly your time, not money.

What do you gain?

• Control of your data. It sits on hardware you choose, and nobody can change the terms or shut it down.
• Predictable cost. A fixed server bill instead of per-seat or per-usage pricing. This matters most with many users or large volumes.
• No arbitrary limits on records, automations or storage.
• Customisation. You can change settings or code that a vendor would never expose.
• Learning. You understand how your tools work, which pays back elsewhere.
• Privacy and compliance. Data stays in your country or inside your network.

What does it really cost?

• Setup time: hours for a simple app, days for a business system.
• Ongoing maintenance: updates, certificate issues, disk space, the occasional broken upgrade. For a small stack, a couple of hours a month. Some months, none. Some months, a whole weekend.
• Security responsibility. You patch it. If you do not, nobody does.
• Backups and recovery. Yours to build and to test.
• Availability. A hosted service has a team and redundancy. Your single server does not. Power cuts, a failed disk or an ISP outage are your problems.
• Your own time at a price. If an hour of your time is worth more than the subscription, the arithmetic changes.

When is it a bad idea?

• Email delivery for your business. Getting mail accepted by large providers is hard, and a poor reputation hurts you. Use a transactional mail service.
• A system that stops your company if it is down, with nobody on call.
• Anything you do not have time to update. An unpatched public service becomes a liability.
• Tools where the vendor's value is the network or data they hold.

When is it a good idea?

• Internal tools used by a known group.
• Software where the vendor charges per user and your headcount is large.
• Data you must keep on your premises, like patient or financial records.
• A business system sold to customers who want to own their installation. This is how I build Rechvix, OrderRestro and the other products on this site.

How do you decide?

Ask five questions.

• What happens to me if this is unavailable for a day? For a week?
• Who will apply security updates, and how will they know one is due?
• Has someone restored the backup recently?
• What would the hosted version cost over three years, including growth?
• Do I actually want to run this, or do I want the result?

If the answers are comfortable, try it. Start with one app. Write down how much time it takes for three months and compare that with the invoice you would otherwise pay. The numbers you collect yourself are better than any article, including this one. A cost walk-through is in self-hosted vs SaaS costs.