The debate between self-hosted and SaaS is not new, but becomes more relevant each year. The TCO, the total cost of ownership over multiple years, is often surprising. While SaaS attracts with low-cost entry packages, self-hosted solutions often incur hidden costs you do not see at first. This article analyzes concrete categories and helps you make the right decision.
The TCO Comparison: SaaS Is Not Always Cheaper
Many decision-makers assume self-hosted is automatically more expensive. That is a misconception. The reality is more nuanced.
Seemingly inexpensive SaaS solutions quickly become expensive through add-on costs. Each additional user costs money. Each additional feature requires an upgrade. Each additional gigabyte of storage adds up. After three years, an organization that started at 20 dollars per month has often spent 500 dollars per month. This is not a rare phenomenon.
Self-hosted, by contrast, has high upfront costs and continuous operating costs. Servers cost money, regular updates require effort, and resilience needs redundant infrastructure. But after the amortization phase, typically two to three years, costs are often significantly lower than SaaS.
The rule of thumb is: under ten users, SaaS is often cheaper. At thirty users or more, self-hosted regularly pays off. In the middle range between ten and thirty users, you must calculate carefully.
Case Study 1: Source Control (GitLab CE vs GitHub Enterprise)
Consider a typical scenario: a developer team of ten people needs a version control system. The comparison between GitLab CE and GitHub Enterprise is instructive.
GitHub Enterprise costs 231 dollars per user per year (as of 2025). For ten developers, that is 2,310 dollars per year. Add storage fees for large repositories and Actions minutes that quickly exceed limits. A realistic cost calculation comes to 3,500 to 4,000 dollars per year.
GitLab Community Edition is free. But self-hosted operation costs money. A typical setup: a virtual server with 8 cores and 16 GB RAM costs 100 to 200 euros per month at AWS or Hetzner. Installation requires about 40 hours of work from an experienced DevOps engineer, costing roughly 2,000 euros. Updates and monitoring fall to your team. Realistically, 20 to 30 hours per year for maintenance equals another 500 to 1,000 euros.
First year calculation: infrastructure 1,500 to 2,400 euros, setup 2,000 euros, maintenance 500 to 1,000 euros. Total 4,000 to 5,400 euros.
This does not look much cheaper on first glance. The difference becomes clear over time. In year two and three, setup and initial learning curve disappear. Only infrastructure and maintenance remain, totaling 2,000 to 3,400 euros per year. After three years, GitHub Enterprise has cost over 10,000 euros, GitLab self-hosted about 8,000 euros.
But the decisive argument is that payoff begins here. GitHub Enterprise continues at the same cost in years four and five. GitLab stays at 2,500 to 3,500 euros. After five years, self-hosted is about 5,000 euros cheaper. And you maintain complete control over your data.
Additionally, with GitLab CE you can operate unlimited private repositories. GitHub Enterprise includes private repositories, but each additional feature like SAML SSO costs extra.
Case Study 2: Analytics (Plausible vs Google Analytics)
A realistic scenario: a website with 100,000 monthly visitors needs analytics data.
Google Analytics is free. That is the first argument for many organizations. But the costs are hidden: you hand all your data to Google. Google processes this data, stores it, and uses it for its own advertising business. For many organizations, especially those with privacy-conscious customers, this is not acceptable.
Plausible, a privacy-friendly analytics tool, costs 20 dollars per website per month (200 dollars at annual billing). That is fair, but for five websites it already comes to 1,200 euros per year.
Self-hosted analytics is possible with open-source tools like Matomo. A small server at Hetzner costs 10 to 20 euros per month. Installation and setup take 20 to 30 hours, about 1,000 euros. Monthly maintenance is minimal, about five hours per year, 250 euros.
First year calculation: infrastructure 150 to 240 euros, setup 1,000 euros. Total 1,150 to 1,240 euros for full control of your data.
After three years, Plausible would have cost 3,600 euros. Matomo self-hosted costs about 2,000 euros (one server, nine hours per year maintenance). The advantage is larger: you own your analytics data, can use it as you wish, and are not dependent on a third party.
Additional argument: if you run many websites, thirty or more, Plausible at around 600 dollars per month becomes extremely expensive. A self-hosted Matomo on a slightly larger server stays at 50 to 100 euros per month.
Case Study 3: Team Chat (Mattermost vs Slack)
Chat systems are ubiquitous and profoundly influence team culture. Slack costs 8 dollars per user per month (Standard plan). For a team of thirty people, that is 2,880 dollars per year. With video calls and additional integrations, another 1,000 to 2,000 dollars per year quickly accumulates.
Mattermost is an open-source alternative. The Community Edition is free. Operation requires a small server, roughly 50 to 100 euros per month at Hetzner or AWS. Installation and configuration take 30 to 40 hours, about 1,500 euros. Regular maintenance is about ten hours per year, 500 euros.
First year calculation: infrastructure 600 to 1,200 euros, setup 1,500 euros, maintenance 500 euros. Total 2,600 to 3,200 euros.
In the first year, Slack is actually cheaper if you only pay for the basic plan. But Slack limits message history without a premium plan. Enterprise complexity adds costs quickly. After three years, Slack reaches about 8,640 euros, Mattermost about 5,200 euros.
Additionally, Mattermost you can extend without waiting for Slack to add features. You can build integrations, modify the code, and maintain complete control over the platform.
Case Study 4: Password Management (Vaultwarden vs 1Password Business)
A smaller example, but instructive: password management for an organization with 20 employees.
1Password Business costs 5 dollars per user per month. For twenty people, that is 1,200 dollars per year.
Vaultwarden (a self-hosted Bitwarden server) costs essentially nothing for the software. A small server costs 30 to 50 euros per month. Installation takes about ten hours, 500 euros.
First year calculation: infrastructure 400 to 600 euros, setup 500 euros. Total about 1,000 euros for complete control over your passwords.
After three years, 1Password has cost about 3,600 euros. Vaultwarden costs about 1,900 euros. More importantly: you can ensure your passwords truly reside only in your system, not with a US provider and all its data protection obligations.
When Self-Hosted Makes Sense
Self-hosting is worthwhile in several scenarios.
Data sovereignty is often the primary argument. If you have sensitive business data, must meet compliance requirements, or have a strong data protection consciousness, self-hosted is attractive. You maintain full control and need not rely on external providers.
Cost predictability speaks for self-hosted. SaaS providers regularly raise prices. A feature included in the free plan today costs extra tomorrow. With self-hosted you pay once for infrastructure and then predictably.
Foreseeable cost structure matters for large teams. At about thirty users or more, self-hosted regularly becomes cheaper. At one hundred users, self-hosted is often half the cost of comparable SaaS.
Customization is an underappreciated argument. With self-hosted you can tailor the software exactly to your workflow. This saves time in daily operations and produces better productivity gains.
Compliance and regulatory requirements speak for self-hosted. The EU AI Act, GDPR, and various industry standards may require that data does not go to US providers. Self-hosted solves many of these requirements.
When SaaS Wins
But SaaS has clear advantages that should not be underestimated.
Small teams under ten people are often better served with SaaS. The administrative overhead is simply too high.
If you lack operations expertise, SaaS is safer. Not every organization has a DevOps engineer or a team with infrastructure know-how. A system outage in self-hosted can be critical if no one can manage the infrastructure.
Quick scalability is a SaaS advantage. If you grow rapidly and infrastructure must scale with you, SaaS is simpler.
Redundancy and fault tolerance are often better with established SaaS providers. Building a large cloud infrastructure with geographic distribution is expensive. A good SaaS provider already has this.
Maintenance and updates happen automatically. You need not worry about patches, security updates, or new versions.
The Hidden Costs of Self-Hosted
Before deciding on self-hosted, you should know the hidden costs.
Backup and disaster recovery are not trivial. A functioning backup strategy takes work. Daily backups consume storage and bandwidth. In a disaster, you must be able to restore a system. Testing this takes time. Realistically, ten to twenty hours per year for backup management and testing, plus storage costs.
Monitoring and alerting matter. A system that fails and you do not know is bad. You need monitoring that alerts you to outages. This can be automated but requires setup and configuration.
Security patches require your attention. A self-hosted system you must also patch yourself. This means regular, sometimes urgent updates. When critical security updates arrive, you must act, not wait.
Scaling requires expertise. As your system grows and gains users, a small server cannot keep up. You must upgrade to larger hardware, possibly distribute across multiple servers, and build load balancing. This demands expertise.
Licensing can surprise you. Some open-source systems have unexpected licensing costs. GitLab, for instance, has different editions. Community Edition is free, but some features exist only in Enterprise or Ultimate. You must know this.
Common Decision Mistakes
A frequent mistake is underestimating operating costs. Operating costs are not just infrastructure, but also the salary for your infrastructure staff. One person working ten hours per month on a system costs 6,000 euros per year at 50 euros per hour.
Another mistake is ignoring opportunity costs. If your DevOps engineer spends ten hours per month on your system, he cannot work on other important projects. That costs money indirectly.
Some organizations underestimate their own technical capacity. “We have a DevOps engineer, so we can do self-hosted.” Not always true. One engineer cannot maintain all systems alone.
Another mistake is ignoring vendor lock-in. With SaaS you depend on the provider. But with self-hosted you also depend, just on the open-source community and your own team. Running an abandoned open-source project is also a lock-in.
Your Decision Framework
Here is a practical framework for your decision.
If you have fewer than ten users or will grow quickly, use SaaS. The effort for self-hosted is too high.
If you have between ten and thirty users, calculate concretely. Look at the TCO over five years and include hidden costs and opportunity costs.
If you have more than thirty users, self-hosted is very likely cheaper. The question then is whether your infrastructure capacity suffices.
If data sovereignty or regulatory requirements matter, lean toward self-hosted. Costs are secondary, control is primary.
If you lack infrastructure capacity, stay with SaaS, even if costs are higher. An outage of an important system costs more than any SaaS fee.
Important related articles are our pieces on DevOps for mid-market: a pragmatic entry and Infrastructure as Code with Terraform and Pulumi. We also recommend our article on Open Source for SMEs for additional context on self-hosted decision-making.
Frequently Asked Questions
Is open-source software really free?
The software is free, but operation costs money. Open-source means the source code is available for you to see and modify. It does not mean operation is free. You pay for infrastructure, updates, maintenance, and support. Hidden costs like storage and bandwidth often apply too.
Can I have redundancy and high availability with self-hosted?
Yes, but it costs extra. You need multiple servers, database replication, and possibly a load balancer. This makes infrastructure more complex and expensive. With ten servers instead of one, monthly infrastructure costs roughly double.
What if the open-source project is abandoned?
That is a real risk. If a project has no active maintainers, it receives no updates. You must then write patches yourself or migrate to another system. That is a real cost element often underestimated. Ensure projects are actively maintained.
How quickly can I migrate from SaaS to self-hosted?
That depends on the system. Some migrations are simple because export formats are standard. Others are labor-intensive because many integrations must be rebuilt. In your decision, consider that migration can cause downtime and data loss if not planned well.
If I use self-hosted, do I also need support?
Support is optional but often worthwhile. Many open-source projects offer commercial support. GitLab offers various support levels, as does Mattermost. Support costs but saves time when problems occur. Factor this into your calculation.
The decision between self-hosted and SaaS is not trivial. It depends on many factors. We help you conduct this analysis and make the right decision for your company. Contact our cloud consulting team for a free analysis.
