Bare Metal
Four tiers on Intel Xeon and AMD EPYC, plus a GPU tier on the Nvidia RTX PRO 6000 Blackwell Server Edition. One tenant per machine, no hypervisor in the way. We rack it, you run it, and any tier can be ordered managed instead.
Reply within 24 h
No commitment
An engineer reviews it
The most demanding brands in Europe run on us.
Where it sits
The same network as our cloud, sometimes the same racks. At whichever site you choose, physical servers, cloud instances and your own hardware sit behind the same edge and reach each other without going out to the internet.
Topology: the public internet and your offices enter the DIVERSITY network edge, which connects to bare metal servers, cloud instances and colocation on one internal network, and to the public clouds over direct peering.
Public internet
Your end users
Head office
Branches and sites
Your own datacenter
Public clouds
AWS, Azure, GCP, Oracle and Cloudflare
DIVERSITY network
Network edge
Madrid, Amsterdam, Munich or Helsinki
Bare Metal servers
One tenant, the whole machine
Cloud instances
VPS, VDS, MEM and MNG on KVM
Colocation
Your hardware, our racks, this network
Public HTTPS
DDoS mitigated at the edge
Private Link
Direct peering
At European exchange points
Same site, one network
No public hop between them
Three ways to connect it
- Our router over the connectivity you already have
- Our fibre and our router, both
- Your own tunnel, over WireGuard, IPsec, or GRE inside IPsec
Public internet
Your end users reach your servers directly, with DDoS mitigation acting at the edge.
Private Link
Offices, branches and your own datacenter. Our router over your connectivity, our fibre and router, or your own tunnel.
Direct peering
AWS, Azure, GCP, Oracle and Cloudflare, at European exchange points.
One network inside
Bare metal servers, cloud instances and colocated hardware behind the same edge, in Madrid, Amsterdam, Munich or Helsinki.
Five tiers, no configurator
We publish the tiers and everything that is true of every server. Configurations are fixed per tier: tell an engineer what the workload does and you get the tier, the configuration and the price back in writing, normally in under 24 hours. Publishing a parts list would make this a configurator, and the fleet rotates fast enough to make one stale anyway.
Tiers
Entry
Intel Xeon E5 and Xeon Scalable, one or two sockets
Up to 4 TB RAM, 10 TB traffic
Standard
AMD EPYC 4000, single socket
Up to 192 GB RAM, 10 TB traffic
Performance+
AMD EPYC 4000 and 9000, single socket
Up to 3 TB RAM, 20 TB traffic
High end
AMD EPYC 9000, single socket
Up to 3 TB RAM, unlimited traffic
GPU
Nvidia RTX PRO 6000 Blackwell Server Edition
Unlimited traffic
On every server
SSD or NVMe
1G or 10G port
IPv4 and IPv6
Remote IPMI and KVM
Managed or unmanaged, on any tier
How it is run
Unmanaged
- We rack the server and hand over access
- The OS, the RAID and everything above them are yours
- Software RAID; a hardware controller is a custom build
- No backup product on an unmanaged server
Managed
- An option on every tier, GPU included
- OS patching, monitoring and backup
- Scope agreed at purchase, not assumed
- Not a separate tier: the hardware is the same
Storage and network
Storage
- SSD or NVMe on every server
- AMD: up to 369 TB, either kind
- Intel: up to 77 TB SSD, 307 TB NVMe
- Software RAID; a hardware controller is a custom build
Addressing
- IPv4 and IPv6 on every server
- A single IPv6 /128 by default
- Rent more: an IPv6 /56, or IPv4 from a /29 to a /24
Private Link
- Our router over the connectivity you already have
- Our fibre and our router, both
- A tunnel over your own connection, with WireGuard, IPsec, or GRE inside IPsec
Direct peering
- AWS
- Azure
- GCP
- Oracle
- Cloudflare
Repairs and terms
Hardware replacement
- Every component that can fail, with no parts billing
- We aim to have it back in service within 4 working hours
- Free on every plan, managed or unmanaged
- Weekends and out of hours need the advanced support plan, which is paid
Lead times
- In stock: 4 hours
- Built but not yet racked, or waiting on a part: 48 hours
- Sourced and assembled to order: up to 14 days
Custom builds
- Accepted managed or unmanaged
- Built from hardware we have in stock, or from parts we source
- Dell or Supermicro chassis
- Two GPUs per box is typical; larger chassis on request
Contract and end of life
- Six-month minimum term
- At the end, your data is deleted
- Disks securely erased to NIST SP 800-88 before reuse
Latency and uptime, in figures
The machine performs the way its silicon performs, and you can look that up. What is worth publishing is the network it sits on: the latency your own browser measures right now, and the availability we commit to by contract.
--ms
Your latency to our network
Measured between your browser and our servers as you read this, not taken from a brochure.
How we measure it (opens in a new tab)
99.9%
Product availability, by contract
With automatic credits if we miss it. A failed component is the repair window, not this.
One tenant on the machine, one jurisdiction over the data.
Dedicated hardware does not change the jurisdiction. If the company holding the rack answers to a US parent, so does the rack: the CLOUD Act reaches any data in the possession, custody or control of a provider under US jurisdiction, through its US parent too, wherever it physically sits. DIVERSITY is European with no US parent, so there is no US entity in our ownership chain to serve. Your server runs in Madrid, Munich, Helsinki or Amsterdam, nobody else runs on it, and you pick which site.
Data in Europe
Workloads and critical data on European infrastructure. No transit through foreign jurisdictions.
GDPR: data protection by design
Built for traceability, compliance, and control. Not a layer added afterward.
European datacenters
Madrid, Munich, Helsinki, Amsterdam. Operated by our own team.
No US parent
No exposure to extraterritorial reach like the CLOUD Act. Jurisdiction is the shield.
When to use Bare Metal
When a workload wants the whole machine: predictable cycles, the disks without a layer in between, or a licence that counts sockets.
Databases that want the disks directly
Licences billed per socket, where a single-socket Standard keeps the count down
Steady, predictable load with nothing to scale in and out
AI training and inference on the RTX PRO 6000 Blackwell tier
Audit requirements that will not accept a shared host
Your own hypervisor or Kubernetes nodes, on metal you control end to end
Hybrid estates that keep reaching AWS, Azure, GCP or Oracle over direct peering
Offices and branches that need a private path in, not a VPN concentrator
Use cases by industry
Where this product earns its place. Sectors where it replaces something more expensive, more painful, or simply riskier.
AI and research
Training and inference on the RTX PRO 6000 Blackwell tier, two cards to a box in the usual build and a larger chassis when you need more. The data stays in the EU, and so do the weights.
Banking and finance
Core systems on a machine no other tenant runs on, in the EU, with an infrastructure provider that is itself subject to European law, and not on the list of critical ICT providers European supervisors publish under DORA.
Healthcare and pharma
Clinical and genomic workloads under EHDS, on a machine with one tenant on it. There is no entity above us that a foreign order for the records on its disks could be served on.
SaaS and startups
The database on metal, the app tier on cloud instances, both behind the same edge. You move the pieces that outgrow a shared host without moving provider.
Industry and logistics
ERP and MES on dedicated hardware, reached from plants and warehouses over Private Link, encrypted from the site to us.
Media and post-production
Render and transcode on machines you do not share, on 10G ports with unlimited traffic, for work where bandwidth would otherwise drive the bill.
Want the right machine for your workload?
Tell us what it has to run and how hard you load it today.
You get a tier, a configuration and a price from an engineer, normally in under 24 hours.
Reply within 24 h
No commitment
An engineer on the call
Four datacenters. One standard.
Whichever site your server sits in, the same controls apply. Independently audited and carrier-neutral, with our infrastructure in them managed by our own engineers.
Our datacenters are independently audited, not self-assessed. Across the estate that means ISO 27001 for information security, ISO 9001 for process, ISO 14001 for environmental management, and SOC 2 Type 2 where we publish it; our Amsterdam capacity additionally sits in a facility audited against the internet exchange's own colocation standard. Scope and audit dates differ by site and both come with the technical dossier, because a certificate without its scope statement is decoration.
Mitigation at the network edge, before traffic reaches your systems. It engages on its own and does not wait for you to open a ticket, which matters because the first ninety seconds are the ones that decide whether an attack is an incident or a graph. Per-customer thresholds are agreed when you sign up rather than discovered during the first event.
None of our datacenters is owned by a carrier, so you never buy transit from whoever owns the building, and are never tied to them. We sit directly on the major European internet exchanges, and we peer with AWS, Azure, GCP, Oracle and Cloudflare, so hybrid traffic takes a short, known path instead of whatever a transit provider chooses that day.
High-sensitivity smoke detection that samples the air continuously rather than waiting for a ceiling sensor to trip, and gaseous suppression that puts a fire out without soaking the racks around it. Rooms are compartmented so an incident stays in the room it started in, and the walls carry a rated fire resistance rather than an assurance.
If part of your infrastructure stays on your own hardware, it can live in the same building as your cloud, up to 20 kW per rack at sites that offer it. Same network, same operations team, no hop across the public internet between the two halves of your estate, and one contract rather than two vendors blaming each other.
Every rack takes independent no-break feeds, and where the facility provides it that is three separate paths rather than the usual two, each behind its own generator. UPS and generators are start-tested on a schedule, not assumed, because the failure mode everyone actually meets is a generator that had not been run since commissioning.
Redundant cooling per room, sized to hold temperature if a unit drops out, with temperature and humidity measured continuously rather than on walk-rounds. Our Amsterdam site runs at a PUE of 1.3 on entirely renewable electricity and pipes half its waste heat into neighbouring homes and university buildings instead of venting it.
The same standard at every site.
Pick a site for latency or for jurisdiction, not for what you get. Every item listed is the floor at all four. Where one facility does more than another, the difference is written into your technical dossier rather than averaged into a number.
Key data
The numbers that matter when uptime is the contract.
sustained peak across the European network
live, per datacenter, on our status page
European infrastructure since 2015
Madrid, Munich, Helsinki, Amsterdam
Things people ask before signing
Straight answers, no upsell.
Why you, and not a commodity host?
If the only thing that matters is the lowest price per server, a commodity host will win and we will tell you so. What you get here instead is an engineer who tells you which tier fits before you order, hardware replacement on every component with no parts billing, the same Private Link and direct peering that front our cloud, and one European jurisdiction over all of it with no US parent above us. The minimum term is six months, which is short on purpose: the argument only works if leaving is easy.
How much RAM and disk does each tier have?
We publish the ceilings, not the per-tier configuration. Intel tops out at 4 TB of RAM and takes one or two sockets; AMD tops out at 3 TB with EPYC 9000 and is always single-socket. Storage reaches about 369 TB on AMD, either SSD or NVMe, and about 77 TB SSD or 307 TB NVMe on Intel. What we do not publish is what a given tier ships with today, because the fleet rotates and a parts list is what a configurator is for. Tell an engineer what the workload does and you get a tier, a configuration and a price back, in writing, before you order.
Is there hardware RAID?
Software RAID by default. We do not fit RAID cards on customer bare metal, so if you need a hardware controller it is a custom build and we source it with the rest of the machine.
How many IP addresses do I get?
Every server is dual stack from the start, IPv4 and IPv6. IPv6 ships as a single /128, and a /56 is rentable if you need to subnet. Additional IPv4 is rentable the same way, in blocks from a /29 up to a /24.
Is it on the same network as your cloud?
Yes, and sometimes in the same racks. A bare metal server, a cloud instance and your own colocated hardware sit behind the same edge in Madrid, Amsterdam, Munich or Helsinki, and reach each other without going out to the internet.
How do I reach it privately?
Over Private Link, in whichever of its three delivery modes suits what you already have. It is the same product that fronts our cloud, our telecom services and colocation, so one private path covers the whole estate rather than one per product.
Can I have a machine built to order?
Yes, managed or unmanaged. We source the parts and build it. Chassis are Dell or Supermicro. Two GPUs per box is the usual density, and a larger chassis can be ordered if you need more cards.
What do you do, and what do I do?
We rack the server, power it on and hand over access, including remote IPMI and KVM. The OS, the RAID and everything above them are yours, which is the same unmanaged model you will know from other operators. If you would rather not run that layer, any tier can be ordered managed, and then OS patching, monitoring and backup are ours.
What happens when a component fails?
You open a ticket and we replace it, free, whatever the component is. In business hours we aim to have the server back in service within 4 working hours. Weekends and out of hours are covered by the advanced support plan, which is paid. There is no parts billing at any point, on any plan.
Is anything backed up?
Not on an unmanaged server. Bare metal has no backup product of its own: backup exists inside the managed option, and its scope is agreed with you at purchase. Running unmanaged, the backup strategy is yours, the same as the OS.
What support is included, and what is not?
Support is free on every product we sell, with a 4-hour target response time on support requests. The advanced plan is paid and buys shorter targets plus weekend and out-of-hours cover. Hardware replacement is separate from both: a defective component is the product failing to work as sold rather than a support entitlement, so it is free on every plan, and the only thing the advanced plan changes is that the repair window keeps running outside business hours.
What does the 99.9% SLA actually cover?
99.9% product availability, by contract, with automatic credits if we miss it, and the same figure covers every product we tie to an SLA. What it measures is the product being available, not the hardware. There is no failover underneath a single-tenant machine, so a failed component is not an SLA event and we will not pretend to measure it: what we commit to instead is a repair target: back in service within 4 working hours, free. If a workload genuinely needs cover around the clock, that is the advanced support plan rather than the SLA.
How fast can I have one?
In stock, 4 hours. Built but not yet racked, or waiting on a part, 48 hours. Sourced and assembled to order, up to 14 days. Those are the three cases, and we tell you which one you are in before you order rather than after.
How much traffic is included, and what if I go over?
Entry and Standard include 10 TB a month, Performance+ 20 TB, and High end and GPU are unlimited. On the three metered tiers you can buy unlimited traffic as an extra, and that upgrade comes on a 10G port. If you stay on an allowance, traffic above it is billed per additional block, or blocked if you ask for that when you order. Either way it is in your contract, not a surprise line on an invoice.
What is the minimum term, and what happens at the end of it?
Six months. At the end we delete your data and securely erase the disks to NIST SP 800-88 before the machine goes back into the fleet.
Why does it matter where my provider is headquartered?
The US CLOUD Act lets American authorities compel any provider under US jurisdiction to hand over data in its possession, custody or control, wherever it is stored, without notifying you. Dedicated hardware does not change that: if the company holding the rack answers to a US parent, the order reaches the rack through the parent. DIVERSITY has no US parent: no US company owns or controls us. There is no entity above us to serve.
We already encrypt everything. Are we not covered?
Encryption protects data in transit and at rest from third parties. It does not protect against an order served on the company that holds the hardware, under its own jurisdiction. If that company holds the keys, or can be compelled to help reach the disks, encryption is not a legal shield. Jurisdiction is, and on an unmanaged server the disks are the only copy we hold.
What does sovereign infrastructure actually mean here?
That the company operating the machine is incorporated, operated and legally subject to European law. Not a subsidiary answering to a parent somewhere else. When a regulator or a government asks for your data, what decides the answer is EU law rather than a foreign one. That is not a feature we added to the product. It is the company the product runs inside.
What they say about our work
“We asked for EU data residency and got something harder to find: an engineer who already knew our setup when we picked up the phone.”
Head of infrastructure
Payments platform, Spain
1 of 5
What else we operate
Cloud instances for the parts of the estate that should not be physical, Private Link for a private path in, Colocation when the hardware is yours. Same network, same operations team.
Shall we talk?
An AI deployment, critical infrastructure, or a quote.
Write or call and you'll get an engineer, not a ticket bot.

