Platform · Automation

The routine runs itself. The decisions stay yours.

With EU AI Act compliance automation in Veritome, reminders, evidence freshness checks, connector pulls, reports and Aria's drafts run on schedule. Nothing is marked done, verified or filed until a person says so, and every automatic step is in the audit trail.

No card · EU-hosted · 5 minutes to a first classification
Aria · Inbox3 waiting
ClassificationFrom a run
Classify Recruitment assistant as high-risk
Annex III(4)(a)Art. 6(2)
Review schedulingFrom a run
Schedule the next review of the support chatbot
Art. 50(1)
Evidence linksFrom chat
Link the published AI notice to the support chatbot
Art. 50(1)
Illustrative proposals · try them, nothing is saved
Where compliance work leaks

Compliance work rarely fails on the work itself. It fails on the follow-up.

What we hear

“The review date passed and nobody noticed until the auditor asked.”

What the product does

Every morning the obligations due soon or overdue, the reviews due and the policies four weeks from review go to their owners, once per person and event.

What we hear

“Half our evidence was a link to a document someone has since moved.”

What the product does

Linked evidence is re-checked every week. A broken link drops back to Pending, and expired evidence stops counting and reminds its owner.

What we hear

“We spend more time filling forms than deciding anything.”

What the product does

Aria prepares the tasks, risks, supplier records and drafts. A person reads the proposal in the Inbox and approves, edits or rejects it.

What runs on its own

Compliance automation that is logged and sent once.

01

Deadline reminders

Daily emails for obligations due soon and overdue, reviews due and incident alerts, to the person who owns each one.

02

Evidence that stays current

Expired evidence returns to Pending with a reminder, and linked evidence is re-checked weekly. Neither ever marks anything verified.

03

Evidence from your tools

Connect Google Drive, SharePoint / OneDrive, GitHub and Jira, pick the files and issues, and they arrive in Evidence as Pending for a person to accept.

04

Reviews that come round

Classifications older than a year and quarterly reviews are flagged, and AI-literacy records about to lapse are reported before they do.

05

A trail nobody can rewrite

Each day's audit log is hash-chained and anchored, so a changed record shows.

06

Reports and a monthly digest

Scheduled reports run on their own, and every administrator gets one digest a month for each organisation they run.

Aria, on a leash you set

Proposals by default. Auto-apply only where you allow it.

Use case 01

Each of Aria's 14 capabilities has its own row in Settings → Autonomy.

  • Propose is the default: the change waits in the Inbox.
  • Auto-apply takes effect only on minimal-risk systems, recorded as Aria's in the activity log.
  • Classification and anything on a high-risk system always need a named sign-off.
  • Organisation-wide changes and document drafts are approve-only, whatever the setting.
Aria · SettingsAutonomy
On a system classified
Minimal
ClassificationAlways needs sign-offNamed sign-off
Tasks & assignments
Waits in the Inbox
Evidence links
Waits in the Inbox
Document drafts
Waits in the Inbox
Try it: switch a row to Auto-apply, then make the system high-risk. The product’s own policy decides each outcome · nothing is saved.
Use case 02

A policy document is picked from a connected drive.

  • It arrives in Evidence as Pending, a link to the file where it already lives.
  • A person links it to the obligations it proves and accepts it.
  • Every week the link is checked; a broken one drops back to Pending.
  • A link behind a sign-in wall is recorded as not checkable, never as broken.
Evidence · filed onceExample
Record · approved
Roles, responsibilities and authorities
One owner · one review date · hash-chained on approval
ISO 42001§5 Counts
ISO 27001§5 Counts
EU AI Act14Related · not counted
NIST AI RMFGOVERN 2.1Related · not counted

The record is credited only where it has been verified against both clause sets. The other clauses are signposted, and nothing is ticked on your behalf.

What never happens automatically

Where a person is required, the product requires one.

Straight answers

EU AI Act compliance automation: your questions

What does Veritome do without anyone logged in?

It sends the reminders: obligations due soon and overdue, reviews due, and policy reviews four weeks ahead to the policy's owner. It returns expired evidence to Pending and re-checks linked evidence weekly. It anchors the audit trail each day, runs your scheduled reports and sends administrators a monthly digest. Each email goes once per person and event.

Can Veritome mark something compliant on its own?

No. No schedule, connector or Aria action marks an obligation done or evidence verified. A connector offers evidence as Pending, a broken link drops evidence back to Pending, and a person decides what counts.

What may Aria do automatically?

Each of Aria's 14 capabilities has its own setting. An administrator may let low-stakes changes on minimal-risk systems apply on their own, recorded in the activity log as Aria's. Classification, anything on a high-risk or prohibited system, and organisation-wide changes always wait for a person, and submissions to a regulator are never made.

What is coming next?

Three things are built and switched off until they have been tested in the public beta: Aria's daily initiative, which prepares up to ten proposals a day from what the workspace shows; checks that run against your GitHub repositories through the GitHub App; and Aria on the public site, answering visitors' questions from the help centre and the legislation with citations.

Where to next

Let the calendar run itself.

Start with one system: classify it, accept the obligations it brings and let the reminders take it from there. No card, no calls.

Check my obligations for free See pricing