Vigilens sits inside the CI/CD pipeline — where AI is actually built and changed. It closes the gap between engineering and compliance before an auditor ever gets involved, and is building toward predicting behavioural drift before it becomes an incident.
No credit card. · All evidence stays yours. · Built in Oslo 🇳🇴
The people who build AI systems and the people responsible for their behaviour operate in entirely different worlds. They speak different languages, use different tools, and meet only at audit time — when it is already too late.
Getting to a submission-ready compliance pack for a high-risk AI system takes 6 to 18 weeks. That cost is not documentation overhead. It is the cost of the gap compounding since the last audit.
A system that passed an audit six months ago may be behaving very differently today. It drifted. It retrained. It found ways around its own guardrails. A point-in-time check misses all of that.
When the engineer and the compliance professional see the same picture in real time, the gap closes. The back-and-forth stops. The audit shrinks from weeks to days.
Determines jurisdiction, entity role, and risk tier. High-risk systems mapped to full EU AI Act Annex III and Annex IV obligations. Runs once at onboarding; updates automatically when the system description changes.
EU AI Act, GDPR, ISO 42001, and ISO 27001 encoded as executable rules. Auto-assigned per classification. Every control carries an acceptance specification — the exact evidence required, cited to the article.
Pulled continuously from GitHub, GitLab, Jira, Confluence, Datadog, MLflow. Every artifact is hashed, timestamped, and immutable. Evidence polarity is enforced: a gap recorded as a gap can never pass a control.
Deterministic verdicts computed from acceptance specs and evidence. No language model decides pass or fail. Human overrides are logged and attributed. Verdicts are always computed, never generated.
Forward simulation over accumulated compliance state. The goal: predict behavioural drift before it becomes an incident. Built on Vigilens' proprietary evidence model — the same structured state that powers continuous monitoring.
Answer 6 questions to find out your classification and obligations under the EU AI Act (Regulation 2024/1689). Based on the official Future of Life Institute compliance flowchart — updated July 2025. This is the first step in the Vigilens pipeline. Once classified, you can connect your CI/CD pipeline and get continuous compliance monitoring from commit one.
Select the option that best describes your relationship to this AI system. You may qualify as more than one type — run the checker once per role. (Source: Article 3, Recital 83)
These functions are prohibited under Article 5 of the EU AI Act. Select all that apply — if any apply, immediate legal review is required.
These are the Annex III high-risk categories under Article 6(2). Select all that apply — even partial overlap is enough to trigger high-risk status.
These trigger either GPAI obligations (Article 51–55) or transparency obligations (Article 50). Select all that apply.
Certain systems are excluded from scope, and jurisdiction determines whether the Act applies at all. Select all that apply. (Source: Article 2)
We'll email you a personalised compliance summary based on your answers. Company email required — personal email addresses are not accepted.
By submitting you agree to receive your compliance summary and occasional relevant updates from Vigilens. Unsubscribe anytime.
Deadlines are no longer abstract. The EU AI Act's high-risk obligations are live — and most AI teams deploying into HR, credit, and customer decisions have months to get compliant. Here's the practical checklist your legal team won't give you.
Read articleYour code has unit tests. Your infrastructure has Terraform. But your governance still runs on Word documents and annual audits. Rules-as-Code changes that — turning regulations into executable checks that run on every release.
Read articleAI startups are losing enterprise contracts not because of the product — but because they can't produce verifiable proof that their AI is safe, auditable, and under control. The security questionnaire has become the new product demo. Here's how to win it.
Read articleA plain-language guide to understanding the EU AI Act, what Articles 5, 6 and 9 actually require, and a step-by-step checklist to assess your current compliance status.
Read articleCompliance costs of up to €400,000. Launch delays for 60% of EU startups. Here's the data on how regulation is hitting SMEs hardest — and how to automate your way through it.
Read articleProhibited practices were the first to bite. GPAI obligations followed in August 2025. High-risk AI hits 2 August 2026. Full phase-in breakdown and readiness checklist for each enforcement wave.
Read articleFour mandatory components — hazard identification, risk estimation, risk evaluation, risk mitigation — plus the continuous lifecycle obligation that runs from design to post-market monitoring.
Read articleEight sections, a continuous update obligation, and 10-year retention. What Annex IV actually requires — and how to structure your documentation so an auditor can verify it in minutes.
Read articleWho must conduct a FRIA, when it must be done, what it covers, how it differs from a GDPR DPIA, and the Article 27 notification obligation to market surveillance authorities.
Read articleMost AI SaaS companies are simultaneously providers and deployers. The obligations are different and both apply. Here is how to map your product architecture to the right compliance track.
Read articleChapter V applies to GPAI model providers. Chapter III applies to high-risk system deployers. When your GPAI model powers a high-risk application, both chapters apply simultaneously.
Read articlePR naming conventions, branch structure, CODEOWNERS, release tagging, and GitHub Actions checks that generate Article 9, 12, and 14 compliance evidence automatically on every commit.
Read articleAnnex IV page templates, Jira label conventions for tracing obligations to tickets, and how to build the Confluence-Jira-GitHub evidence chain regulators expect.
Read articleMLflow run tags for Article 9 test evidence, model registry compliance gates, Datadog Article 12 log schema, Article 72 monitor naming, and 10-year retention configuration.
Read article