Europe
Europe is not one jurisdiction and not a cloud of ours, so a European deployment is installed in the country you choose.
What this means #
Europe is a geography, not a legal system. Treating it as one region is how organisations end up with a deployment that satisfies a diagram and fails a review. So a European deployment starts from a country: which one, which zones inside it, who operates the instance and who contracts for it.
It also starts from a different model to the United Kingdom. We operate one cloud, and it is UK-resident. In Europe, as in the United States, the Caribbean and New Zealand, the platform is installed into infrastructure you run, on-premises or fully disconnected if that is what your mandate requires. What is genuinely portable is the platform itself: the same operator reconciles it, the same interfaces are exposed, the same isolation model holds and the same audit ledger records it, wherever you place it.
What you decide #
- Country
- The first decision, and the one the rest follow from. Placement, contracting and support are all settled against it.
- Zones within it
- One zone to start, more for replication and survivable site loss, nominated explicitly rather than chosen for you.
- Cross-border scope
- Whether any copy, backup or route may leave the country, and where to if so.
- Operator
- Run by your team, or run by your team with our platform engineers alongside under an access path you define.
- Deployment pattern
- Private cloud, on-premises, edge, multi-site, hybrid, fully air-gapped or the micro server, in any country you can place hardware or capacity in.
- Commercial route
- How you buy, and from whom, differs by country. Ask and we will tell you what applies to yours.
What follows from it #
These are consequences of the placement rather than promises about it, which is the difference that matters under review.
It runs where you run it #
The accelerators, database tier, object storage and model artefacts sit in the country you chose, on infrastructure you operate, and can be geo-distributed across its data centres for latency and resilience.
Cross-border replication is a choice #
Storage replicates only to the zones you nominate. If those are all in one country, that is where the copies are; if you want a second country for continuity, you say so.
The platform does not vary #
The lakehouse, the inference plane, the app runtime, durable workflows and the software factory behave identically in every country, because they are the same declared platform.
Traffic reaches the right place #
Load-balanced DNS and edge routing take each user to a healthy site, so serving users across several countries does not require several disconnected platforms.
Where to go next #
United Kingdom
The one cloud we operate ourselves, and what it places in the UK.
Continue →On-premises
What installing the platform into infrastructure you already run actually involves.
Continue →Ask about a country
Name the country and the constraint, and we will tell you what is possible there.
Continue →