Health

AI Regulation Agent

Whether an AI system falls under the high-risk obligations hinges on its purpose. And then there is social data protection.

Determines when an in-house AI system falls under the high-risk obligations.

Determines when an in-house AI system falls under the high-risk obligations.

Open agent

Enlarge demo

Public administration

Four processes that take up the most time today

Developed in Germany · Hosted in the EU

Developed in Germany · Hosted in the EU or on-premises

Delivered together with

Sovereign hosting in Germany, single-tenant from the first user.

Sovereign hosting in Germany, single-tenant from the first user.

Legal, tax and compliance expertise for legally sound deployment.

Legal, tax and compliance expertise for legally sound deployment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

One project, two sets of rules, three units each with their own list of questions.

The business unit submits a project with a description that only outlines the purpose in broad terms. Compliance and data protection read the same description, classify it independently and arrive at different lists of questions. Until the classification is settled, the project goes back and forth between the units several times.

1

project

The business unit submits an AI system with a description of its purpose.

2

sets of rules

One asks about the risk class, the other about the legal basis and purpose limitation for the social data.

3

rounds between the units

Compliance, data protection and IT governance pass the project around until the purpose is described precisely enough.

1

list of obligations

The result is a list that has to be drawn up from scratch for the next project.

Once the purpose is classified against the same grid and the list of obligations derived from it, review effort falls by 50%.

The 50% reduction in review effort is this agent's headline figure. Two sets of rules and three coordination rounds describe a typical path to classification; they are not a measured value.

Three steps through the process.

The agent classifies the project by its purpose and derives the obligations with references; compliance and data protection sign off the approval.

1.

1.

Record the purpose and data types

The agent takes in the business unit's submission and breaks it down into purpose, affected persons and data types. It records anything that remains unclear as a question for the business unit.

The agent takes in the business unit's submission and breaks it down into purpose, affected persons and data types. It records anything that remains unclear as a question for the business unit.

Project sheet KI-2026-017, purpose in 4 sentences, 3 data types named

2.

2.

Determine the risk class with references

The agent goes through the criteria one by one and notes for each which detail from the project supports it. Criteria without a supporting detail stay open.

The agent goes through the criteria one by one and notes for each which detail from the project supports it. Criteria without a supporting detail stay open.

Classification against 6 criteria, 2 of them open for lack of detail

3.

3.

Prepare the documentation for approval

The agent compiles the classification, the derived obligations and the open points in a paper. It goes to compliance and data protection for signature.

The agent compiles the classification, the derived obligations and the open points in a paper. It goes to compliance and data protection for signature.

einordnung_KI-2026-017.docx, 11 derived obligations, 2 open points

What the agent does not do.

It does not approve any AI system.

It does not approve any AI system.

It presents the classification and the obligations with references. Compliance and data protection sign off the approval.

It does not replace the data protection assessment.

It does not replace the data protection assessment.

It names the data types in the project and the questions that follow from them. The data protection officer is responsible for the assessment.

It classifies nothing without a described purpose.

It classifies nothing without a described purpose.

If the purpose stays vague, it records the affected criteria as open. IT governance puts the follow-up question to the business unit.

Connected systems

GRC tool

record of processing activities

document management

Operations

Deployment model

EU cloud, private cloud or on-premises

EU cloud, private cloud or on-premises

Data processing

GDPR-compliant, no model training on your data

GDPR-compliant, no model training on your data

Responsible teams

Compliance, Data Protection, IT Governance

Compliance, Data Protection, IT Governance

The questions that come up before the first meeting.

How quickly is the AI Regulation Agent ready to use?

Where is the data processed?

Where does the figure “50% less review effort” come from?

Related agents.

All agents

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English
neuland.ai

The AI management and orchestration platform from Cologne.

Developed in Cologne. Operated in the EU or in your data center.

Certifications and compliance: ISO 27001, ISO 9001, GDPR, EU AI Act, DORA, StBerG, and BRAO
WirtschaftsWoche Best of Technology 2026 seal, 2nd place in the Process Management category for neuland.ai

© 2026 neuland AI AG