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.
A vendor manager at a desk reviewing supplier contracts
Turns the vendor spreadsheet into the dependency register a supervisor can read, before the next contract quietly renews.
Specimen: a 600-person payments firm, EUReight of 38 vendors
VendorSpendShareLands inContract end
Northlane Cloud single source 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.
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.
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. Quoted from a human-verified compliance corpus under licence. The DORA register of information exports in the supervisory template's column order.

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 clause text behind every obligation is quoted from a human-verified compliance corpus under licence. The register computes on your own list and names the lists to check; it never rules on a vendor or a country.