Vendor Register

Paste your vendor list. Get the register the regulator asks for by name.

Per vendor: what you depend on it for, the share of your spend and your systems that sit with it, the country the dependency lands in, the vendors with no fallback, the obligations DORA, NIS2 and NIST SP 800-161 attach to that relationship, the contract clauses each expects, and the DORA register entry. Eight vendors free, no account.

Build your own registerEvery share and every finding is arithmetic on the columns you paste, in your browser. Nothing leaves it until you choose to save.
Try one of yours
A vendor manager at a desk reviewing supplier contracts
Walk into the supervisory review with the concentration, the single-source vendors and the register of information already filled, from the vendor spreadsheet you already keep. Paste a plain vendor list and get it read against DORA, NIS2 and NIST SP 800-161 in your browser, cited so you can check it, with no third-party risk platform to buy.
Specimen: a 600-person payments firm, EUReight of 38 vendors
VendorSpendShareLands inContract end
Northlane Cloud single source share at or above 25% no exit plan€2,050,00027.8%IEIreland412 days
Anvil Pay Acquiring€640,0008.7%IEIreland350 days
Cardinal Scheme Services no contract end€310,0004.2%BEBelgiumnot stated
Greyfriar Managed IT chain of two or more€296,0004.0%INIndia180 days
Quillon Compute origin unconfirmed€205,0002.8%DEGermany vendor country not stated150 days
Tidewater Staffing ends inside 90 days€190,0002.6%DEGermany30 days
Ebbtide Bank single source€142,0001.9%DEGermany545 days
Zorvane Analytics unrecognised€42,0000.6%EEEstonia220 days
38 vendors€7,376,00011 countries
Spend, share and where the dependency lands, as the register computes them from the pasted columns. The full register adds the systems each vendor touches, the criticality, nine findings, the obligation rows under DORA and ISO 27001, and the register-of-information entry per vendor.
Vendor risk assessments

Standard workflows and templates to assess and evaluate third-party risks

Assess and evaluate each vendor across a wide range of third-party risks: financial, legal, strategic, reputational, ethical, information security, operational, cybersecurity, environmental and geopolitical risks. Ten standard templates, one per risk domain, each question citing the DORA, NIS2, NIST SP 800-161 or ISO/IEC 27001 clause it comes from or marked general practice. The workflow: pick the vendor from your register (or a prospective one), confirm the domains suggested from its category and criticality, assign an assessor and a due date, answer with evidence by reference, send the vendor a questionnaire link for its part, rate each domain yourself (inherent and residual, with a rationale; the tool never sets a rating), raise findings with remediation actions and owners, and have a reviewer approve or return it with a reason. Portfolio by domain and rating, CSV and XLSX exports. On Solo and Team; the specimen is open to read.

FinancialLegal and regulatoryStrategicReputationalEthicalInformation securityCybersecurityOperational resilienceEnvironmentalGeopolitical and country

One vendor per line: Vendor | provides | category | annual spend | vendor country | service country | systems | single source | contract end | criticality | exit plan | subcontractors. Tabs, commas or pipes; a header row is optional and its column names are recognised in any order. A first line dora: yes | as at: 2026-09-19 ticks the regime and pins the date.
Classification and every figure run in your browser against a published dictionary. Nothing is sent anywhere until you choose to save.
Reads the homepage and up to six of its own pages (privacy, subprocessors, security, trust, careers, about) and fills the list with what they load and name, the page behind every row. Only the address you type is sent.
01

Paste the list you already have

The procurement export, the contract folder index or the spreadsheet the last audit produced: one vendor per line, with what it provides, the annual spend, the countries, the systems it touches, whether it is the only source and when the contract ends, in any order the header names. Every vendor is matched against a published dictionary of 45 categories in eight families; a vendor that matches nothing is marked unrecognised and never guessed.

02

Read what depends on each vendor, and where

Per vendor: the share of annual spend, the share of the systems named, the country the dependency lands in, the criticality as pasted or derived from the systems and the single-source answer, the days left on the contract. Per register: the largest vendor, the top three, the largest country, the vendors with no fallback, the contracts ending inside 90 and 180 days. Each figure is a comparison of your own columns, never a verdict on a vendor.

03

Take the obligations to the contract folder

Tick the regimes that reach you and each vendor carries the clauses that attach to the relationship: DORA Articles 28 to 31 and the key contractual provisions of Article 30, NIS2 Article 21(2)(d), 21(3) and 24, the NIST SP 800-161 supplier controls, ISO 27001 controls 5.19 to 5.23. Requirement text is our own statement of each clause, read from the published text and cited so you can check it against the official text. The DORA register of information exports with the fields the supervisory template asks for.

04

Assess and evaluate every third-party risk, with standard workflows and templates

Templates for financial, legal, strategic, reputational, ethical, information security, operational, cybersecurity, environmental and geopolitical risks, each question cited to its clause or marked general practice. Assessor and due date, answers with evidence by reference, a vendor questionnaire link, your own inherent and residual rating per domain with a rationale, findings with remediation, reviewer approval or return, an append-only history, and the portfolio by domain and rating in CSV and XLSX.

Why a register and not a vendor risk platform

The platforms are built for the bank with a procurement function and a licence budget. The vendor manager at a 600-person firm has a contract folder, a spreadsheet and a supervisor who now asks for the register by name. Before the platform conversation, somebody has to say what the business depends on each vendor for, where that dependency lands, which vendors have no fallback and which contracts carry the clauses the regime expects. That is the register this builds, in your browser, from the list you already hold.

The dictionary and the obligation table are ours and published in full: every vendor category it recognises, in eight families, and what each regime attaches to a vendor relationship. The requirement text behind every obligation is stated in our own words from the published standards, read clause by clause from the published text. The register computes on your own list and names the lists to check; it never rules on a vendor or a country.

Building the vendor register of information: the questions buyers ask

What does Vendor Register produce?

It turns your pasted vendor list into the register a supervisor asks for by name. Per vendor it shows what you depend on it for, the share of your spend and systems that sit with it, the country the dependency lands in, the vendors with no fallback, and the obligations each regime attaches to that relationship.

Which regimes does it read against?

DORA (Regulation (EU) 2022/2554), the NIS2 Directive, NIST SP 800-161 Rev 1 and ISO/IEC 27001:2022. It states each obligation in our own words from that text, cited to its clause, and where the page names an obligation without stating its requirements, it says so and does not state them.

Which clauses does it attach to a vendor relationship?

DORA Articles 28 to 31 and the key contractual provisions of Article 30, NIS2 Article 21(2)(d), 21(3) and 24, the NIST SP 800-161 supplier controls, and ISO 27001 controls 5.19 to 5.23. The requirement text is read clause by clause from the published text.

Can it produce the DORA register of information?

Yes. Each vendor carries a DORA register entry, and the register of information exports with the fields the supervisory template asks for.

How does it decide what each vendor is?

Every vendor is matched against a published dictionary of 45 categories in eight families. A vendor that matches nothing is marked unrecognised and never guessed.

What figures does it compute?

The share of annual spend, the share of the systems named, the country the dependency lands in, the criticality as pasted or derived, the days left on the contract, the largest vendor, the top three, the largest country, the vendors with no fallback, and the contracts ending inside 90 and 180 days. Each figure is a comparison of your own columns, never a verdict on a vendor.

What do I paste, and how?

One vendor per line, with the fields the header names recognise in any order, separated by tabs, commas or pipes, and a header row optional. A first line such as dora: yes | as at: 2026-09-19 ticks the regime and pins the date.

Can it read my company's website instead of my list?

Yes. You can enter your company's website and it reads the homepage and up to six of its own pages, such as privacy, subprocessors, security, trust, careers and about, and fills the list with what they load and name, keeping the page behind every row. Only the address you type is sent.

Does the register assess the vendors?

No. The register computes on your own list and names the lists to check, and it never rules on a vendor or a country. Whether a dependency is acceptable is a judgement for you and your supervisor.

Can I assess and evaluate the third-party risks, not just register the vendors?

Yes, on Solo and Team. There are ten standard templates, one per risk domain, each question cited to its clause or marked general practice, and you assign an assessor and a due date, answer with evidence by reference, and rate each domain yourself, inherent and residual, with a rationale. The tool never sets a rating.

How much does it cost to try?

Eight vendors are free and no account is needed. The specimen register of 38 vendors is open to read.

Does anything I paste leave my browser?

No. The classification and every figure run in your browser against a published dictionary, and nothing is sent anywhere until you choose to save.

How Vendor Register compares with the alternatives

A spreadsheet is better as the vendor list you keep, because it is free and holds every field you already record. A procurement, legal or compliance consultant is better on judgement, since whether a dependency is acceptable and what a contract must contain are their call, and a third-party risk platform is better once a procurement function is feeding it and contracts are managed inside it. A general AI assistant is better at summarising a contract or explaining DORA Article 30, but it does not compute each vendor's share of spend and systems or attach the DORA, NIS2, NIST SP 800-161 and ISO/IEC 27001 obligations to the relationship. Vendor Register reads the list you already hold and produces a per-vendor register — what you depend on each vendor for, where the dependency lands, the vendors with no fallback and the contracts ending inside your window — and never rules on a vendor or a country.

Primary source: DORA (Regulation (EU) 2022/2554)