Skip to content

Sovereign infrastructure

Vetting AI vendors: eight questions for your shortlist

Eight questions you can put to any vendor of AI and business software. We answer seven of them for ourselves here too. The list of building blocks we use, with licences, we hand over in writing in a conversation.

In short

The checklist is a set of questions for procurement, IT leads and management. It clarifies where a system runs, who operates it, which model reads your data and what happens on a failure or an exit. It does not replace legal advice.

Updated: November 2026

Overview

The eight questions at a glance

The order is the one of the questions further down.
TopicA warning signA good answer
Location The answer is just “in the EU”. Country and data centre are named in the contract.
Operator A third party in the background goes unnamed. Operator and subcontractors are named.
Model changes The model is treated as a trade secret. The model appears in the log of every call.
Training Nobody can name the origin. Developer and licence of the model are known.
Ownership The promise rests on a single ownership structure. The contract covers acquisition and extraordinary termination.
Licences There is no list of building blocks. A written list with licences is available.
Logging You are expected simply to take the vendor's word. Model, time and result can be retrieved.
Exit A switch would need a new project. A switch is a setting with a deadline.

How to use the list

The phrase “digital sovereignty” appears on many vendor pages in 2026. A vendor can be right on one point and silent on the rest. The eight questions therefore go through the parts one by one.

Background and the five layers are explained on the sovereign infrastructure page. How data location and control come apart is covered in the article sovereignty and data residency.

Where exactly is my data, and which law applies there?

Why you ask

The location decides which law governs storage and requests from authorities. A region such as “Europe” leaves that open.

How to recognise a good answer

The vendor names the country and the data-centre operator, and says whether backups and test systems sit in the same places. It also says which parts do not run there.

How Beyonetix answers

Our servers and language models run in a hosting environment in Germany that a partner operates. Images, video and speech output partly run through declared cloud services. We do not claim a data centre of our own, and we make no blanket statement on whether individual systems use owned or rented hardware.

Who operates the infrastructure technically?

Why you ask

Whoever runs the servers has access to systems and administration tools. Behind a German vendor there can be a group or a hyperscaler that works under a different legal system.

How to recognise a good answer

You get the list of subcontractors with their task and location, and the vendor announces changes beforehand.

How Beyonetix answers

One of our partners operates the hosting environment. The language model for text, search and chat runs there. The failure path is set per company.

Which model handles my request, and would I notice a change?

Why you ask

A model change alters answers, costs and sometimes the place of processing. If it happens unannounced, you are vetting a system that is a different one tomorrow.

How to recognise a good answer

The vendor names the model per task, records changes in the log and announces larger switches.

How Beyonetix answers

For text, open models run. Many ERP modules call them through a central layer. The model used appears in the log of the calls through that layer. If the main path fails, the fallback shows up there as well.

Who trained the model, and on what?

Why you ask

Training determines which knowledge and which built-in tendencies a model brings along. It also shows in which legal area the training data sat.

How to recognise a good answer

The vendor names the developer of the model and the licence, and says openly whether it trains itself or uses a finished model.

How Beyonetix answers

We do not train base models ourselves. We select open, freely usable models and operate them.

Who owns the model, and what happens in an acquisition?

Why you ask

Sovereignty promises hold as long as their owners hold. Mergers and sales shift seat, law and priorities, often within a few months.

How to recognise a good answer

You find in the contract an extraordinary right of termination on a change of ownership and a duty to inform you in good time.

How Beyonetix answers

The open models belong to their developers. Where they run for your request and who sees the requests is our responsibility.

Under which licences do the building blocks in the background run?

Why you ask

Databases, caches and queues sometimes sit under licences that restrict commercial operation. If a maker changes its terms, everyone building on it is affected.

How to recognise a good answer

The vendor discloses the list of building blocks with licences and explains what it does when a licence changes.

How Beyonetix answers

We hand over the list of building blocks we use, with their licences, in writing in a conversation.

Can every AI call be traced later?

Why you ask

Without a log you cannot say after an incident which model saw what. Auditors, data protection officers and your customers ask exactly that.

How to recognise a good answer

For any call you can see which model ran, when and with what outcome, and you receive this data as an export.

How Beyonetix answers

Every language-model call through the central layer is logged: model, usage, response time, success or failure. The log belongs to the layer that the calls pass through anyway.

What happens if the vendor, a partner or the legal position changes?

Why you ask

At some point something changes: a cloud partner drops out, a court overturns a legal basis, the vendor is sold. Then it matters how fast you can react.

How to recognise a good answer

The vendor describes the switching path step by step and names the data formats for export and the duration.

How Beyonetix answers

Model choice sits per task in the central layer. Switching the model provider is therefore a setting. How you take your data with you if you change vendors is something we put in writing before a project starts.

Using the list in a conversation

  1. Send the vendor the eight questions in writing beforehand.
  2. Ask for the answer from someone who knows the architecture.
  3. Pay attention to questions 3 to 5, because that is where a location statement parts ways with an answer about the technology.
  4. Record open points with a deadline in the contract.
  5. Repeat the check on every major occasion.

Where to read on

Questions and answers

Questions about the checklist

Is a location in the country enough?

It answers one of the eight questions, namely which law governs storage. Whose software runs, who operates it and which model reads your data are covered by the other seven.

Who should answer the questions?

Ask for a written answer from the vendor's technical or executive management. An answer from sales alone rarely covers the architecture.

How often do I check again?

Once a year and on any occasion that changes the situation, such as an acquisition, a new cloud partner, a new model or a contract renewal.

Does the list also apply to open-source solutions?

Yes. Open licences answer question 6 well. Who operates the solution, where it runs and who sees the calls stay open, and the other questions cover those.

Put the eight questions to us

With your use case and your data. We answer in writing.