---
title: Cloud, hybrid or on-premise. How to choose | Disruptive Lab
description: Public cloud, hybrid cloud or your own servers, compared fairly by cost over five years, data rules, the people needed, risk and the way out.
url: https://disruptivelab.dev/en/news/cloud-hybrid-on-premise
language: en
covers: 2026-02-02/2026-02-08
---

1.  [News](https://disruptivelab.dev/en/news)
2.  [Costs, contracts, ownership](https://disruptivelab.dev/en/news/costs-and-ownership)
3.  Cloud, hybrid or on-premise. How to choose

[Decision guide](https://disruptivelab.dev/en/news/decision-guides)  [Costs, contracts, ownership](https://disruptivelab.dev/en/news/costs-and-ownership)

# Cloud, hybrid or on-premise. How to choose

There is no single right place for every system, so the choice is made system by system, by load, rules, the people who run it and the cost of leaving.

- **Published:** 17 November 2026
- **Updated:** 17 November 2026
- **Reading time:** 8 min read
- **Editor:** David Lahuta

Week of 2 February 2026

## In short

There is no single right place for every system, so decide system by system. A changing load, little IT staff and a quick start favour the public cloud. A steady heavy load, strict data rules and a team that already runs servers favour your own servers. Most companies with several systems end up with a mix, a hybrid cloud. From 12 January 2027 a cloud provider may no longer charge you for switching away.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1)

## Contents

1.  [What are the three options?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#what-are-the-three-options)
2.  [How do the three options compare?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#how-do-the-three-options-compare)
3.  [What speaks for and against each option?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#what-speaks-for-and-against-each-option)
4.  [What does each option cost?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#what-does-each-option-cost)
5.  [How demanding is each option?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#how-demanding-is-each-option)
6.  [When is the public cloud the right choice?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#when-is-the-public-cloud-the-right-choice)
7.  [When is a hybrid cloud the right choice?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#when-is-a-hybrid-cloud-the-right-choice)
8.  [When are your own servers the right choice?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#when-are-your-own-servers-the-right-choice)
9.  [How do you decide, step by step?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#how-do-you-decide-step-by-step)
10.  [What should you answer before deciding?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#what-should-you-answer-before-deciding)
11.  [What do companies usually get wrong?](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#what-do-companies-usually-get-wrong)

## What are the three options?

NIST, the US standards institute, defines a public cloud as open to the public and located at the provider.[2](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-2) A private cloud serves one organisation and may sit on or off its premises, so private cloud and on-premise are not the same thing.[2](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-2)

-   **Public cloud.** Your systems run in a provider's data centres, paid by use. Rented software belongs here too.
-   **Hybrid cloud.** For NIST, two or more clouds bound together so that data and applications can move between them.[2](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-2) In everyday use, some systems in a public cloud and some on your own servers, connected.
-   **On-premise.** Your own servers, in your building or in a rented rack in someone else's data centre (colocation).

In 2025, 52.74% of EU enterprises with ten or more people paid for cloud services.[3](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-3) Of those, 85.15% used cloud e-mail, but only 30.12% ran their system for orders, stock and accounting (ERP) there.[3](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-3)

## How do the three options compare?

Comparison

Criterion

Public cloud

Hybrid cloud

Own servers

Cost over several years

Little to start, then rent that grows with use

Both kinds of cost, plus the link

Hardware up front, then power, space and people

Data and rules

With the provider, under its contract

Sensitive data at home, the rest in the cloud

In your hands, with every security duty

People needed

Someone to own access, settings and the bill

Skills for two environments

A team for updates, backups and monitoring

Speed

Quick start, capacity on demand

Quick in the cloud part

Slower, capacity means new hardware

Risk

A bill that grows unnoticed, reliance on one provider

The link, and two environments to secure

A server nobody updates, nobody on call

The way out

No switching charges from 12 January 2027, the move is still work

Each part leaves on its own terms

A migration, and hardware written off early

## What speaks for and against each option?

Each list covers cost, data, effort, speed and dependence.

Public cloud

Pros

-   Little to pay up front.
-   Buildings, power and hardware are the provider's job.
-   No hardware to buy or repair.
-   Capacity follows demand.[2](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-2)
-   The provider must help you switch.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1)

Cons

-   By one estimate, at large scale, two to three times the cost of running it yourself.[4](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-4)
-   Data sits with the provider, under the jurisdiction it must state on its website.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1)
-   Access, settings and the bill still need an owner.
-   Prices and services change on the provider's schedule.
-   One provider's own services make leaving harder.

Hybrid cloud

Pros

-   Steady load on owned machines, peaks in the cloud.[2](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-2)[4](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-4)
-   Sensitive data stays on your servers.
-   Each system runs where it is easiest.
-   New projects start in the cloud at once.
-   No single provider holds everything.

Cons

-   You pay for both, and data flowing out of a cloud used side by side may still be charged at cost.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1)
-   Data moving between the parts must be protected.
-   Two environments to secure and back up.
-   A change across both needs both ready.
-   The link is one more thing that can fail.

Own servers

Pros

-   By one estimate, at large scale, one third to one half of the cloud cost.[4](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-4)
-   You know where the data is and who can reach it.
-   Hardware can serve five years or more.[6](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-6)
-   Full capacity always there.
-   Nobody else changes the price or the terms.

Cons

-   Hardware paid up front and replaced later.
-   All security work is yours, up to tested restores.
-   Someone must update and repair, nights included.
-   More capacity means more hardware.
-   You depend on the few who know the setup.

## What does each option cost?

Costs

**Public cloud.** To start, little beyond setting it up. To run, rent that grows with use. To leave, the work of moving. From 12 January 2027 providers may not charge for switching, fees for moving data out (egress) included; until then at most their own costs.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1) Standard fees and early termination penalties are not covered, so read the contract.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1)

**Own servers.** To start, hardware and a room with power and cooling, or a rented rack. To run, power, space, replacement and above all people. To leave, a migration and hardware written off early.

**Hybrid cloud.** Both, each for its part, plus the link between them.

**What published cases show.** 37signals, a US software company, spent USD 3.2 million on cloud in 2022, while already paying about USD 60,000 a month for racks in two rented data centres.[5](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-5) It moved its applications to its own hardware in 2023, bought for about USD 700,000, and its cloud bill fell to USD 1.3 million in 2024, with file storage still to move.[6](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-6) It expects to save well over USD 10 million over five years, with the same team.[6](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-6) comma.ai, which trains driving models, estimates its own data centre cost about USD 5 million against USD 25 million or more in the cloud.[7](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-7)

Both have large, steady loads. Experts quoted by Andreessen Horowitz in 2021 put such loads outside the cloud at one third to one half of the cloud cost, for large software companies.[4](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-4) Your figure moves with how steady and large the load is and whether you already pay people who run servers.

## How demanding is each option?

Complexity

One scale, low, medium or high.

Public cloud

Hybrid cloud

Own servers

People and skills

Medium. No hardware, but access and costs need an owner

High. Two environments and the link

High. Updates, backups, monitoring, repairs

Time to a working state

Low. A standard setup starts quickly

Medium. The own part waits for hardware

Medium. Hardware comes first

What can go wrong

Medium. A wrong setting exposes data, costs creep

High. The link fails, data travels unprotected

Medium. Missed updates, a failure with nobody on call

comma.ai says a couple of engineers and technicians built and maintain its data centre.[7](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-7)

## When is the public cloud the right choice?

When the load changes with the season or growth, when IT staff is scarce, or when you must start quickly. For e-mail and office work, rented software is usually the honest answer. Andreessen Horowitz calls the cloud the obvious choice for a new project.[4](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-4) For many small companies it is the right home for most systems.

## When is a hybrid cloud the right choice?

When your systems have different needs. A steady, heavy system or one with sensitive data stays on your servers, the website and new projects run in the cloud. Andreessen Horowitz found that even the companies most determined to leave the cloud kept 10 to 30% or more of their work there.[4](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-4)

## When are your own servers the right choice?

When the load is steady and large, when a law, a regulator or a customer wants data under your direct control, and when you have people or a supplier to run servers. The published savings came at a scale many companies never reach.[4](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-4)[6](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-6)[7](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-7)

## How do you decide, step by step?

Step by step to your decision

1.  Is the load steady or changing? Changing points to the cloud, steady and large to costing own servers.
2.  Must data stay in your hands, or only in the EU? Your hands point to own servers or a hybrid, the EU alone often to a cloud region in the EU.
3.  Do you have people who run servers, and will you keep them? If not, the cloud, or own servers run by a supplier.
4.  What would five years cost each way, with hardware, power, space and people set against rent?
5.  How would you leave? For the cloud, read the switching terms and the list of data you can take, which the contract must contain.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1) For own servers, keep backups and documentation another supplier can use.
6.  The recommendation. A changing load or no IT staff, the public cloud. A steady heavy load, strict rules and an IT team, own servers. Mixed answers, a hybrid, system by system.

## What should you answer before deciding?

Before you decide

-   Which systems do we run, and how heavy and steady is each load?
-   Which data is personal, confidential or bound by a customer contract?
-   Does NIS2 apply to us, and what does it ask of our suppliers?[9](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-9)
-   Who runs our systems today, and what do the contracts say about exit?
-   How much data could we lose, and how long could each system be down?
-   What is the exit plan for each system, with backups in our hands?

## What do companies usually get wrong?

-   Moving a system to the cloud unchanged and paying more.
-   Keeping servers nobody updates.
-   Comparing a cloud bill with hardware alone, forgetting people, power and space.
-   Building on one provider's own services without an exit. Providers must say when switching would be highly complex or costly.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1)
-   One decision for all systems.

## What this means for a company in Europe

Under the Data Act, in application since 12 September 2025, cloud customers may move to another provider or to their own servers, with notice of at most two months and a transition of normally 30 days.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1)[10](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-10) Switching charges end on 12 January 2027.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1) Services built for one customer and not offered widely may still charge.[1](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-1) In November 2025 the Commission proposed further exemptions for small and mid-sized providers and custom-made services on contracts before September 2025, still a proposal at the time of writing.[11](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-11)[12](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-12) The GDPR lets personal data leave the EEA only under its transfer rules.[8](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-8) NIS2 asks companies in scope to manage their suppliers' security and to plan backups and recovery.[9](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-9)

## Country by country

NIS2 works through each country's own law, which sets the duty towards suppliers and names the authority.[9](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-9) Most of these laws repeat the directive, so a company in scope secures its supply chain and weighs each direct supplier's weaknesses and security practice.[9](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-9) Some ask for more. Czechia, Slovakia and Hungary write the security duties into the supplier contract by law,[13](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-13)[21](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-21)[16](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-16) and Croatia, Latvia and Lithuania do it through implementing rules.[14](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-14)[19](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-19)[20](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-20) On 17 November 2026 Spain, France and Ireland had not yet transposed NIS2,[22](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-22)[15](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-15)[18](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-18) and it was not yet part of the EEA Agreement for Norway and Iceland.[17](https://disruptivelab.dev/en/news/cloud-hybrid-on-premise#source-17) The page for your country gives its law, its authority and what it asks of suppliers.

## Next step

If it would help, we are glad to look at your systems with you in a meeting, where each would best run and at what cost over five years. We build custom business systems and applications for the cloud, a hybrid cloud or your own data centre, so the answer follows your systems.

[Custom business systems and applications](https://disruptivelab.dev/en/custom-business-systems)

## Sources

1.  1. [Regulation (EU) 2023/2854 (Data Act), Articles 2, 23, 25, 28 to 31, 34 and 50, Official Journal of the EU](https://eur-lex.europa.eu/eli/reg/2023/2854/oj). Read on 17 November 2026
2.  2. [NIST, Special Publication 800-145, The NIST Definition of Cloud Computing, September 2011](https://csrc.nist.gov/pubs/sp/800/145/final). Read on 17 November 2026
3.  3. [Eurostat, Cloud computing, statistics on the use by enterprises, 2025 data](https://ec.europa.eu/eurostat/statistics-explained/index.php?title=Cloud_computing_-_statistics_on_the_use_by_enterprises). Read on 17 November 2026
4.  4. [Andreessen Horowitz, Sarah Wang and Martin Casado, The Cost of Cloud, a Trillion Dollar Paradox, 27 May 2021](https://a16z.com/the-cost-of-cloud-a-trillion-dollar-paradox/). Read on 17 November 2026
5.  5. [37signals, David Heinemeier Hansson, We stand to save $7m over five years from our cloud exit, 21 February 2023](https://world.hey.com/dhh/we-stand-to-save-7m-over-five-years-from-our-cloud-exit-53996caa). Read on 17 November 2026
6.  6. [37signals, David Heinemeier Hansson, Our cloud-exit savings will now top ten million over five years, 17 October 2024](https://world.hey.com/dhh/our-cloud-exit-savings-will-now-top-ten-million-over-five-years-c7d9b5bd). Read on 17 November 2026
7.  7. [comma.ai, Harald Schäfer, Owning a $5M data center, 3 February 2026](https://blog.comma.ai/datacenter/). Read on 17 November 2026
8.  8. [Regulation (EU) 2016/679 (GDPR), Articles 44 and 45, Official Journal of the EU](https://eur-lex.europa.eu/eli/reg/2016/679/oj). Read on 17 November 2026
9.  9. [Directive (EU) 2022/2555 (NIS2), Articles 21 and 41, Official Journal of the EU](https://eur-lex.europa.eu/eli/dir/2022/2555/oj). Read on 17 November 2026
10.  10. [European Commission, Data Act explained](https://digital-strategy.ec.europa.eu/en/library/data-act-explained). Read on 17 November 2026
11.  11. [European Commission, Digital package, general questions](https://digital-strategy.ec.europa.eu/en/faqs/digital-package). Read on 17 November 2026
12.  12. [European Commission, Simpler digital rules to help EU businesses grow, 19 November 2025](https://commission.europa.eu/news-and-media/news/simpler-digital-rules-help-eu-businesses-grow-2025-11-19_en). Read on 17 November 2026
13.  13. [Zákon č. 264/2025 Sb., o kybernetické bezpečnosti, §§ 13, 14, 25 and 33, Zákony pro lidi](https://www.zakonyprolidi.cz/cs/2025-264). Read on 17 November 2026
14.  14. [Uredba o kibernetičkoj sigurnosti, Narodne novine 135/2024, Prilog II., mjera 8](https://narodne-novine.nn.hr/clanci/sluzbeni/2024_11_135_2217.html). Read on 17 November 2026
15.  15. [Assemblée nationale, dossier législatif, Résilience des infrastructures critiques et renforcement de la cybersécurité, T.A. n° 366 of 17 November 2026](https://www.assemblee-nationale.fr/dyn/17/dossiers/DLR5L17N50731). Read on 17 November 2026
16.  16. [2024\. évi LXIX. törvény Magyarország kiberbiztonságáról, időállapot 2026. 10. 01., Nemzeti Jogszabálytár, 6., 16., 23. and 82. §](https://njt.jog.gov.hu/jogszabaly/2024-69-00-00). Read on 17 November 2026
17.  17. [EFTA, EEA-Lex factsheet 32022L2555 (NIS2)](https://www.efta.int/eea-lex/32022L2555). Read on 17 November 2026
18.  18. [Houses of the Oireachtas, bills register, bills updated 1 June 2024 to 17 November 2026](https://api.oireachtas.ie/v1/legislation?limit=1000&date_start=2024-06-01&date_end=2026-11-17). Read on 17 November 2026
19.  19. [Ministru kabineta noteikumi Nr. 397, Minimālās kiberdrošības prasības, likumi.lv, points 86 to 92](https://likumi.lv/ta/id/361481). Read on 17 November 2026
20.  20. [Vyriausybės nutarimas Nr. 818 and Kibernetinio saugumo reikalavimų aprašas, suvestinė redakcija 2026-06-27, Seimas, points 33 to 39](https://e-seimasx.lrs.lt/rs/actualedition/94365031a53411e8aa33fe8f0fea665f/OfOzGDbKJx/). Read on 17 November 2026
21.  21. [Zákon č. 69/2018 Z. z. o kybernetickej bezpečnosti, consolidated version in force from 30 April 2026, Slov-Lex, §§ 4 and 17 to 20](https://www.slov-lex.sk/static/pdf/2018/69/ZZ_2018_69_20260430.pdf). Read on 17 November 2026
22.  22. [Boletín Oficial de las Cortes Generales, Congreso, Serie D núm. 610, 4 de noviembre de 2026](https://www.congreso.es/public_oficiales/L15/CONG/BOCG/D/BOCG-15-D-610.PDF). Read on 17 November 2026

## Change log

1.  17 November 2026 Published.

## Related articles

Briefing · Costs, contracts, ownership

### [When a rented service closes in ten days](https://disruptivelab.dev/en/news/service-shutdown-exit)

A scheduling service closed at under ten days' notice and said it would delete user data. What to secure before signing, and what the EU Data Act gives.

Week of 16 March 2026

Guide · European rules

### [The AI Act for companies that only use AI](https://disruptivelab.dev/en/news/ai-act-for-deployers)

A company that uses AI but builds none is a deployer under the AI Act. What applies already, what comes in December 2027 and what to keep on record.

17 November 2026

## Company details

- **Company name:** Disruptive Lab s.r.o.
- **Registered office:** Vavrečkova 5262, 760 01 Zlín
- **Company ID (IČO):** 08240647
- **VAT ID (DIČ):** CZ08240647
- **E-mail:** office@disruptivelab.dev
- **Phone:** +420 777 702 032
