Vendor library
Already-assessed vendors you adopt instead of assessing from scratch — and what adoption actually brings.
The problem it solves
Large cloud providers and global platforms do not answer customer questionnaires. Assessing one from scratch means assembling a dossier from public documentation — work every organization does separately and arrives at similar conclusions.
The library is that work done once. You find the vendor, adopt it, and it enters your portfolio already assessed.
Two kinds of entry
Some entries are built from collected and curated public evidence — the hyperscaler case, matching the P0 profile. Others are shared assessments, where a supplier answered and agreed to make the result available.
The origin is visible on the entry, and it matters: an assessment answered by the supplier itself and a dossier assembled from outside do not carry the same evidential weight, even when they reach the same conclusion.
Adopting creates a supplier of your own
Adoption does not create a shortcut or a link: it creates a supplier in your organization, with the assessment already filled in. From then on it is yours — it enters your risks, your reports, and your per-area views like any other.
That also means you can add to it. A library entry is a starting point, not a verdict: if your contract with that vendor has particularities, they go into your copy.
Translation
Adopted content is translated into your organization's language where needed. The adoption is marked incomplete while that finishes, rather than appearing ready with half the content in another language.