Europe’s digital autonomy debate needs procurement teams and IT staff

Bert Hubert’s essay, “EU & Civil Society need to progress on Digital Autonomy”, pushes Europe’s digital autonomy debate away from slogans and into the offices that sign contracts, run migrations, defend tenders, and support users.

European officials, think tanks, and civil society groups have spent years debating autonomy, sovereignty, and values. Hubert argues that those talks now miss the people who turn policy into systems: procurement officers, government IT teams, vendors, ministry executives, change managers, and reporters who shape public patience.

The problem starts with incentives. Procurement teams face lawsuits when they restrict tenders to European suppliers. IT departments have spent decades building around Microsoft, Amazon, and Google. Contractors and consultants know those platforms, sell those platforms, and warn ministries away from change. Ministers can announce autonomy, but staff still need budgets, legal cover, skills, and vendors that can survive public-sector buying rules.

Hubert’s strongest point concerns the chain of execution. Politicians need to care. Ministries need to direct agencies. Executives need to back technical staff. Procurement teams need to defend tenders. Vendors need to bid. Users need to accept friction. Civil society can help each link, but panels about definitions will not move a mail server, replace an identity system, or migrate a document suite.

That frame gives the debate a sharper technical shape. Europe does have servers, software, and skilled engineers. Europe lacks mature substitutes for the full U.S. cloud model and the office computing stack that governments use each day. A ministry can buy compute from a European provider, but it still needs identity, email, document editing, collaboration, device management, logging, compliance controls, backup, and support contracts that procurement staff can defend.

The consistency model matters as much as the vendor logo. Governments need to decide which systems demand national control, which systems can run with European operators, and which systems can tolerate foreign dependencies under contract. A public login system, health registry, police platform, or tax workflow carries a different risk than a public brochure site. Civil society can help officials rank those systems and map each class to procurement rules, operational controls, and exit plans.

Hubert also points to a legal gap. Many officials believe trade rules prevent member states from limiting tenders to European suppliers. Recent European court decisions give governments more room to use national security exceptions than many procurement teams assume. Civil society groups could turn that legal work into usable guidance, model clauses, and defense funds for public buyers who choose European suppliers and expect litigation.

The API design lesson sits under the policy argument. Governments that want autonomy need interfaces that let them change providers. They need portable identity, exportable data, documented schemas, tested disaster recovery, and contracts that include exit drills. A vendor can meet a sovereignty label while still trapping a ministry behind proprietary formats, opaque admin tools, and workflows that only one integrator understands.

Open source helps, but Hubert warns against treating openness as the finish line. Users still need tools that work under deadline pressure. Administrators need support. Procurement teams need suppliers that answer tenders. A pure project with weak documentation and no service model will lose to Microsoft in a ministry that must keep 20,000 employees working Monday morning.

Civil society can do useful work here. It can bring procurement groups, vendors, IT staff, lawyers, and change managers into the same room. It can publish maps of the software stack, separate mature products from gaps, and explain where governments need investment. It can press media outlets to cover European alternatives with the same seriousness they give U.S. incumbents.

The trade-off is cost. European governments may need to accept higher short-term spending, slower migrations, and some user discomfort. They may need state-backed companies or hybrid public-private bodies that can build capacity outside the standard consultant model. That approach carries risk, but the current path also carries risk: foreign platform dependence, weak exit power, and public services that ministers cannot control in a crisis.

Hubert does not ask civil society to stop talking. He asks it to aim its meetings at execution. The next useful panel may include fewer speeches about values and more people who know tender law, mailbox migration, identity federation, support desks, and user training. Europe will make progress when those people can leave the room with money, authority, and a plan.