Skip to main content
DIVERSITY. We make IT happen

AI on your own data, on our own GPUs.

Open-weight models, or your own, on our GPUs in Amsterdam, and engineers who build with them: assistants on your documents, agents that answer your calls. Computer vision, already delivered in four sectors. Your data never trains anything except your own models.

Free, 60 minutes

Written diagnosis in a week

An engineer on the call

Where it runs

Everything we run, on our own network.

In this example your offices and your document stores reach us over Private Link. From there we run all of it: the assistant, the index, and the model on our GPUs in Amsterdam.

A worked example: an assistant on your own documents

  1. 01

    Your documents

    Our engineers index them into a vector database: pgvector, on our managed PostgreSQL.
  2. 02

    A question

    Someone on your team asks the assistant. It looks up the passages in your documents that answer it.
  3. 03

    The model

    An open-weight model, or your own, writes the answer from those passages, on our GPUs.
  4. 04

    Run by us

    We run the model endpoint and the database. Your team gets an assistant, not another system to operate.

And the legal side: 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. How that compares

Want this on your own documents? The discovery call starts from what you have. Request it

Architecture of a private assistant. Your offices and your document stores, outside the DIVERSITY network, reach it over Private Link. Inside the network, your documents are indexed into a vector database, pgvector on our managed PostgreSQL. The private assistant looks up relevant passages there and sends the question and passages to an open-weight model or your own, running on our GPUs in Amsterdam.

Your offices

Your document stores

DIVERSITY network

Private assistant

A chat window for your staff

Vector database

pgvector, on our managed PostgreSQL

Open-weight model, or yours

On our GPUs in Amsterdam

Private Link

Our router, with
or without our fibre,
or a tunnel

Question and passages

Relevant passages

What we build

What our engineers build for you.

Our engineers build it with your team, or for it.

  • Assistants on your own documents

    The worked example above, built for your documents: a vector database and a model on our GPUs.

    • Chat and search over your documents
    • A private, ChatGPT-style assistant for your staff
    • Fine-tuning an open-weight model on your data
  • OCR and document processing

    Built by our engineers on top of the Data-Driven platform, so what the documents say lands in tables your team can query.

    • OCR on scanned documents
    • Document processing: fields and tables out of forms and files
  • Computer vision

    Models that read what a camera sees, already delivered in these four sectors.

    • Manufacturing
    • Logistics and warehousing
    • Retail
    • Safety and security
  • Voice and messaging agents

    We run the phone system and the GPUs, and host the speech-to-text and text-to-speech ourselves, on those GPUs.

    • Answering inbound calls
    • Outbound calls: reminders, confirmations, campaigns
    • Agents that reply by SMS and messaging
    • Hand-off to a person, when your phones are on our CloudPBX
    • Transcription, call summaries and contact-centre analytics
  • Forecasting and fraud detection

    The machine learning that predicts and flags, trained on your own history.

    • Forecasting, predictive maintenance and churn
    • Anomaly and fraud detection

    And the work around them: MLOps to deploy, monitor and register models, and data labelling and synthetic data.

  • Consulting

    Advice on its own, or the first step before a build.

    • Finding the use case worth building
    • EU AI Act readiness: risk classification, documentation and governance
    • Architecture for AI workloads

    Readiness is an assessment we make, not a promise that your system conforms.

Not sure what to build first?

Tell us what you have in mind, or what you already run with us. Existing customers use the same form.

Free, 60 minutes

Written diagnosis in a week

An engineer on the call

Platform

Use our GPUs directly.

Call a model we host, or run your own on the hardware. With our engineers or without them.

Call a model

The model is hosted and run by us. Your application sends a request and gets an answer.

  • Model as a service

    Shared open-weight models, usually from the Qwen, GLM and gpt-oss families, hosted by us and billed per use.
  • Dedicated inference endpoint

    An endpoint of your own, serving your model or an open-weight one we host, as we agree with you for each endpoint.

Run your own

Capacity for your own training and inference, on our hardware.

  • GPUs by the hour

    Short bursts of GPU capacity, for a batch job, an evaluation or an experiment.
  • Training clusters

    Several GPU servers networked for one customer, sized to the project.

Vector search

The index behind an assistant like the worked example above: pgvector, on our managed PostgreSQL, run by us like our other managed databases.

The hardware

Seven Nvidia GPU models, currently in Amsterdam.

  • H200
  • H100
  • L40S
  • L4
  • A10
  • V100S
  • RTX PRO 6000 Blackwell Server Edition

Our current fleet. Tell us the workload and we will say which fits. The RTX PRO 6000 Blackwell, usually two to a server, is also the GPU tier of our Bare Metal: you can rent one of those servers outright in any of our four datacenters, managed or unmanaged, on Bare Metal's six-month minimum term.

Need something the fleet does not have? We build to order: tell us what you need and we will say where it goes and how soon.

The GPU tier on Bare Metal

Just need GPUs? Tell us what you want to run.

Ask about GPU capacity

Data residency isn't sovereignty. Jurisdiction is.

An EU region settles where your data sits, not who the provider answers to. Three ways to run a model on sensitive data, compared.

Criterion

US AI service, EU region

Your own GPUs

DIVERSITY

Models

Their catalogue

Whatever you deploy

Open-weight, or yours

Who runs it

The provider

Your team

We do

Building on it

You, or a partner

Your team

Our engineers, or yours

Which GPUs

Theirs

Whatever you buy and rack

Seven Nvidia models

Where models run

An EU region you select

Wherever your servers are

Currently Amsterdam only

Used in training

Usually off, by their terms

Only what you train

Only your own models

Foreign legal orders

The US company can be compelled

Depends on your host

No entity above us

Procurement or compliance questions of your own? Bring them to the discovery call. Request it

Testimonials

What they say about our work

“Our case files could never go to a US AI service. Now the team asks an assistant that runs on GPUs in Amsterdam, and nothing we give it trains anyone else's model.”

Head of knowledge management

Law firm, Spain

1 of 6

  • Santander
  • BASF
  • Commerzbank
  • AXA
  • Stellantis
  • Finnair
  • Siemens Healthineers
  • Marimekko
  • E.ON
  • Meliá Hotels International
  • Nippon Sanso
  • Siemens Gamesa
  • Ilunion
  • Douglas
  • IFEMA
  • Kemira
  • ISS A/S
  • Iberia
  • Comunidad de Madrid
  • Allianz

Things people ask before signing

What we get asked, with honest answers.

Why not a US provider's EU region?

For a lot of work you could, and your data would sit in the EU. What an EU region does not change is who the provider answers to. 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, and that reaches a European subsidiary through its US parent. DIVERSITY has no US parent: no US company owns or controls us, so there is no entity above us for that order to be served on.

Are open-weight models good enough for what we need?

It depends on the task, and it is the first thing the discovery call settles. If a closed model is the better tool for what you want to do, we will say so.

Which models do you host?

Open-weight models, usually from the Qwen, GLM and gpt-oss families. We do not publish a fixed list, because the catalogue changes. Tell us the task and we will tell you which fit. On a dedicated endpoint you can also bring your own model: we agree it with you, by its licence, its size and the GPUs it needs.

What is the difference between model as a service and a dedicated endpoint?

Model as a service is shared: models we host that several customers call, billed per use. A dedicated endpoint is yours, serving your own model or an open-weight one we host, agreed with you by the model's licence, its size and the GPUs it needs.

Where are the GPUs, and which ones?

The AI services on this page run in Amsterdam, including model as a service, dedicated endpoints, GPUs by the hour and training clusters. The fleet there is currently Nvidia H200, H100, L40S, L4, A10, V100S and RTX PRO 6000 Blackwell Server Edition; tell us the workload and we will say which fits. The RTX PRO 6000 Blackwell is also the GPU tier of our Bare Metal, usually two to a server, and those servers are available in all four of our datacenters (Madrid, Munich, Helsinki and Amsterdam), on Bare Metal's six-month minimum term. If you need something the fleet does not have, we build to order and will tell you where it goes and how soon.

Do you offer a private coding assistant, or run models on our premises?

No to both. We do not offer a private coding assistant, and we do not run models on hardware at your site.

Can you build on an outside AI service if we want one?

Yes, if that is your decision. We do not recommend it: we host open-weight models on our own GPUs, and an outside service puts your data back where you came to us to avoid. We will tell you on the call what you would gain and what you would give up.

Who runs it, and who do we call when something breaks?

We run the model endpoints, the shared models and the vector database. Once you are a customer, you reach us through the customer console or at support@ondiversity.eu. Support is free on every product we sell, with a 4-hour target response time on support requests, and the paid advanced plan adds shorter targets plus weekend and out-of-hours cover.

What does the SLA cover?

99.9% uptime, by contract, with automatic credits if we miss it, on every product we tie to an SLA. It measures whether the service is up. A hardware fault on a GPU server you rent through Bare Metal is different: that is a repair rather than an SLA event, and we aim to have it back in service within four working hours.

How does a model get into production, and stay there?

That is MLOps, and it is part of what our engineers do: deploying the model, monitoring it once it runs, and keeping a registry of what was trained and what is deployed.

How is it billed?

Model as a service is billed per use. We do not publish prices for any of it; ask us.

How do we start?

The discovery call, and it is free: 60 minutes, an engineer rather than a salesperson, and a written diagnosis inside a week. Already a customer? Same call, same form: tell us what you run with us and it starts from there.

Does our data train your models?

No. Your data never trains anything except your own models. That includes the shared models: what you send them is not used to train them.

Will using you make us compliant with the EU AI Act?

No provider can promise that, and we do not. The Act puts most of its obligations on whoever provides and deploys the AI system, which is usually you. What we offer is a readiness assessment: how your use case is classified for risk, the documentation it needs, and the governance around it.

Who can compel you to hand our data over?

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.

You might also want

One of our GPUs, the RTX PRO 6000 Blackwell, is also the GPU tier of Bare Metal. Document AI is built on Data-Driven. Voice agents answer on our own telephony.

Shall we talk?

A free 60-minute call, and you leave with a written diagnosis inside a week.

Write or call and you'll get an engineer, not a ticket bot.