01
The Gap in the Market
There is currently no European cloud provider that can reliably serve medium and large businesses while meeting their legal and operational requirements. As someone who previously led the cloud strategy for a major European corporation, I experienced firsthand how fragmented and risky the landscape is for companies operating under European law.
02
Legal Complexity and Business Risk
Managing dozens of contracts with US and EU vendors revealed how compliance isn't built-in. You need a legal team just to stay afloat:
- GDPR, ISO 27001, and BSI Grundschutz obligations don't transfer to your provider — you carry them regardless of who runs the hardware.
- Contracts often exceed hundreds of pages.
- Frameworks like Safe Harbor and Privacy Shield have been repeatedly invalidated.
When a framework is invalidated, the legal basis for an existing transfer disappears on the date of the ruling. Contracts signed under it have to be renegotiated.
03
What You Actually Get
At Origin Cloud, we treat IaaS as the technical foundation it is — not a black box.
We offer:
- The gp1 instance series with published hourly rates
- Erasure-coded block storage on general-purpose SSD, with snapshots
- Granular IAM and stable resource identifiers (URNs) on every object
- Platform metrics for every instance, volume, and network
You get the primitives and the identifiers. What you compose from them is yours.
04
Bring Your Own Image, Kernel, or Bootloader
We don't believe in hiding information:
- Bring your own image, kernel, or bootloader
- Custom BIOS and UEFI configurations are supported
The defaults are sensible. When they don't fit, the internals are documented so you can change them.
We document the internals. If the defaults don't fit your workload, you can change them without opening a ticket.
05
Fits Your Existing Toolchain
Origin Cloud fits into your existing workflows with:
- A CLI and a GraphQL API, both covering every resource type
Platform metrics are charted in the console. Tracing, log export, and real-time state-change events are planned.
This is infrastructure that works with your ecosystem, not against it.
06
Why Build It from Scratch?
We didn't start with OpenStack. We didn't resell a white-labeled platform.
We built the cloud we wish we had:
- Our own control plane, IAM, and URN system — not licensed from a vendor
- Every layer inspectable and operable by us, not a black box we're reselling
- Built from day one toward GDPR, ISO 27001, and BSI Grundschutz controls
Why? Because what sets us apart couldn't be bought. So we built it — so you can build on it. See the services it runs today.
07
Built So Your Workload Heats Someone's Home
Cloud infrastructure is built to be hard to see into. You don't know which hardware runs your workload, what it costs in energy, or where the heat goes. Origin Cloud is built on the opposite bet: a provider you can inspect is worth more than one you can't — to the customers who have to answer for what they run.
The physical form of that bet is compute sited inside the cities it serves, with its waste heat delivered into the buildings above it.
Built so your workload heats someone's home.
The destination has a name: the Regional Data Network — regions made of zones you deploy across for availability, and small sites embedded in the neighbourhoods they serve, whose waste heat enters local heat networks instead of the sky.
None of it is operating today. No site delivers heat, and we publish no efficiency or carbon figures until a running system produces them. What exists now is one region in open beta — the destination is written down here so you can hold us to it.
This is not a sustainability pledge. Owning the plant is what will make energy and carbon per workload measurable rather than modelled — a per-workload figure your own reporting can consume, once it exists. Heat reuse is how that number gets good; the auditable number is the product.