← Back to blog
web-developmentself-hostingsaasinfrastructure

Self-Hosting vs. Enterprise Subscription: When Own Infrastructure Is Worth It

SaaS or self-hosting? An honest comparison based on market data: cost development, SaaS sprawl, vendor lock-in, EU Data Act and TCO calculation over 3 years.

· Valorferrum

The software landscape for businesses is dominated by subscription models (SaaS). For almost every task – from CRM to project management to email marketing – there is a cloud solution that is ready to use immediately. That is convenient. But this convenience has a cost structure that often only becomes visible after one or two years.

I describe here the differences between SaaS subscriptions and self-hosting based on market data: How are cloud expenses developing? How many tools typically accumulate? What does vendor lock-in mean economically and regulatorily? And what does an honest cost calculation over three years look like? No blanket recommendations, just a technical and economic assessment.

1. Cloud and SaaS spending is growing in double digits. Gartner forecasts global public cloud end-user spending for 2024 at around 679 billion US dollars – growth of about 20 % year-on-year. Subscriptions are structurally getting more expensive, not cheaper: price increases and usage-based pricing are the norm in the SaaS market, not the exception.

2. A relevant share of cloud spending is considered unused. In the annually published “State of the Cloud” report by Flexera, surveyed organizations themselves estimate a quarter to a third of their cloud spending as wasted (self-reporting, exact annual fluctuations see review). Cost intransparency is therefore not an isolated case, but a systemic feature of the rental model.

3. SaaS sprawl: The number of tools grows faster than the management. IT management reports (e.g., Zylo) count several hundred SaaS applications in large enterprises, typically dozens in SMEs – a part of them without central management (“Shadow IT”). Each individual subscription is small; the sum is not.

And the counterpole is not a niche model: According to W3Techs, over 40 % of all websites worldwide run on WordPress – an open-source system that is classically self-hosted. Open-source surveys (OpenLogic / Linux Foundation) show that over 90 % of organizations use open source. Self-hosting is therefore not a retro decision, but the market standard on the web – just invisible because it runs in the background.

The SaaS model: rented convenience

Why SaaS is often chosen:

  • Immediate usability: No server configuration, no installation. Create account, get started.
  • No maintenance: Updates, security patches and backups are the provider’s responsibility.
  • Scalability: With more users or data volume, the next package is booked.

The typical disadvantages that become visible in the market data:

  • Cost escalation: SaaS prices scale with usage (users, contacts, API calls). What starts at €29/month can cost multiples with growth – reinforced by the double-digit market growth trend.
  • Sprawl effect: Dozens to hundreds of individual subscriptions without central overview; part of them are no longer actively used but still paid for (see Flexera waste share).
  • Vendor lock-in: Data often lies in proprietary formats. A switch can take months or fail due to missing export functions.
  • Egress economics: Public price lists of large cloud providers price data outflow (e.g., AWS outbound transfer in the cent range per GB). Moving out is therefore not only organizationally, but directly priced in.
  • Data sovereignty: Sensitive data (customer data, tracking data, internal documents) lies in a third party’s infrastructure – including their terms and sub-processors.

The self-hosting model: own control

Why self-hosting is often chosen:

  • Full data control: The data lies on a server over which the company has administrative control. For tracking and customer data, this is often the decisive factor (see privacy-oriented tracking).
  • Predictable costs: A VPS costs a fixed monthly amount (market-typical approx. €5–20), independent of user or contact numbers – as long as the resources are sufficient.
  • No lock-in: Open-source software can be modified, extended and moved to any server.
  • Mature ecosystems: With WordPress (> 40 % market share on the web) and modern generators like Astro, mature, performant self-hosting stacks exist. Your own website on own infrastructure is the living proof: Astro, self-hosted, Lighthouse 90+ (see Tech Stack).

The typical challenges:

  • Maintenance effort: Updates, patches, backups and monitoring are your own responsibility.
  • Technical know-how: Linux, Docker, web servers and databases are basic prerequisites.
  • Availability: In case of outages, recovery is your own task – without a support contract there is no external help.

The true costs: TCO calculation over 3 years

The comparison “subscription price vs. server price” falls short. A Total-Cost-of-Ownership calculation over three years often shows a different picture.

Example calculation: Email marketing tool (5,000 contacts)

Cost factorSaaS solution (subscription)Self-hosting (e.g., Listmonk on VPS)
Monthly license/serverapprox. €50approx. €10 (VPS)
Setup & configuration€0 (ready to go)approx. €200 (one-off, external)
Maintenance & updates€0 (included)approx. €50/year (1–2 h work, estimate)
Costs over 3 yearsapprox. €1,800approx. €610

Honest assessment: The maintenance hours are an estimate, not a study figure – they vary strongly depending on the system. And they are the actual lever: Whoever does not have their own technical time must buy it. For more complex systems (CRM, ERP) or with strong growth – exactly the cases where SaaS prices escalate – the difference is typically more pronounced. Conversely: for a single niche tool without sensitive data, the subscription can be the more economically sensible choice.

Lock-in is now a regulatory issue

That vendor lock-in is not a theoretical problem is shown by the legislator: The EU Data Act (Regulation (EU) 2023/2854, applicable from September 2025) requires cloud providers, among other things, to facilitate switching and to gradually reduce switching fees (deadline details to verify in review). If moving out of a cloud has to be regulated by law, the lock-in was real beforehand. For decisions today this means: exportability and open formats are not a footnote, but a core criterion.

When which model makes sense

In practice, a hybrid strategy has proven useful. Not every software has to be self-hosted.

Typical use cases for SaaS (rent):

  • Non-differentiating processes: Accounting, niche tools, simple collaboration.
  • Very specific requirements where own development would exceed the scope.
  • Organizations without any technical resource for maintenance and security.

Typical use cases for self-hosting (own):

  • Your own CMS: Websites on WordPress or Astro are among the most important digital assets and should sensibly run on own infrastructure.
  • Tracking & Analytics: Tools like Matomo are often self-hosted to preserve data sovereignty.
  • Customer databases & CRM: When customer data is the most valuable asset, it doesn’t like to lie in a black box.
  • Communication: Email servers (e.g., mailcow) or chat systems (e.g., Matrix/Element) are proven self-hosting candidates.

The middle way: Managed self-hosting

For many SMEs and startups, the balancing act between “administer everything yourself” and “rent everything” is too large. Here the most sensible solution often emerges: Managed self-hosting.

The software runs on an own server, but maintenance, monitoring and security updates are outsourced to a specialized freelancer or small agency. The company retains data sovereignty and avoids scaling subscription fees; technical stability lies with the professional. This is often the sweet spot for organizations that are growing and want to regain digital sovereignty without becoming system administrators themselves.

Orientation checklist for decision-making

  • Current SaaS subscriptions listed and annual costs summed (make sprawl visible)
  • Checked whether data exports in open formats (CSV, JSON, SQL) are possible
  • Growth scenario played through: How do subscription costs develop with 2× or 10× usage?
  • Evaluated which tools belong to the core business (rather own) and which are aids (rather rent)
  • Checked whether internal resources or a freelancer for maintenance are available
  • Data protection requirements checked: Must certain data lie on own infrastructure?
  • TCO calculated over 3 years – including own time or external maintenance

The decision between self-hosting and SaaS is rarely black or white. It is a trade-off between convenience and control, between short-term relief and long-term cost structure. The market data clearly shows one thing: The rent scales with success – the ownership scales with planning.

When infrastructure becomes a bottleneck

When your own website is slow, tracking data is unreliable or dependencies on expensive SaaS tools limit the scope, a technical reset is often sensible.

A Website Tracking Check or a technical SEO analysis shows where infrastructure decisions have direct impacts on visibility and performance. For building or rebuilding own web infrastructure, web development is the right entry point. How technical investments are composed is shown in the open calculation.

Sources

  1. Gartner: Forecast Public Cloud End-User Spending, 2024 (≈ $679 bn, ≈ +20 % YoY).
  2. Flexera: State of the Cloud Report (self-assessment waste share, annually).
  3. Zylo et al.: SaaS management reports on app counts and Shadow IT (“SaaS Sprawl”).
  4. W3Techs: CMS and technology market shares (WordPress > 40 % of all websites).
  5. OpenLogic / Linux Foundation: State of Open Source Report (> 90 % open-source usage).
  6. EU Data Act, Regulation (EU) 2023/2854: Switching rights and reduction of switching fees.
  7. Eurostat / Bitkom Cloud Monitor: Cloud usage and data protection concerns in EU/DE.
  8. Public price lists of large cloud providers (egress/outbound transfer prices).
  9. Own infrastructure: mailcow (email), Astro/WordPress (web) on own VPS, Lighthouse 90+ (see Tech Stack).

Note: Benchmark and market values are orientation values from the mentioned reports, no guarantees. Individual values (exact percentages, deadlines, prices) are verified against primary sources in the Layer-2 review. This article does not replace individual IT strategy consulting.

Next step

Questions the article does not answer?

In the free intro call (15 min) we look together at what your project really needs – honest, no obligation, no sales pressure.

Free intro call To the services