All features

Know which AI you use

AI provider due diligence

Keep a documented record of who you work with on AI and what documentation each provider has given you.

What it is for

VIS-4 records the providers of your AI systems and the documentation they have given you. Each system in the inventory is linked to its provider, so you can see which provider stands behind which system and what is still to be requested.

For a deployer, reviewing the provider's documentation is, in Alethexis, an internal methodological control (IM): diligence of your own, not a provider obligation that becomes yours. If the provider offers a general-purpose AI model, filing the documentation it publishes is internal documentary diligence for you.

Each provider's score is not a legal compliance rating, but a tool to help you manage your relationship with each provider and decide which one to ask for documentation first.

How it works

One record per provider, in three blocks

Identification: name, product, website and country of origin. Nature: whether the product is or embeds a general-purpose AI model, whether that model is one considered systemic, and whether it carries CE marking. Documentation: whether there is a data processing agreement (DPA) and its date, and what you have received —instructions for use, model card or technical sheet, the provider's impact assessment, transparency report, general-purpose model documentation—.

A diligence score out of 100

The platform calculates a score from 0 to 100 from the answers in the record: it adds for the documentation and items recorded, such as the DPA, the instructions for use or a provider in the EU or the EEA, and subtracts when critical items are missing, such as processing personal data without a DPA or a general-purpose model without its documentation. The “Score breakdown” shows line by line where the figure comes from, and the colour (red, amber, green) shows whom to chase first. It is recalculated when the record is saved.

An optional qualitative assessment

Alongside the score, you can answer a 12-question questionnaire about the provider —technical documentation, where data is processed, incident reporting, configurable human oversight, model changelog…—. It is an internal due-diligence criterion: it informs, but changes neither the score nor the closing of the section. The date of the last assessment only changes when its answers change.

Every system, with its provider

From the inventory you link each system to its provider; unlinking asks for confirmation. The section can be finalised when every system has a provider linked and every score is at 40 or above; until then, the screen lists the systems with no provider and the providers below 40.

Who works on it

The Owner, the AI Officer, the DPO and Contributors record and edit providers. Only the Owner deletes a provider.

Basis

The controls in the Alethexis catalogue that this feature helps to document, with their legal basis where they have one, and their nature.

  • IMInternal methodological control
IMInternal methodological controlM1-VIS-006

GPAI provider's public documentation on file

Collect and file the documentation the GPAI model provider publishes in support of Articles 53 to 55 (model card, copyright policy, training-data summary, DPA). For the deployer this is internal documentary due diligence; it is not a substantive obligation arising from Articles 53 to 55.

Legal basis

No direct basis in law.

IMInternal methodological controlM1-VIS-005

Identification of the underlying GPAI model

For each system, identify whether it uses or embeds a general-purpose AI model (ChatGPT, Claude, Gemini, Llama, Mistral and the like) and record the provider and the model version. This enables GPAI documentary due diligence for the deployer and the assessment of downstream obligations.

Legal basis

No direct basis in law.

Data from the controls catalogue. The labels show the regulatory nature of each control; they are not a statement of compliance.

Available in

  • M1Visibility
  • M2Governance
  • M3High-Risk Ready

Modules build on each other: M2 includes everything in M1, and M3 includes M1 and M2.

FAQ

What does a high score mean?
That you have good documentation for that provider. It isn't a legal compliance rating: what falls to your organisation depends on the actual use of the system and on your advisers.
Do I need to record the large providers too?
Yes, at least those of the systems in your inventory, however large they are. Many publish their DPA and their documentation on their trust portals: record them in the provider's record.
What do I enter if the provider does not give me certain documentation?
Record what you have and note what was requested and is still pending; that is also evidence of diligence.
My provider is outside the EU. Is that a problem?
Not in itself, but the international transfer of data needs a mechanism that covers it. Record it and document that mechanism.
Do the provider's obligations become mine when I record it?
No. Recording a provider and its documentation does not transfer to your organisation the obligations the Regulation places on the provider. What you do here is keep a record of your diligence about it.

Try it with your own systems