Vendor under data sovereignty rules
Sovereignty and procurement rules become weights, OSS rises.
Open the live lab · preloaded to this scenario
Vendor Selection and Concentration Risk Monitor
Context
A government agency procures an AI vendor under data sovereignty and public procurement rules. Data must stay in country, lock in is politically unacceptable, and the process must defend every criterion.
The decision
Encode sovereignty and low lock in as heavy weights and the open source backed, portable option wins, the constraints are the scorecard.
What most miss
Procurement teams treat sovereignty as a checkbox; it's actually a weighting that reshapes the whole ranking away from the hyperscaler default.
Stakes
A sovereignty breach or an un exitable contract is an audit and public accountability event.
Studied · AI Investment Strategy and Portfolio Governance · verified 2026-07-03
Sources: Public-sector AI procurement (data sovereignty, anti-lock-in); Constraint-as-weight vendor scoring