Recorded on the production dashboard with a demo account and fictional demo projects. They show what ComplianceLint assesses; they are not legal advice.
How it works
One demo project, a credit-scoring API, through the whole loop: an overview, then each step in its own short video.
Overview1:37
Also on YouTube46 articles checked inside your AI coding assistant.
ComplianceLint checks a code base against 46 articles of the EU AI Act, inside the AI coding assistant you already use. One command sets up the scanner as an MCP server. Connect the project to the dashboard. Signing up is free; the wizard and Human Gates need a paid plan. The Profiling Wizard asks about your role first, then about your system. For this demo, a credit-scoring API, it concludes from the answers: high-risk, with the company as provider, and marks the obligations those answers rule out as not applicable. Your assistant reads the code and documents and answers the scanner's questions. ComplianceLint never receives your code. The sync sends the findings, their evidence notes, attestation records and scan details. The dashboard shows each finding with its evidence and the text of the law. Chapter III Sections 1 to 3 apply to Annex III high-risk systems from 2 December 2027, subject to Article 111, so findings on them are readiness findings, not statements of current legal non-compliance. What code alone cannot settle is answered by a person, in Human Gates. On the Business plan, the Compliance All-in-One Pack exports the latest scan as one zip for your legal counsel or an auditor. With non-compliant findings open, it holds a gap assessment, not a declaration of conformity. ComplianceLint is a tool, not legal advice. Eight short videos show each step.
Walkthrough
A fictional customer-support chatbot that is not high-risk, from the first scan to the Compliance Pack: the AI notice in the chat, marking of AI images and text, labels for images that look real, AI-written press releases, AI literacy, and safeguards against misuse.
Covers Article 4, Article 5, Article 6, Article 50 of the EU AI Act
Overview1:29
Also on YouTubeAn EU AI Act fix-up in eight steps
Demo Corp, a fictional company, runs a customer support chatbot built on the OpenAI API. The same system makes product images for social media and writes press releases. It went live on 1 September 2026. ComplianceLint's first scan finds gaps under Article 50 of the EU AI Act, the transparency obligations. The chatbot never says it is an AI, the image code strips the signed provenance data from every image, and nothing tells people which images were made by AI. Over the next episodes, the project is fixed step by step: the AI notice in the chat, marked and detectable content, labels on images and press releases, AI literacy, and safeguards against misuse. After each fix: a rescan, the evidence, and where code cannot settle a question, a person confirms in a Human Gate. At the end, every obligation in ComplianceLint's applicable-check scope is marked compliant except one: the marking of AI-generated text under Article 50(2) stays open for review, with the reason and a review date. The Compliance Pack exports the record. That is ComplianceLint's assessment, not a legal opinion. It covers the EU AI Act obligations the tool checks, not other laws such as data protection.
Walkthrough
A fictional recruiting AI, high-risk under Annex III, point 4(a), and not yet on the market: the first scan, an emotion-recognition feature removed, the Profiling Wizard and the readiness view, logs and human oversight, log retention and bias safeguards, the documents and Human Gates, and the record of what is still open.
Covers Article 5, Article 6, Article 9, Article 10, Article 12, Article 13, Article 14, Annex III of the EU AI Act
Overview1:13
Also on YouTubePreparing for the EU AI Act in seven steps
Fictaro GmbH is a fictional company. Its product, Fictaro Shortlist, ranks job applications and helps recruiters decide whom to invite. It is still in development and planned for launch in March 2028. An AI system that filters job applications and evaluates candidates is listed as high-risk in Annex III, point 4(a), of the EU AI Act. The amended AI Act applies its Annex III high-risk requirements from 2 December 2027; because Fictaro Shortlist is planned for its first market launch in March 2028, it cannot rely on the transition for systems already on the market. This series follows the team as it prepares, with ComplianceLint in the AI coding assistant and on the dashboard: a feature that has to go, human oversight and logs, bias, the documents, and the record of what is still open. The findings are ComplianceLint's preliminary assessment, not a conformity assessment or a certification. The series ends with a plan, not with a declaration of conformity.
Walkthrough
A fictional private employer prepares to use a high-risk recruiting AI (Annex III, point 4(a)) before first use: the first scan, when a deployer can become the provider, the deployer role and why the Article 27 fundamental rights impact assessment is not required for this employer, human oversight, input data and logs, telling candidates and workers, and the record of what is still open.
Covers Article 4, Article 25, Article 26, Article 27, Article 86, Annex III of the EU AI Act
Overview1:11
Also on YouTubeUsing a high-risk recruiting AI as a deployer
Many companies that meet the EU AI Act in recruiting will not build the system. They buy it and use it. This series follows Example Logistics GmbH, a fictional employer, as it prepares to use Fictaro Shortlist, the fictional recruiting system of the previous series. A scan of the employer's own integration code finds a high-risk recruitment use and problems that are the employer's to fix: rejections with no person involved, data the vendor says not to send, logs set to be deleted after 30 days, and a product name and a second purpose that could make the employer a provider. The Profiling Wizard sets the role: a deployer of a high-risk system and, as a private employer that does not provide public services, outside the fundamental rights impact assessment of Article 27. The episodes then fix the code and list what is open before first use. It ends with a documented plan, not a statement of compliance. ComplianceLint's results are a preliminary assessment, not legal advice.