Montro

AI governance for the tools you deploy

An EU AI Act inventory of the AI tools your teams use, with an owner and a decision for each.

AI governance for the tools you deploy

Deployer duties

From inventory to oversight

When a tool is high-risk, deployers must assign human oversight, keep the logs it produces and inform workers it affects. Montro records who is responsible for each duty and keeps the record with the tool’s entry.

  • An oversight owner for each high-risk tool
  • Logs and notices filed with the entry
  • Worker information recorded
Book a pilot

Deployer

You are the deployer

Most of the AI your organisation uses was built by someone else. The Act still gives you duties of your own.

Deployer

What the Act asks of every deployer

Keep staff AI-literate and stay clear of prohibited practices. Public bodies, and firms using AI for credit scoring or insurance pricing, also assess the impact on fundamental rights before first use. Deepfakes and emotion recognition must be disclosed to the people they affect.

Provider

When you become the provider

Put your name on a high-risk system, change it substantially, or use a tool for a high-risk purpose it wasn’t built for, and the Act can treat you as its provider. Your team records the role for each tool, so a change in role doesn’t go unnoticed.

What the inventory holds

Each AI tool, on record

What sits behind each entry in your AI inventory, and who is responsible for it.

Signals

AI switched on, raised for review

When a tool you already approved adds an AI feature, it comes back to your team with its source.

Roles

Deployer or provider, recorded

Your duties under the Act depend on your role. Your team records it for each tool, so the right obligations are followed.

Category

Risk category, set by your team

Montro can suggest where a tool may sit under the Act. Your team sets the category and records why.

Benefits

What changes once AI is on record

Three moments where it pays off: a vendor ships an AI update, two teams review the same tool, and an AI contract comes up for renewal.

Vendor AI updates, reviewed

When a vendor adds AI to a product you use, it reaches your team as a change to review, with the vendor’s announcement as its source.

Data protection and security on one entry

Your DPO and your security team assess the same AI tool from the same record, so a DPIA and a security review don’t start from separate lists.

Renewals

Renewals that ask about AI

When an AI tool comes up for renewal, its entry shows the features in use, the data it handles and past decisions, so procurement asks the right questions.

Keep reading

Other parts of the platform

Each capability works from the same supplier entries. See what else they support.

Compliance

How each change is raised with its source, decided by your team and recorded in the registers you keep.

Read more

App & Supplier Register

How the register is built: five read-only sources, a catalogue of more than 20,000 apps, and your scores.

Read more

Questions

High-risk uses, general-purpose AI, prohibited practices and who answers for what.

An AI system is high-risk in two cases. First, when it is a safety component of a product, or the product itself, that EU law already requires a third party to check, such as a medical device. Second, when it is used in an area listed in Annex III, such as recruitment, credit scoring, education or access to essential services, unless it only performs a narrow or preparatory task. Montro flags tools that may fall into these areas, and your team sets the category.

The obligations for general-purpose AI models sit with the companies that build them, and have applied since 2 August 2025. Your duties depend on how you use the tool: drafting emails is not high-risk, but screening CVs with the same tool can be. The register records the use, not just the tool.

Prohibited practices have applied since 2 February 2025, so that use has to stop. Montro raises the tool for review, your team records the decision to stop or change the use, and the entry keeps that history.

Categories are set by your team, so they stay as decided until you change them. When guidance changes or a date moves, as the Digital Omnibus did for high-risk duties, affected entries can be reviewed again with the earlier decision kept.

Both, for different things. The vendor answers for how the system is built; you answer for how you use it. Montro keeps both sides on one entry: the vendor’s documentation and your own decisions.

Third-party records are becoming decision logs. The firms that get this right will be the ones that can show who decided, on what evidence, and when.

  • Pen-test summary on request
  • Frankfurt hosting
  • Sample register
  • Expert Series guests
  • Cyber Ireland member

See it on your own suppliers

A read-only connection, about an hour to set up, and a named person who can say yes to a decision.

By booking you agree to our Terms of Service.

Montro AI discovery audit dashboard