AI Governance
Your AI inventory under the EU AI Act, including AI switched on inside tools you already approved.
Read moreThe software and suppliers your business runs on
One register for the apps and suppliers you depend on, built from the accounts you already have.
How the register is built
What goes into the register
Where each entry comes from, how it is recognised and what it carries.
Sources
Five sources, all read-only
Sign-in, directory, finance and cloud each show a different part of what you use. An optional browser extension, off by default, adds the rest.
Catalogue
Matched against more than 20,000 apps
Each candidate is matched to a known app, so names and vendors are recognised rather than typed in.
Scores
Your risk scores, kept with each entry
Montro takes in the scores your team or your providers already use. It does not invent its own.
Lifecycle
A register that stays true after day one
New apps arrive as candidates with their source, and apps nobody uses any more are raised for re-tiering. The register reflects what the business uses now, not what it used on the day it was set up.
- New apps raised as candidates
- Unused apps re-tiered, history kept
- Each change linked to its source
Benefits
What the register saves you
Fewer one-off requests, fewer rebuilt lists, and one place to look when someone asks what the business uses.
Answers without rebuilding
When someone asks what the business uses, the register already holds the answer. Nobody has to compile a fresh list.
One list everyone works from
IT, finance, security and data protection work from the same entries, instead of each keeping their own version.
Overlap
Spot tools that do the same job
With apps matched to the catalogue, teams paying for similar tools show up side by side, so you can decide which to keep.
Data
What the data shows
More of what European businesses run now comes from outside suppliers, which is why the register behind them matters.
52.7%
of EU enterprises paid for cloud services in 2025
58.2%
of those firms run finance or accounting software in the cloud
65.5%
of those firms buy security software as a service
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 moreQuestions
How the register is built, where data lives and what it connects to.
Mostly from what is already recorded elsewhere: apps people sign into or grant access to, apps you pay for, and services in your cloud accounts. An optional browser extension adds the rest. Each one arrives as a candidate, with its source.
In Frankfurt, on AWS in the EU. What Montro stores is the register itself (app names, owners, sources and decisions), not the data inside those apps.
Connecting takes about an hour. Candidates appear once the first source is connected, and you can add the others at your own pace.
Yes. It connects to Okta, Microsoft Entra ID or Google Workspace for sign-in, and to AWS, Azure or GCP for cloud. It sits alongside your stack and changes nothing in it.
The same entries feed your DORA register of information, the UK material third-party register, your GDPR record of processing, NIS2 supply-chain records, your EU AI Act inventory and ISO 27001 control evidence. Your team decides what goes into each.
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.
