Tech startup · AI-native

Evidence for investors from day one.

If you build an AI product for the EU market, you are a provider — and the heaviest duties land on you before they reach your customer. Veritome is the shortest path from 'we just realised this applies' to a signed Declaration of Conformity, without a fractional compliance officer or a six-figure consultancy.

No card · EU-hosted · 5 minutes to a first classification
Veritome system record — the six-phase journey bar and the obligations of one AI system
Sound about right?

Three conversations every founder has had this year.

What we hear

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

What the product does

There is no single pack; there are the records a VC actually checks: classification record, mapped obligations, Annex IV draft, signed DoC, public verify URL. One link in the data room.

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. The Annex IV smart forms take an afternoon. Aria drafts the DoC; a person signs it. Lawyer time goes on the contracts, not the Regulation.

What we hear

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

What the product does

Build the IFU once, send a sharing token per customer. Each deployer imports it; you get a sealed audit trail of who received what.

What changes for you

The shape of compliance when you ship the AI yourself.

01

Provider-first journey

The journey assumes you are a provider. Annex IV, FRIA, DoC and CE marking surface in the right phase, in the right order.

02

A sprint, not a quarter

The six phases are sized to be done in one push. The dashboard shows which obligation is blocking the next gate.

03

Outputs investors can check

The regulator-view dossier doubles as a due-diligence artefact. The public verify URL lets a VC check the seal without an account.

04

Aria does the heavy drafting

Annex IV first drafts, DoC text, FRIA narratives — proposed, cited, and applied only when a named person approves.

05

Founding-member pricing

30% off for life during the founding programme. Fixed monthly cost, no minimums, no implementation fee.

06

Cross-organisation IFU handoff

Enterprise prospects will ask for an Art. 13 package. Build it once; share a token per customer. Sealed and integrity-checked.

In practice

Three startups, one engine.

Use case 01

A 14-person HR-tech startup with a CV-screening product — Annex III §4, high-risk provider.

  • Classification places the system in §4 in under ten minutes; Aria reasons through the §4 versus §5 split.
  • The engine materialises the full provider obligation set across the six phases.
  • Annex IV assembles from the model card, the training-data record and the risk plan.
  • The DoC is drawn up in the editor; the dossier goes into the Series A data room.
Veritome guided classification — the register wizard that walks Article 5, Annex I, Annex III and the Article 6(3) exception
Use case 02

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

  • GPAI provider duties (Art. 53) sit beside the high-risk provider set; Art. 55 appears only above the systemic-risk threshold.
  • The training-data summary and copyright policy are filed in the GPAI tab.
  • Compute and energy figures are recorded once and carried into the model documentation.
  • Downstream-developer documentation is generated in the same flow.
Veritome obligations register — engine-derived duties with owners, dates and status
Use case 03

A 9-person healthtech startup pre-launch — CE marking under the MDR and EU AI Act conformity in parallel.

  • The Annex I product route is recorded, so the notified-body procedure carries the EU AI Act conformity assessment with it.
  • The notified body's certificate reference is tracked beside the conformity assessment.
  • Annex IV is reused as the MDR technical-file annex — same evidence, two regulations.
  • The FRIA runs because the system reaches end users; deployer hospitals can import it.
Veritome Annex IV technical-file builder — sections assembled from live system data with a hash-sealed export
What you will lean on

The capabilities that get you to ship.

Straight answers

Questions founders ask

We build the AI product. Are we the provider?

If you place an AI system on the EU market or put it into service under your own name, yes — and the Article 16 provider duties land on you before they reach your customer. Article 25 also makes a deployer the provider when they put their name on a system or substantially modify it; the classification tests both.

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

There is no button by that name. What a data room wants is a classification record per system, the mapped obligations with their status, the Annex IV technical file, the Declaration of Conformity where one applies, and the dossier with a public verify URL. Veritome produces each of those from the register; one link goes in the data room.

Do we need ISO/IEC 42001 as well?

Not by law — it is voluntary. Enterprise procurement increasingly asks for it, so Veritome runs it as a programme pre-credited from your EU AI Act work, and the certificate comes from an accredited body. The pricing page says which plan carries it.

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

Placing a general-purpose model on the market brings the Article 53 documentation, copyright-policy and training-summary duties; the Article 55 systemic-risk duties apply only above that threshold. The GPAI tab records them alongside the high-risk provider set.