On-premise AI runs models on servers the organisation owns and operates. Private cloud AI runs them on dedicated capacity at a cloud provider. For regulated sectors the questions are who can reach the data, which law governs the provider and how to exit. A European-owned private cloud gives most of the control for less capital.
Summary
- Ownership decides jurisdiction. An EU region of a US cloud stays within reach of US disclosure orders. Ten of DORA's 19 critical providers have a US parent.
- Sector rules rarely demand on-premise. DORA, GDPR and NIS2 require control, exit plans and supply-chain security. An EU-owned private cloud can meet them with less work.
- Start in the cloud, buy when volume is steady. Own hardware pays off at high, steady use or when data may not leave the building.
What is private AI?
Private AI runs models in an environment the organisation controls, away from shared public AI services. VMware calls it "an architectural approach that aims to balance the business gains from AI" against privacy and compliance requirements.1
It takes two forms. On-premise: the organisation owns and runs the servers, in its own data centre or a colocation rack. Private cloud: a provider owns and runs the hardware and rents out dedicated capacity.
On-premise, colocation or private cloud: what is the difference?
Four options cover almost every European deployment.
Only the operator's ownership decides which law can reach the data.
| Option | Hardware | Operated by | Upfront cost | Add capacity | Exit |
|---|---|---|---|---|---|
| On-premise | Owned | Own staff | High | Buy servers | Keep the hardware |
| Colocation | Owned | Own staff | High | Buy servers | Move or resell hardware |
| EU-owned private cloud | Provider | Provider | None | Contract | Notice period, data export |
| US cloud, EU region | Provider | Provider | None | On demand | Notice period, data export |
Operator under EU jurisdiction only Operator with a US parent
Sources: 18 U.S.C. 2713; provider terms; accessed 28 September 2026. Colocation: the site operator may have a US parent, but the customer keeps the hardware and access. Qualitative comparison; costs are in the text.
Colocation is often overlooked. The organisation owns the servers and holds the keys. The site supplies power, cooling and connectivity, so no data centre has to be built for GPUs.
The Lindstead price index lists the European GPU providers and their ownership: Scaleway and OVHcloud in France, Hetzner, IONOS and STACKIT in Germany, Verda in Finland and Nebius in the Netherlands.
Why does the provider's jurisdiction matter?
The US CLOUD Act obliges a provider to disclose data in its "possession, custody, or control", wherever it is stored.2 The duty follows the company, not the data centre. In June 2025, under oath before a French Senate inquiry, Microsoft France's director of public and legal affairs could not guarantee that French citizens' data would never reach US authorities without French consent. It had not happened, he added.3
Transfers to the United States rest on the EU-US Data Privacy Framework. The General Court upheld it in September 2025; an appeal is pending at the Court of Justice as case C-703/25 P.4,5 Lindstead found no judgment as of September 2026: legal uncertainty, not a ban.
Most critical ICT providers to EU finance have a US parent
Ten of DORA's 19 critical providers belong to US-headquartered groups.
Ten of the 19 critical ICT providers to the EU financial sector have a US parent.
Designated critical ICT third-party providers, by headquarters of the parent group, number of providers
1 Accenture (Ireland), Capgemini and Orange (France), Deutsche Telekom and SAP (Germany). Accenture plc is incorporated and headquartered in Ireland; counted by its US origins, the split becomes 11 US and 4 EU. 2 Colt Technology Services and LSEG. US count: AWS, Bloomberg, Equinix, FIS, Google Cloud, IBM, InterXion (Digital Realty), Kyndryl, Microsoft, Oracle.
Source: European Supervisory Authorities, list of designated CTPPs, 18 November 2025; parent headquarters from company filings; accessed 28 September 2026
View data table
| Category | Series 1 | Series 2 | Series 3 |
|---|---|---|---|
| United States | 10 | Not reported | Not reported |
| EU¹ | Not reported | 5 | Not reported |
| United Kingdom² | Not reported | Not reported | 2 |
| Japan | Not reported | Not reported | 1 |
| India | Not reported | Not reported | 1 |
Series 1: US-headquartered parent. Series 2: EU-headquartered parent. Series 3: Other. Unit: number of providers
The European Commission's Cloud Sovereignty Framework of October 2025 scores cloud offers on eight sovereignty objectives, from 0, no sovereignty, to 4, full digital sovereignty.10 Any buyer can use it to test "sovereign" claims.
What do sector rules require?
No EU rule requires on-premise AI. Sector rules require control, documented risk management and a way out.
Each sector has a different reason to keep AI under control.
| Sector | Main rules | What it means for hosting |
|---|---|---|
| Financial services | DORA, GDPR | Exit strategy for critical ICT providers |
| Healthcare | GDPR Art. 9, NIS2 | Health data needs an Art. 9 exception |
| Public sector | GDPR, NIS2, cloud policy | Citizen data, procurement, sovereignty |
| Legal services | Professional secrecy, GDPR | Privileged files stay under control |
| Energy | NIS2, Cyberbeveiligingswet | Supply-chain security of providers |
| Manufacturing | Trade secrets, Data Act | Designs and know-how stay inside |
Sources: Regulation (EU) 2022/2554; Regulation (EU) 2016/679; Rijksoverheid, 7 July 2026; accessed 28 September 2026.
- Financial services. DORA has applied since 17 January 2025. It requires exit strategies for ICT services behind critical or important functions.6 On 18 November 2025 supervisors designated 19 critical ICT third-party providers, including AWS, Google Cloud and Microsoft.7
- Healthcare. Health data is a special category under GDPR Article 9, prohibited unless a listed exception applies.8 An external model adds a processor to assess, and often a transfer.
- Energy and critical infrastructure. The Dutch Cyberbeveiligingswet implements NIS2 and applies from 15 August 2026. More than 8,000 organisations get new duties, including supply-chain security.9
- Public sector and legal services. Citizen data, procurement rules and professional secrecy favour infrastructure the organisation controls.
The AI Act is the exception: its duties follow role and use case, not hosting. A credit-scoring model is high-risk from 2 December 2027 wherever it runs.14 The AI Act timeline lists every date. Lindstead maps DORA, GDPR and NIS2 obligations to each AI system first.
What does each option cost and how long does it take?
Own hardware turns operating cost into capital spend, and 2026 raised the price. The list price of an RTX PRO 6000 Blackwell on NVIDIA's US marketplace rose to $16,000, about €14,300, in August 2026.11 Hetzner rents a dedicated server with one such GPU in Germany for €1,199 a month plus a one-off €599 setup fee.12 The European GPU price index tracks rising on-demand prices.
Pan et al. (arXiv 2509.18101) find owned hardware pays back in about three months for small models, 6 to 24 months for medium ones and often more than two years for large ones. Ownership suits high, steady volumes or strict residency rules.13 The Lindstead break-even calculator shows the token volume where own GPUs beat an API.
Three more costs matter:
- Staff. On-premise and colocation need a team for GPU servers, inference software, patching and model updates. A private cloud provider runs the hardware.
- Utilisation. Owned GPUs cost the same at 10 or 90 percent load. Rented capacity follows demand.
- Time. Cloud capacity comes with the contract. Own hardware waits on supplier delivery and a ready data centre.
How to decide: five questions in order
- How sensitive is the data? Public or internal data can often use an API. Special category data, privileged files and trade secrets point to private deployment.
- Which law may reach the operator? If non-EU disclosure orders are unacceptable, only on-premise, colocation or an EU-owned cloud remain.
- How large and steady is the volume? High, predictable use favours owned hardware. Uncertain demand favours rental.
- Can the organisation run GPU infrastructure? Without a team for servers, security and model updates, a private cloud is the realistic start.
- What does exit require? Regulated entities need a tested exit plan. Open-weight models and standard inference software turn a move into a contract question, not a rebuild.
For most regulated organisations the answer is one sequence: prove the use case in an EU-owned private cloud, then move steady, sensitive workloads to owned hardware. Lindstead delivers a first production use case on-premise or in a European cloud, with the logging and access controls auditors expect.
Can on-premise and private cloud be combined?
Yes. Most mature set-ups use one of three patterns:
- Sensitive on-premise, the rest in the cloud. Client files and health data stay on owned hardware. Development, testing and burst capacity run in an EU-owned cloud.
- Private models, external APIs for public data. Public content goes to a commercial API; confidential work runs on a private model, routed per request type.
- Cloud first, hardware later. The same open-weight model and inference stack run on rented capacity until volume justifies buying servers.
Hybrid needs one policy for data classification, logging and model versions. The 2026 European briefing on where AI should run has the full picture.
Frequently asked questions
-
It can be. DORA does not ban cloud services. It requires ICT third-party risk management, specific contract terms and exit strategies for services that support critical or important functions. A private cloud contract that meets them, with a tested exit plan, fits DORA.
-
No. The CLOUD Act reaches data in a US provider's possession, custody or control, wherever it is stored. An EU region fixes location, not which law can compel the provider. Customer-held encryption keys reduce the risk; an EU-owned provider or own hardware removes it.
-
Private AI runs in an environment the organisation controls, outside shared public services. Sovereign AI adds that the infrastructure, the operator and often the model answer only to European law. Private AI at a US-owned cloud is private, not sovereign.
-
Yes. Open-weight models such as Mistral Small, gpt-oss or Gemma run on one server with one or a few GPUs; larger models need an eight-GPU node. The bank then carries security, monitoring, model updates and the model risk management supervisors expect.
-
No. AI Act duties depend on role and use case, not on where the model runs. An organisation using a model internally is usually a deployer, on-premise or in the cloud. Hosting affects GDPR, DORA, NIS2 and data access, not the AI Act classification.
Lindstead advises regulated organisations on where their AI should run and deploys a first use case on infrastructure they control. The self-hosted LLM guide covers models, hardware and a step-by-step plan. Schedule a meeting to discuss the options.
Sources
- VMware, VMware Private AI: privacy and security best practices, technical white paper, May 2024. www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vmware-private-ai-foundation-privacy-security.pdf
- 18 U.S.C. 2713, Required preservation and disclosure of communications and records (CLOUD Act), Cornell Legal Information Institute. www.law.cornell.edu/uscode/text/18/2713
- The Register, Microsoft admits it 'cannot guarantee' data sovereignty, 25 July 2025. www.theregister.com/2025/07/25/microsoft_admits_it_cannot_guarantee/
- Court of Justice appeal in Latombe v Commission, case C-703/25 P, notice in the Official Journal, 22 December 2025. eur-lex.europa.eu/eli/C/2025/6610/oj/eng
- WilmerHale, European Court of Justice to review challenge to EU-U.S. Data Privacy Framework, 1 December 2025. www.wilmerhale.com/en/insights/blogs/wilmerhale-privacy-and-cybersecurity-law/20251201-european-court-of-justice-to-review-challenge-to-eu-us-data-privacy-framework
- Regulation (EU) 2022/2554 (DORA), Articles 28 and 64. eur-lex.europa.eu/eli/reg/2022/2554/oj/eng
- European Supervisory Authorities, designation of critical ICT third-party providers under DORA, 18 November 2025. www.eiopa.europa.eu/european-supervisory-authorities-designate-critical-ict-third-party-providers-under-digital-2025-11-18_en
- Regulation (EU) 2016/679 (GDPR), Article 9. eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- Rijksoverheid, Cyberbeveiligingswet en Wet weerbaarheid kritieke entiteiten vanaf 15 augustus 2026 van kracht, 7 July 2026. www.rijksoverheid.nl/actueel/nieuws/2026/07/07/cyberbeveiligingswet-en-wet-weerbaarheid-kritieke-entiteiten-vanaf-15-augustus-2026-van-kracht
- European Commission, Cloud Sovereignty Framework, version 1.2.1, October 2025. commission.europa.eu/document/download/09579818-64a6-4dd5-9577-446ab6219113_en
- Tom's Hardware, NVIDIA RTX PRO 6000 Blackwell list price on NVIDIA's US marketplace, 12 August 2026. www.tomshardware.com/pc-components/gpus/nvidia-doubles-rtx-pro-6000-blackwells-msrp-to-a-staggering-usd16-000-96gb-card-started-pre-orders-below-usd8-000-last-year
- Hetzner, GEX131 dedicated GPU server, product page. www.hetzner.com/dedicated-rootserver/gex131/
- Pan et al. (Carnegie Mellon University and independent researchers), cost-benefit analysis of on-premise LLM deployment, arXiv 2509.18101. arxiv.org/abs/2509.18101
- Regulation (EU) 2026/1744 (Digital Omnibus on AI), Official Journal, 24 July 2026. eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:L_202601744
Method: desk research of public sources, accessed 28 September 2026. Dollar prices converted at the ECB reference rate of 2 October 2026. This guide is general information, not legal advice. Corrections: contact@lindstead.com.