Montro
One supplier entry, Harbourline CRM BV, feeding six registers: register of information, material third-party register, record of processing, supply-chain records, AI inventory and control evidence

Six registers, one set of supplier records

Third-party and AI rules now overlap. DORA, the UK's new third-party rules, GDPR, NIS2 and the EU AI Act each ask for their own record, often about the same suppliers, and ISO 27001 asks for evidence of the controls behind them.

Montro keeps one entry for each supplier and feeds every register from it. Changes are raised with their source, the supplier confirms, and your team decides, so your registers agree with each other.

Framework

The registers behind each regulation

What each regulation asks you to keep, and what Montro does to keep it true.

AI — EU AI Act: your AI inventory

AI

EU AI Act: your AI inventory

A record of the AI systems you use, your role for each and the category your team sets. Montro brings in the tools it finds and keeps each decision with the entry.

Learn more

Processing

GDPR: your record of processing

The Article 30 record, with processors and sub-processors linked to the activities they support. New sub-processors are raised for your team to review.

Learn more
Processing — GDPR: your record of processing
Third parties — DORA: your register of information

Third parties

DORA: your register of information

Only financial entities keep one. Montro raises supplier changes, so the register is up to date when it is submitted each year.

Learn more

Supply chain

NIS2: your supply-chain records

Essential and important entities keep records of their direct suppliers under Article 21. Lapsed certificates and new suppliers are raised with their source.

Learn more
Supply chain — NIS2: your supply-chain records
A Dublin waterfront building with a card showing Montro built where the regulators are: Dublin-built, hosted in Frankfurt, read-only and penetration-tested

European

Built where the regulators are

Montro is built in Dublin by Outproduct Ltd and hosted on AWS in Frankfurt. The platform is penetration-tested, and ISO 27001 certification is in progress.

Hosted in Frankfurt

On AWS in the EU. Your register and its history are held there, and connections to your systems are read-only by default.

Built around European registers

Entries follow the registers EU and UK rules ask for, from the DORA register of information to the GDPR record of processing, rather than a generic vendor list.

Setup

What the 30-day pilot looks like

A proof of concept run on your real suppliers, with your team deciding at each step.

Day 1: connect in under an hour

Read-only links to sign-in, directory and finance. Nothing to install unless you add the optional browser extension.

Week 1: candidates to review

Montro proposes the suppliers and AI tools it finds, each with its source. Your team confirms which ones belong.

Weeks 2–4: registers take shape

Accepted entries feed the registers that apply to you, and supplier changes start coming through for review.

Day 30: decide on evidence

You’ve seen the registers built from your own suppliers, and you decide whether to continue.

Two colleagues reviewing the day 30 pilot outcome: entries accepted, changes decided and registers that apply

Outcome

Evidence, not a demo

By day 30 the registers already reflect real decisions, so the choice to continue rests on what you’ve seen.

Questions

Which rules apply, working across borders, and what you share with regulators.

It depends on your sector, your size and where you operate. DORA covers financial entities, NIS2 covers essential and important entities in its sectors, GDPR covers anyone handling personal data, and the EU AI Act covers anyone building or using AI. The UK has its own third-party rules for regulated financial firms. Your team marks which registers apply, and entries feed only those.

The EU rules are the same everywhere, but NIS2 and parts of GDPR depend on national law. Montro keeps one entry per supplier, and your team records which entity or country each register is kept for.

No. Regulators have no access to Montro. Your team decides what to share and submits it through the regulator’s own channels.

The register is built around the EU AI Act. New rules are added to the product as they take effect, and we only say we cover them once they are live.

No. Most of what each register asks about a supplier is the same: who they are, what they support, where they process data and who owns them. Montro asks once and fills each register from that.

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.

Priced to scope — never per seat, never per supplier. Upgrade only when the evidence earns it.

Montro register dashboard during the 30-day proof of concept