FEATURE industry built around global semiconductor, software and infrastructure supply chains.
Instead, Brazil wants to identify the dependencies it cannot avoid and reduce the ones it considers dangerous.
Under the Market Listening Support Handbook, the future platform should allow technologies, particularly software, to be developed, maintained and evolved by Brazilian institutions and teams. That makes software control central to the strategy.
Serpro has already spent years working across multiple public Cloud environments. Alexandre Improta, strategic projects manager at Serpro’ s Data Center, said the organisation began operating in this model in 2019 and now works with technologies from different providers.
“ This experience integrates the technical references used in the discussion of the Brazilian Cloud. The goal is to establish mechanisms that allow the use of external technologies while maintaining control over elements considered critical to the operation,” said Improta.
In practice, that means designing an infrastructure capable of surviving supplier changes. Two requirements are particularly important: interoperability and national capability.
The architecture is expected to use open standards, allow migration between environments and support equipment from different vendors. These sound like familiar enterprise technology principles, but in a sovereign Cloud they become geopolitical safeguards.
Vendor lock-in is no longer simply a procurement problem when the workloads involved support government operations or critical public services. Dependence on one proprietary platform can become dependence on a particular company, jurisdiction and technology ecosystem. Brazil therefore wants sovereignty to vary according to the importance of the workload.
A relatively low-risk application may tolerate dependencies that would be unacceptable for a system supporting essential government services. As criticality increases, so does the required ability to operate, recover, audit, modify and ultimately replace parts of the infrastructure.
But Brazil is also attempting something harder: turning the abstract language of technological sovereignty into numbers.
Serpro has developed what it calls the Sovereignty Gradient, an assessment methodology dividing sovereignty into three areas. Data sovereignty accounts for 30 % of the score, technological sovereignty another 30 % and operational sovereignty 40 %. Fifteen criteria feed into the index. The heavier weighting given to operations is significant.
A platform can satisfy residency requirements and still leave its operator dangerously dependent on someone else to keep it running. Operational sovereignty asks a more basic question: if outside assistance disappears tomorrow, can the service continue? Serpro is trying to prove the answer rather than accepting contractual assurances.
It is effectively a technological stress test for sovereignty.
26
INTELLIGENT CIO LATAM www. intelligentcio. com