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
An 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.