Montro

Know which suppliers need you, and which don’t

Montro keeps one register of the suppliers and AI services your organisation depends on. Changes reach you as a roll-up with the exceptions that need a decision, each with its source and an owner, so you can show who decided, on what evidence, and when.

Know which suppliers need you, and which don’t

The problem

More alerts, fewer answers

Watching suppliers is easy now. Showing what was decided about each change is not.

Findings pile up without owners

A security tool can flag a supplier change. It cannot tell you who owns the decision, or record what they decided.

AI arrives inside tools you already approved

A supplier switches on an AI feature, and the approval you gave last year no longer covers what the tool does.

The board asks for posture, not a feed

A list of every alert does not answer whether your suppliers are in a state you can defend.

How Montro helps

From a supplier list to a record you can defend

Three steps that turn a list of suppliers into evidence.

Register

Every supplier and AI service in one place

Built read-only from sign-in, directory, finance and cloud data.

Changes

Each change raised with its source

Mapped to the NIS2, DORA and EU AI Act articles it touches, for its owner to review.

Decisions

Every decision on the record

A roll-up for the board, and the trail behind each answer for the examiner.

Setup

From connection to a register in 30 days

An admin approves read-only access. Montro starts building the register straight away, and your team decides on what it raises.

Day 1: connect read-only

Microsoft Entra ID, Google Workspace or Okta, approved by an admin. No agents to install.

First week: first candidates

Suppliers and AI services found so far, each raised with its source for its owner to review.

Rest of the pilot: decisions

Owners decide on each candidate, and entries are mapped to GDPR, the EU AI Act, DORA and NIS2.

After the pilot: the register stays current

New changes are raised as they appear, dormant suppliers are re-tiered, not removed, and every entry keeps its owner.

Outcome

Evidence that holds up when it is asked for

A register with a decision behind every entry, in place of spreadsheets and screenshots.

Request a pilot

Obligations

Three regulations, three records, one intake

DORA, NIS2 and the EU AI Act each ask for their own record. Montro keeps all three from the same read-only intake, so a change is reviewed once and reflected in every record it touches.

DORA register of information

Article 28(3), for financial entities. Each ICT contract, the function it supports, whether that function is critical or important, and the exit plan, kept current for your filing.

Learn more

NIS2 supply-chain records

Article 21. The suppliers behind your network and information systems, each with an owner and a decision on every change.

Learn more

EU AI Act AI inventory

The AI systems you use as a deployer, recorded in the same register as your suppliers, so one review covers both.

Learn more

Keep reading

The rest of your governance team

One register serves every seat at the table. See what it gives your colleagues.

For DPOs

Sub-processor changes reach your DPO confirmed by the supplier, so the Article 30 record stays true.

Read more

For IT Directors

IT decides which candidates cross into the register, and sees unused licences before renewal.

Read more

For Heads of Compliance

The register of information, current and with a decision behind every entry, ready for the examiner.

Read more

Questions

The questions CISOs ask before they connect anything.

No. Montro reads from systems you already run: sign-in and OAuth grants, directory and licence data, finance and cloud accounts. The optional browser extension is off by default and reads metadata only.

Anything that never touches your identity provider, directory, finance systems or cloud accounts, such as a tool paid for privately and used without company sign-in. You get the full scope list, including these limits, before you connect.

Montro raises them as candidates against the EU AI Act’s high-risk categories, and your team confirms each one. Whatever you decide, whether an assessment, added oversight or retiring the tool, stays on the record. High-risk obligations apply from December 2027.

It's the register of information under Article 28(3): your contracts with ICT providers, the business functions they support, whether each supports a critical or important function, substitutability, exit plans and annual expense, kept ready to file as xBRL-CSV. You file it; Montro keeps it true.

Yes. Montro reads from your identity provider, directory, finance systems and cloud accounts, and is built to sit alongside the GRC and security tools you already run, not replace them.

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 AI discovery audit dashboard