Deployment & support model
What is it actually like to buy, deploy and be supported on this — including whether the price is discoverable at all?
Requirements, evidence source, and references
This page is the citable form of this dimension — a finding elsewhere can link straight to the bar it was judged against.
Deployment & support model
7 requirementsWhat is it actually like to buy, deploy and be supported on this — including whether the price is discoverable at all?
Pricing is published, indicative, or contact-only — recorded as found, without treating contact-only as disqualifying.
Trial availability and evaluation licensing: can an engineer try it before a sales conversation?
Contract flexibility — term length, exit terms, and whether migration off the product is contemplated.
Migration support offered, and whether it is included or a separate professional-services line.
Documentation is sufficient to deploy without a sales engagement.
Support model and response commitments are stated, including who carries the pager for a cryptographic defect.
A published vulnerability-disclosure process, and a track record of using it.
Where to report, and expected response time.
Whether past advisories were published, and how quickly patches followed.