Exclusive for the AI Engine Pro community
AI Act Made Simple for AI Engine Pro users
AI Engine Pro makes it easier to build and launch. AAMS helps you understand the AI Act responsibilities created by the resulting product.
Start the RRCS assessment See the current timeline
For fellow AI builders
AI Engine Pro can power a customer-facing chatbot, knowledge assistant, RAG workflow or bespoke AI service. Once that system is placed on the market, put into service or used in the EU, the organisation behind it may have obligations under the EU AI Act.
The underlying model provider’s compliance work does not automatically cover your product, intended purpose, interfaces, data flows or the way users rely on its outputs.
AI Engine Pro is created by Jordy Meow at Meow Apps.
What the AI Act changes for an AI Engine project
The relevant route depends on what the system does, who offers or uses it, and the context in which people rely on it.
- Customer-facing AI. People must be informed when they are interacting with an AI system in the situations covered by Article 50.
- RAG and tailored workflows. Connecting proprietary knowledge, changing the intended purpose or packaging a system for clients can affect your role and evidence needs.
- Business decisions. Employment, education, essential services and other sensitive contexts require closer classification before deployment.
- Teams using AI daily. Providers and deployers must take measures to support the development of AI literacy among relevant staff and operators.
Exposure is context-specific. The relevant question is not whether the product is described as a wrapper, but how it is configured, presented, used and made available.
The current AI Act implementation timeline
Regulation (EU) 2026/1744 changed the high-risk timetable. It did not pause the obligations already in application.
- February 2, 2025: First provisions applied. Definitions, prohibited practices and the original AI literacy provision entered into application.
- August 2, 2025: Governance and GPAI. Governance rules and obligations for providers of general-purpose AI models applied.
- July 27, 2026: The Digital Omnibus entered into force. The amended Article 4 requires providers and deployers to support the development of AI literacy without guaranteeing a specific level for each individual.
- August 2, 2026: Article 50 transparency. Relevant transparency obligations now apply, including notices for AI interaction and duties concerning certain synthetic content. (We are here: September 21st, 2026.)
- December 2, 2026: Additional prohibitions and transitional marking deadline. New prohibited-practice provisions apply. Certain systems placed on the market before August 2, 2026 must comply with Article 50(2).
- December 2, 2027: Annex III high-risk systems. Requirements apply to systems classified as high-risk under Article 6(2) and Annex III.
- August 2, 2028: High-risk systems in regulated products. Requirements apply to systems classified as high-risk under Article 6(1) and Annex I.
Sources: Regulation (EU) 2026/1744 and the European Commission AI Act guidance.
Do not want to follow the EU compliance path?
You might find Not in the EU (Yet) useful. It is a small, standalone WordPress plugin that blocks public site and REST requests from EU IP addresses when a trusted CDN or host supplies the visitor’s country.
Its settings page includes three editable visitor notices, a formal legal notice, a message critical of excessive bureaucracy, and a “coming soon” notice for EU users, plus an optional logo, a fully custom HTML card, and an opaque background style.
Download “Not in the EU (Yet)”
It is a technical access-control measure, not legal advice or a conclusion about your obligations. It requires country geolocation headers from your CDN or host.
Use RRCS to turn uncertainty into a compliance path
RRCS gives you a structured first reading of the facts that shape your AI Act position and the next action to prioritise.
- Risk. Identify the use case, people affected and legal risk signals.
- Role. Clarify whether you may act as provider, deployer, importer or distributor.
- Readiness. See evidence gaps and priorities for a defensible next step.
For teams that need implementation support, AAMS provides lawyer-led guidance, document review and a tailored action plan. Where accurate for the use case, part of that implementation, such as transparency notices or governance documentation, can itself be built using AI Engine Pro.