Tech startup · AI-native

Evidence for investors from day one.

If you build AI for the EU market, you are its provider. Get from 'this applies' to a signed Declaration of Conformity without a consultancy.

No card · EU-hosted · 5 minutes to a first classification
System journeyCredit-scoring model
HighProvider
Classify1/1Done
Scope & literacy3/3Done
Build & document4/9In progress
Conformity assessment0/4To do
Register0/2To do
Operate & monitor0/6To do
EU AI Act journey
8of 25 done
GDPR duties on this system
2of 3 done
Conformity assessment opens when Build & document closesThe next step is always clear
Illustrative record · articles are real, the system is not
Sound about right?

Conversations most founders have had this year.

What we hear

“The lead VC asked for an EU AI Act readiness pack. I didn't know what that meant.”

What the product does

No single pack: classification, obligations, Annex IV, a signed DoC and one verify link.

What we hear

“We launch in six weeks and the team is six engineers. None of us are lawyers.”

What the product does

Classification takes an hour, Annex IV an afternoon; Aria drafts the DoC, a person signs.

What we hear

“Our enterprise prospect won't sign without an Art. 13 IFU package.”

What the product does

Build it once, send each customer a token, and keep a sealed trail of receipt.

What changes for you

EU AI Act compliance when you build the AI yourself.

01

Provider-first workflow

Annex IV, FRIA, DoC and CE marking, each in the right phase.

02

Sized for a sprint

Six phases sized for one push; the dashboard shows what blocks the next gate.

03

Outputs investors can check

A VC checks the dossier's seal without an account.

04

Founding rate

30% off for as long as you stay subscribed, if you join before our full launch, with no implementation fee.

In practice

Three startups on the same engine.

Use case 01

A 14-person HR-tech startup screening CVs: Annex III §4, high-risk provider.

  • Placed in §4 in under ten minutes; Aria weighs §4 against §5.
  • Annex IV assembled from the model card, data record and risk plan.
  • The dossier goes into the Series A data room.
ClassificationRecruitment assistant
Prohibited practicesNo — none of thoseArt. 5
Product lawNoArt. 6(1)
Annex III area4. EmploymentArt. 6(2)
Art. 6(3) exceptionIt profiles natural personsArt. 6(3)
Your roleWe use it as supplied — a finished tool somebody else providesArt. 3(3)–(8)
VerdictHighDeployerEvery step cites its article
Illustrative record · articles are real, the system is not
Use case 02

A 22-person legal-tech startup fine-tuning an open-source LLM.

  • GPAI duties (Art. 53) sit beside the high-risk provider set.
  • Training-data summary and copyright policy filed in the GPAI tab.
  • Documentation for downstream developers generated in the same flow.
Obligation registerDerived by the engine
13obligations applyDeployerHigh

13 obligations apply to a deployer of a high-risk system.

Classify1
Scope & literacy2
Build & document4
Conformity assessment0
Register1
Operate & monitor5
Art. 26(1)Use system per provider's instructions for use
Art. 26(2)Assign human oversight person(s)
Art. 26(5)Monitor operation; suspend & notify on serious risk
Art. 26(9)Use Art. 13 information for the GDPR Art. 35 DPIA
Computed by the engine for one system · switch the role to compare
Use case 03

A 9-person healthtech startup working on MDR and EU AI Act conformity together.

  • The notified body carries the EU AI Act conformity assessment.
  • Annex IV reused as the MDR technical-file annex.
  • Deployer hospitals receive the instructions for use; where Annex III applies, they run their own FRIA.
Annex IV — Technical DocumentationRecruitment assistant
§1General DescriptionArt. 11
§2System Elements & Development ProcessArt. 11
§3Training, Validation & Testing DataArt. 10
§4Testing & Validation ResultsArt. 15
§5Human Oversight MeasuresArt. 14
§6Risk Management SummaryArt. 9
§7Cybersecurity MeasuresArt. 15
§8Pre-determined Changes & Continuous LearningProvider narrative · to write
Sealedsha256sha256 fingerprint e4d4b64e5aeabf734f6512c3249ff428c83229491c30f20c63c233614049e0227 of 8 filled from the register
Illustrative file · the sections are the builder's own; §8 is always yours to write
What you will lean on

The features that get you to launch.

Straight answers

EU AI Act for SaaS and AI startups: questions founders ask

We build the AI product. Are we the provider?

Yes, if you place it on the EU market or put it into service under your own name; the Article 16 duties are yours. A deployer who rebrands or substantially modifies a system becomes one too (Article 25).

What does an investor's 'EU AI Act readiness pack' actually contain?

There is no button by that name. A data room wants a classification record per system, the mapped obligations, the Annex IV file, the DoC where one applies, and a dossier with a public verify URL.

Do we need ISO/IEC 42001 as well?

Not by law: it is voluntary, but enterprise procurement increasingly asks for it. Veritome runs it as a programme pre-credited from your EU AI Act work, included from the Govern plan; the certificate comes from an accredited body.

We fine-tune an open model. Which duties apply?

Placing a general-purpose model on the market brings the Article 53 duties: documentation, copyright policy and the training summary. The Article 55 systemic-risk duties apply only above that threshold.