Regulation (EU) 2024/1689 · OJ L of 12.07.2024 · in force Full enforcement of high-risk obligations: 2 August 2026
Compliance signal detection · Reg (EU) 2024/1689

EU AI Act compliance signals, detected and documented.

AICVS scans your source code for AI-related compliance signals, maps each finding to a specific article of the AI Act, and produces SHA-256-sealed evidence artefacts that support — and are designed to slot into — the technical documentation your compliance officer is already preparing.

It's a tool, not a substitute for a compliance officer. Read what we do and don't do below.

Coverage
EU AI Act ISO 42001 ISO 27001 (mapping) SOC 2 (mapping) EU data residency
aicvs · platform.live
EU-WEST · 47ms
Time to full enforcement
95 days
2 August 2026 · 00:00 CET (Reg 2024/1689 Art. 113)
Languages
19
Python · TS · Go · Rust · Java + 14
Detection layers
6
regex · AST · stat · semantic · SBOM · secrets
Articles mapped
47
Title III · IV · IX
Detection rules
116+
with per-rule false-positive rates
Maps to Art.5 Art.6 Art.10 Art.11 Art.13 Art.15 Art.50 Art.51–56 Art.72 Art.73

Built for the gap between Semgrep and OneTrust.

If you're a 10-to-200-person EU company building software that uses AI, the existing market gives you two options. Free generic SAST tools that don't understand the AI Act. Or six-figure GRC platforms aimed at multinationals.

AICVS sits between them. One thing, done well — code-level signal detection mapped to specific articles of Regulation (EU) 2024/1689, with cryptographic evidence chains that your compliance officer or external auditor can use as input to the technical file.

Built and operated in Limerick, Ireland — same time zone, same regulatory regime, same currency.

What you get
  • Source code scanned in 19 languages with 116+ detection rules across six analysis layers
  • Each finding mapped to a specific article of Reg (EU) 2024/1689, with the relevant paragraph cited
  • Per-rule false-positive rates displayed alongside every finding so you can prioritise honestly
  • Context-aware severity — declare your system's intended purpose and findings are weighted accordingly
  • SHA-256 evidence chain + RFC 3161 trusted timestamp for tamper-evident audit trails
  • Code never persisted: read into memory, analysed, discarded
  • EU data residency: Supabase EU-West-1 + Render Frankfurt, no transfer outside the EU
The deadline

2 August 2026. What that actually means.

From this date, Title III obligations for high-risk AI systems become enforceable. Market surveillance authorities can request your technical documentation. The penalty structure in Article 99 is tiered, and proportionality applies — but documentation gaps are visible to auditors regardless of company size.

High-risk obligations enforceable
2 Aug 2026

Title III becomes operational

Risk management (Art.9), data governance (Art.10), technical documentation (Art.11), transparency (Art.13), human oversight (Art.14), and accuracy/robustness (Art.15) all apply to high-risk systems on the EU market.

Article 113 · entry into application
Three-tier penalty structure
€7.5M – €35M

Caps under Art. 99

Tier 1 (Art. 5 prohibited practices): up to €35M or 7% turnover. Tier 2 (most provider obligations): up to €15M or 3%. Tier 3 (incorrect information to authorities): up to €7.5M or 1%. SMEs receive proportionality consideration under Art. 99(6).

Article 99 · penalties
Documentation matters most
Annex IV

What auditors will ask for

The technical file under Art. 11 + Annex IV is what market surveillance reviews. Many smaller deployers underestimate this until they're asked. AICVS produces evidence artefacts that are designed to feed into Annex IV documentation, but a qualified human still has to compile the file.

Article 11 · Annex IV
How it works

From source file to article-mapped evidence in under three seconds.

Six layers of detection. Cryptographic sealing. Article-level mapping. Plain-English caveat for every finding. All in EU infrastructure.

01 · UPLOAD

Source file in

Drop a file or hit the API from CI. You can attach system context — intended purpose, Annex III category — to weight findings appropriately.

02 · DETECT

Six-layer scan

Regex → AST → stylometry → semantic → SBOM → secrets. 116+ rules across 19 languages. Each rule has a measured false-positive rate.

03 · MAP

To EU AI Act articles

Every finding cites a specific article and paragraph of Reg (EU) 2024/1689. Mapped to your role: Provider · Deployer · Importer · Distributor.

04 · SEAL

Evidence chain

SHA-256 hash chain · RFC 3161 timestamp · evidence bundle for Annex IV. Verifiable at /verify/{id}.

ai_credit_model.py Annex III §5 · high-risk
scan-a3f9bc12 ● COMPLETE
22
/ 100
REVIEW REQUIRED
142 LOC · SHA: 8e2a1c…
7 findings · 4 articles
CRITICAL
Explicit AI authorship declaration. File header indicates AI generation — direct provenance signal under Art.50 transparency obligations.
AI-001 · line 1 · Generated by Copilot FPR 3%
Art.50
CRITICAL
Dynamic code execution detected. exec() on untrusted template input (CWE-95). Real cybersecurity issue under Art.15 regardless of AI context.
AST-001 · line 89 · exec(template_code) FPR 5%
Art.15
HIGH
OpenAI integration in user-facing path. GPAI usage in a credit-decision pipeline; Art.50(1) downstream notification likely required.
AI-002 · line 34 · openai.ChatCompletion.create() FPR 12% · context: high-risk
Art.50
MEDIUM
Dead model imports. torch and torch.nn imported but never referenced — possible scaffolding artefact, fails Art.10 data governance trace.
AST-005 · lines 4–5 FPR 15%
Art.10
MEDIUM
Low identifier-naming variance. Shannon entropy below human-baseline threshold — statistical signal of AI generation. Not a violation; relevant to Art.13 documentation if AI assistance was used.
STAT-002 · σ²=4.2 FPR 20%
Art.13
LOW
Template docstrings detected. 3 functions contain placeholder text — common in early-stage development, but worth filling in before Art.11 documentation is finalised.
AST-007 · lines 22, 56, 91 FPR 40%
Art.11
Evidence ▸ SHA-256: 8e2a1c4f7b3d…b9e2 Timestamp ▸ RFC 3161 · 29 Apr 2026 14:08 UTC Verify ▸ aicvs.io/verify/scan-a3f9bc12
Honest scope

What AICVS does. What it does not do.

Most compliance tools stop here. We start here, because pretending a scanner can replace a compliance officer is how products end up in cease-and-desist letters.

What AICVS does

  • Detects compliance signals in source code — AI authorship, GPAI integrations, ML library use, dynamic code execution, dependency hygiene, statistical patterns associated with AI generation.
  • Maps each finding to specific articles and paragraphs of Regulation (EU) 2024/1689 with verbatim citations.
  • Produces evidence artefacts — scan reports, SHA-256 hash chains, RFC 3161 timestamps, structured PDFs that compliance officers and auditors can use as input.
  • Reports per-rule false-positive rates calibrated against internal review samples and refined by user feedback.
  • Adjusts severity by context — when you declare your system's Annex III category and intended purpose, findings are weighted accordingly.
  • Maintains a tamper-evident audit trail for every scan, with public verification at /verify/{id}.

What AICVS does not do

  • Does not certify compliance. Conformity assessment under Art. 43 is a formal process involving notified bodies for some categories. AICVS produces inputs; it does not issue conformity certificates.
  • Does not produce a complete Annex IV technical file. The technical file requires risk management documentation, data governance evidence, validation records, post-market monitoring plans — much of which lives outside the codebase. AICVS contributes the source-code-related evidence.
  • Does not replace your compliance officer or external auditor. A qualified human is still required to review findings against intended purpose, decide remediation priority, and sign off on the technical file.
  • Does not provide legal advice. Regulatory interpretation belongs to your solicitor or DPO.
  • Does not classify your system's risk tier for you. Annex III categorisation is a legal determination based on intended purpose and deployment context. AICVS asks you for it; it cannot decide it.
  • Does not detect every form of AI involvement. Detection signals are probabilistic; sophisticated AI-assisted development can be hard to detect. False negatives are possible.
Bottom line: AICVS is a compliance-readiness tool that produces evidence inputs. The compliance work itself — risk classification, conformity assessment, documentation compilation, regulator engagement — is human work. Anyone who tells you otherwise is selling you a different product.
Framework coverage

EU AI Act primary. ISO and SOC 2 as cross-mapped overlays.

AICVS rules map first to the EU AI Act. Where applicable, the same rule emits cross-references to ISO 42001, ISO 27001, and SOC 2 controls — useful for organisations preparing parallel evidence packs.

PRIMARY FULL
EU AI Act

Regulation (EU) 2024/1689. Provider, Deployer, Importer, and Distributor obligations. 47 articles mapped across Title III, IV, IX.

Art.5Art.6Art.10Art.11Art.13Art.15Art.50Art.72/73
AI MANAGEMENT FULL
ISO 42001

First international AI management system standard. AICVS findings cross-map to A.6.1 (assessment), A.6.2 (treatment), A.8.2 (development).

A.6.1A.6.2A.7.4A.8.2
SECURITY CROSS-MAP
ISO 27001

Cybersecurity findings under Art. 15 cross-mapped to A.5.7, A.8.25, A.8.28. Not a substitute for a full ISO 27001 audit.

A.5.7A.8.8A.8.25A.8.28
SOC AUDITS CROSS-MAP
SOC 2 Type II

CC6 (logical access), CC7 (operations), CC8 (change management) referenced where applicable. Useful for US-facing buyers; not an audit substitute.

CC6.1CC7.1CC7.2CC8.1
Capability Generic SAST
Semgrep, CodeQL
GRC Platform
OneTrust, Drata
AI text detector
GPTZero, Copyleaks
AICVS
Analyses source code ✗ Text only ✓ 19 languages
EU AI Act article-level mapping Partial ✓ 47 articles
Per-rule false-positive rates ✓ Calibrated
SHA-256 evidence chain + RFC 3161
Source code never persisted Stored Stored ✓ Memory only
EU data residency Varies US default US default ✓ EU-only
Entry price (monthly) Free / $299 €5,000+ €8 €0 → €199

Built in Ireland. Operated in Ireland. Audited in Ireland.

AICVS is a product of Rivoryn Limited, a private company registered in Limerick. We chose Ireland deliberately: the Data Protection Commission supervises our data handling, our infrastructure runs entirely on EU soil, and our regulatory home is the same one that produces the supervisory authorities you'll be answering to.

We are early-stage and we say so plainly. The platform is in active development. Our focus is on making the underlying detection demonstrably accurate, the article mappings demonstrably correct, and the evidence chain demonstrably tamper-evident. We will trade a quieter launch for a defensible product every time.

If you'd like to talk to us before subscribing, write to hello@aicvs.io. We answer.

Registered
Limerick, IE
Rivoryn Limited
Compute
Frankfurt
Render · EU region
Data
EU-West-1
Supabase · AWS Dublin
Code retention
0 sec
Memory-only analysis
Patent status
Filed
IPOI · application pending
Audit trail
7 yrs
SHA-256 + RFC 3161 retained

Run a scan. Read the report. Decide for yourself.

Five free scans a month, no card required. The first scan tells you more than a hundred-page sales deck. If it's useful, upgrade. If not, you've cost us nothing.

5 free scans/month · upgrade only when needed · cancel anytime