Three conversations every founder has had this year.
“The lead VC asked for an AI Act readiness pack. I genuinely didn't know what that meant.”
“We launch in six weeks and the team's six engineers — none of us are lawyers.”
“Our enterprise prospect won't sign without an Art. 13 IFU package.”
The shape of compliance when you ship the AI yourself.
Provider-first journey
The default journey assumes you're a provider. Annex IV, FRIA, DoC, CE marking — all surface in the right phase, in the right order.
Fast-track in 30 days
Six-phase journey designed to be doable in a sprint. The dashboard shows exactly which obligation is blocking the next phase gate.
Investor-ready outputs
The regulator-view dossier doubles as a due-diligence artefact. Public verify URL means VCs check the seal without account access.
Aria does the heavy drafting
Aria writes Annex IV first drafts, DoC text, FRIA narratives. You edit. The first draft is the time-eater on every other tool.
Founding-member pricing
30% off for life during the founding programme. Fixed monthly cost, no minimums, no implementation fee.
Cross-org IFU handoff
Your enterprise prospects will ask for an Art. 13 package. Build it once; share a token per customer. Sealed, integrity-checked, ready for your records.
Three startups, one engine.
A 14-person HR-tech startup with a CV-screening product — Annex III §4, high-risk provider.
- Classification wizard puts the system in §4 in under 10 minutes; Aria reasons through the §4 vs §5 split.
- Engine materialises the full provider obligation set across 6 phases.
- Annex IV technical doc auto-assembles from the model card + training-data record + RiskPlan.
- DoC drawn up in the editor; CE marking unlocked on phase-4 completion.
- 30-day target hit; the dossier goes into the Series A data room.
A 22-person legal-tech startup fine-tuning an open-source LLM for contract review.
- GPAI provider obligations (Art. 53) materialise alongside the high-risk provider set; the systemic-risk duties in Art. 55 only appear if your model crosses that threshold.
- Training-data summary and copyright-compliance policy filed in the dedicated GPAI tab.
- Training-compute and energy-consumption figures recorded once in the GPAI tab and carried into the model documentation.
- Downstream-developer documentation generated in the same flow.
A 9-person healthtech startup pre-launch — CE marking under MDR + AI Act conformity in parallel.
- Annex I product route recorded, so the MDR notified-body procedure carries the AI Act conformity assessment with it.
- Notified body engaged; certificate reference tracked alongside the conformity assessment.
- Annex IV doc reused as MDR technical file annex — same evidence, two regulations.
- FRIA runs because the system reaches end-users; deployer hospitals can paste-import it.
