Role · More than one at once

Roles belong to systems, not companies.

EU AI Act roles attach to systems: you deploy what you buy and provide what you build. One register derives each duty set separately.

No card · EU-hosted · 5 minutes to a first classification
AI systems4 in the register
SystemRole · riskStageDone
Recruitment assistantDeployerHighBuild & document5/12
Credit-scoring modelProviderHighBuild & document8/25
Meeting summariserDeployerMinimalOperate & monitor2/2
Document searchDeployerMinimalOperate & monitor2/2
One register, each system its own role
Illustrative workspace · roles, tiers and obligations are the engine's
The reality

What a mixed estate does to a spreadsheet.

What we hear

“We keep two trackers, one for what we build and one for what we buy.”

What the product does

Two trackers, two versions of the truth. One register with a role per system leaves nothing to reconcile.

What we hear

“Someone put our logo on a vendor model and told procurement, not compliance.”

What the product does

That is an Article 25(1)(a) event: the provider set moved to you. The question belongs in the intake.

What we hear

“Our team applies provider rules to bought tools because it feels safer.”

What the product does

It only costs more: an Annex IV file for a deployed system spends effort your real duties needed.

What you get

Provider and deployer roles on one register.

01

Both duty sets, kept apart

The engine decides which duties each system shows, so nobody has to remember.

02

Article 25 asked up front

Branding, modification and intended-purpose questions sit in the intake, while the answer is cheap to act on.

03

Reclassify without a rebuild

When a system changes role, its obligations regenerate. Work against duties that still apply is kept.

04

An honest portfolio view

Every system's role, tier and stage, with per-tier averages, not one flattering blended number.

In practice

Three estates that hold both roles.

Use case 01

A SaaS company shipping an AI feature and running bought tools internally.

  • Provider for the shipped feature: Annex IV, conformity, CE, Art. 49.
  • Deployer for HR's bought CV screener: oversight, logs, worker notice.
  • Art. 4 literacy covers both: it attaches to the organisation.
AI systems4 in the register
SystemRole · riskStageDone
Recruitment assistantDeployerHighBuild & document5/12
Credit-scoring modelProviderHighBuild & document8/25
Meeting summariserDeployerMinimalOperate & monitor2/2
Document searchDeployerMinimalOperate & monitor2/2
One register, each system its own role
Illustrative workspace · roles, tiers and obligations are the engine's
Use case 02

A consultancy reselling a partner's model under its own brand.

  • Art. 25(1)(a) makes them provider of the branded system.
  • Still a deployer of everything they use internally.
  • The role change recorded with its date and reasoning.
ClassificationRecruitment assistant
Prohibited practicesNo — none of thoseArt. 5
Product lawNoArt. 6(1)
Annex III area4. EmploymentArt. 6(2)
Art. 6(3) exceptionIt profiles natural personsArt. 6(3)
Your roleWe use it as supplied — a finished tool somebody else providesArt. 3(3)–(8)
VerdictHighDeployerEvery step cites its article
Illustrative record · articles are real, the system is not
Use case 03

A manufacturer importing a component model and embedding it in a product.

  • Importer duties under Art. 23 for what crosses the border.
  • Provider duties for the finished product under their own name.
  • The ten-year Art. 23(5) retention runs beside the provider file.
Obligation registerDerived by the engine
12obligations applyDeployerHigh

12 obligations apply to a deployer of a high-risk system.

Classify1
Scope & literacy2
Build & document4
Conformity assessment0
Register0
Operate & monitor5
Art. 26(1)Use system per provider's instructions for use
Art. 26(2)Assign human oversight person(s)
Art. 26(5)Monitor operation; suspend and inform where use may present a risk
Art. 25(1)Watch for the changes that make you the provider
Computed by the engine for one system · switch the role to compare
Also included

The parts a mixed estate reaches for.

Straight answers

Straight answers for a mixed estate.

Can one organisation really be a provider and a deployer at once?

Yes, and most are. EU AI Act roles attach to a system, not a company: you deploy the vendor tools you use and provide what you build or brand. Each system's obligations derive independently.

What changes when a system moves from deployer to provider?

That system's whole duty list. Branding, substantial modification or a change of intended purpose into high-risk (Art. 25(1)) moves the provider set to you, and the original provider's obligations for that system fall away.

Do we pay for both roles?

Plans follow how many AI systems you register and how many are high-risk, not which roles you hold; the pricing page sets this out in full. Both roles share one register, one audit trail and one evidence base.

How do we stop the two sets of duties from confusing people?

The obligation engine decides what applies. A deployer system never shows an Annex IV tab; each system's screens carry only its own duties.

What if we are not sure which role a system holds?

That is why the check exists. A short set of questions per system, including the ones that decide Article 25, give the role, risk class and obligations, each citing its article.