Off the hyperscaler,
with engineers who do the work.

Our focus is moving workloads off the US hyperscalers and onto our infrastructure. What keeps the plan honest is its shape: a decision for every workload, with the reason written next to it. We tell you what is straightforward, what is complex, and what is probably not worth moving, and some of what you run is better left where it is. We take no commission from AWS, Azure, Google Cloud or Oracle, and you can buy the review or the plan on its own and have someone else carry it out.

No. We review, move and look after workloads on a hyperscaler, on our infrastructure and on your own servers, and we move workloads between hyperscalers as well as off them.

Written findings, ranked by risk, with what to fix first. If you want the fixes made, our engineers can make them, or your team can.

Both. Modernising usually means both: new applications, rebuilding old ones, and the platform they run on, from Kubernetes to infrastructure as code and CI/CD.

Yes. It is one of the migrations we do: an inventory of what runs on VMware, a destination for each workload, and the move itself.

With readiness for NIS2, DORA, ISO 27001, ENS (Spain's national security framework) and GDPR: where you stand, what is missing and what to fix first. Readiness is an assessment we make, not a promise that your system conforms, and not a certificate. For DORA we also give technical input to your exit plan. Penetration testing, security monitoring and a fractional CISO belong to our SecOps service, not this one.

Remotely, wherever you are. On-site at your premises only in Madrid, Munich, Helsinki and Amsterdam, the cities where we run datacenters. They work on a hyperscaler, on our infrastructure or on your own servers. Visits for an assessment are different: for those, we travel to you.

A managed service is a product we run on our infrastructure, such as a managed database. An embedded engineer works inside your team, on your infrastructure as well as ours.

Your choice: our managed services for what can be managed, our engineers inside your team, or a handover to your own team, with runbooks and training. Once you run on our infrastructure, support on it is free, with a 4-hour target response time on support requests. New design or architecture work is consulting, like everything on this page.

Four ways: a defined project, a block of hours, a retainer, or a dedicated team, and embedded engineers come in all four. We do not publish prices.

It depends on what you run and what you want from it, so we do not publish a typical length. We scope it with you after the discovery call.

The discovery call, and it is free: 90 minutes, an engineer rather than a salesperson, and a written diagnosis inside a week. It is a conversation, not a review: the review, the plan and the work come after, if you want them. Already a customer? Same call, same form.

No, and anyone telling you otherwise is selling something. DORA does not require you to host in the EU. What it does require is that you can show you manage the risk of piling critical dependencies onto the same few providers, and that you have an exit plan you have actually tested. European supervisors now publish a list of the critical ICT providers the sector leans on hardest, and the large hyperscalers are on it. We are not. We can give technical input to your exit plan, and carry out the migration if you ever run it.

What moves to us sits in our datacenters in Madrid, Munich, Helsinki or Amsterdam. What stays on a hyperscaler stays under its terms, and talks to ours over direct peering.

For what runs with us: DIVERSITY is a European company with no parent company, US or otherwise, so there is no entity above us for an order from outside the EU to be served on. That is a structural answer rather than a policy one.