Putting into Service: EU AI Act Definition (Article 3(11))
Putting into service under EU AI Act Article 3(11): supply of an AI system for first use to a deployer or own use — why an in-house build still triggers duties.
"Putting into service" is a moment, not an actor. Under Article 3(11) of Regulation (EU) 2024/1689, it means the supply of an AI system for first use directly to the deployer, or for the provider's own use, in the Union for its intended purpose. It is the route that catches the system you build and run yourself — switching on the same obligations as a sale.
The EU AI Act definition (Article 3(11))
The three elements that must all be present
Three elements of Article 3(11) are load-bearing, and all must be present at once. First use is the decisive one: like placing on the market under Article 3(9), putting into service is a one-time event per system. Directly to the deployer or for own use is the distinctive part — no sale, no customer, no transaction is required; a system supplied straight to a deployer, or turned on by the organisation that built it, is put into service. For its intended purpose ties the act to a defined term, Article 3(12) — the use the provider specifies in the instructions for use (see intended purpose). And in the Union pulls a non-EU developer into scope the moment its system is first used in the EU.
An act, not an actor
The definition is not a person or a role. That distinguishes it from the provider under Article 3(3), the who that carries the duties, and from the deployer under Article 3(4). One company can be both: build a system for your own use and you are provider and deployer at once.
Why it matters: obligations trigger with no sale
The Act pairs "placing on the market" and "putting into service" deliberately: you cannot dodge the rules by never selling.
The in-house build is the trap
Under Article 16, providers of high-risk AI systems carry the full obligation stack: conformity assessment, technical documentation under Annex IV, the EU declaration of conformity, registration. Putting into service is one of the two events that attaches that stack. Build a high-risk recruitment screener for internal hiring and never sell it, and you are still its provider.
Be honest about the scope. Most general business AI — support bots, productivity tools, content generation — is not high-risk. For those, putting into service mainly engages Article 4 AI literacy and Article 50 transparency where output reaches third parties, not the full Article 43 stack. Where the high-risk duties do apply, most provider-obligation breaches sit at Article 99(4) (€15 million or 3% of total worldwide annual turnover, whichever is higher); incorrect or misleading information to authorities at Article 99(5) (€7.5 million or 1%). Article 99(6) caps SMEs and start-ups at the lower figure.
A deployer can become a provider
The roles are not fixed. Under Article 25, a deployer becomes a provider — and itself puts a system into service under its own name — if it puts its name or trademark on a high-risk system, makes a substantial modification under Article 3(23), or changes the intended purpose so a system becomes high-risk. Repurpose a vendor's tool into a high-risk use it was never built for, and you have stepped into the provider's role.
Putting into service vs placing on the market vs making available
Three Article 3 concepts get confused constantly. The table separates them.
| Term | Article | In plain words | One-time or repeatable | Typical trigger |
|---|---|---|---|---|
| Making available | 3(10) | Any supply of a system for use on the Union market in a commercial activity, paid or free | Repeatable | Every supply, including each resale |
| Placing on the market | 3(9) | The first making available of a system on the Union market | One-time | Initial market entry, typically a sale |
| Putting into service | 3(11) | Supply for first use directly to the deployer, or for own use, for its intended purpose | One-time | Direct deployment, including an in-house build |
Free of charge is part of the Article 3(10) definition, so a free release is not an exemption. Putting into service is the only one of the three that fits when there is no sale at all: a bespoke deployment to a single deployer, or a system the provider runs internally — never placed on the market, yet not exempt.
When the obligations actually bite
Putting into service is the trigger; when the high-risk duties attach depends on the staggered application dates:
- Article 5 prohibitions and Article 4 AI literacy have applied since 2 February 2025.
- GPAI model obligations (Articles 51 to 55) have applied since 2 August 2025.
- High-risk stand-alone Annex III systems (Article 6(2)): the statute reads 2 August 2026.
The Digital Omnibus, now adopted — the European Parliament passed it on 16 June 2026 and the Council on 29 June 2026 — defers the Annex III date to 2 December 2027. That date is settled; only publication in the Official Journal (expected before 2 August 2026) remains outstanding, as a formality.
How Confir helps
The hard part is rarely the definition — it is spotting that an in-house build is a putting-into-service event and tracing the duties that crystallise around it. Confir maps each system against Article 3(9), 3(10) and 3(11), flags whether a release is placing on the market or putting into service, tests whether a change of intended purpose has tipped a deployer into provider status under Article 25, and routes high-risk systems into the pre-market checklist. The synthesis engine is deterministic and rule-based — no model inference, no hallucination — so each classification traces back to the Regulation.
Frequently asked questions
What does 'putting into service' mean under the EU AI Act?
Article 3(11) of Regulation (EU) 2024/1689 defines it as the supply of an AI system for first use directly to the deployer, or for the provider's own use, in the Union for its intended purpose. It is a one-time event per system, like placing on the market. The key feature is that no open-market sale is required: build an AI system and run it internally and you have put it into service. The relevant obligations then attach all the same.
How is putting into service different from placing on the market?
Placing on the market (Article 3(9)) is the first making available of an AI system on the Union market, typically a sale. Putting into service (Article 3(11)) is supply for first use directly to a deployer or for the provider's own use. The Act pairs the two so a system entering use is covered whether or not it is sold. The clearest example is the in-house build: never placed on the market, yet put into service.
Do we owe obligations for an AI system we built only for our own internal use?
Possibly yes. Running your own AI system internally counts as putting it into service under Article 3(11), so no sale is needed to trigger duties. If the system is high-risk under Article 6 and Annex III, the provider obligations in Article 16 apply. Most internal business AI is not high-risk, though; for those the realistic duties are Article 4 AI literacy and Article 50 transparency where output reaches third parties, not the full conformity-assessment stack.
Does 'intended purpose' affect whether a system is put into service?
Yes. Article 3(11) ties putting into service to use 'for its intended purpose', and intended purpose is itself defined in Article 3(12) — the use the provider specifies in the instructions for use. If a deployer uses a system for a different purpose that is itself high-risk, Article 25 can convert that deployer into a provider, carrying the full obligation stack. So the intended purpose both qualifies the act and can shift the roles.
When do these obligations apply to a high-risk system put into service?
Article 5 prohibitions and Article 4 AI literacy have applied since 2 February 2025; GPAI obligations (Articles 51 to 55) since 2 August 2025. For stand-alone high-risk Annex III systems the statute reads 2 August 2026, deferred to 2 December 2027 under the Digital Omnibus, now adopted (European Parliament 16 June 2026, Council 29 June 2026). Only publication in the Official Journal, expected before 2 August 2026, remains outstanding, as a formality.
Related terms
- placing on the market — the first making available under Article 3(9)
- intended purpose — the element inside the Article 3(11) definition
- deployer — who receives a system put into service
- provider — who carries the obligations the act triggers
- Article 16 — provider obligations for high-risk systems
Manage your EU AI Act compliance in one place
Confir automates risk classification, technical documentation, and audit trails for any company. No consultants. No 6-month projects. 14-day free trial.
Start free trial →