Government Digital Infrastructure Procurement Competition Issues

Introduction

Government digital infrastructure procurement concerns the acquisition of cloud computing, data centres, government networks, digital identity systems, cybersecurity infrastructure, AI infrastructure, software platforms, APIs, interoperability systems, data-management platforms and related technology services by public authorities.

Competition problems can arise at every stage of procurement. Governments may unintentionally create single-vendor dependence, excessive technical specifications, interoperability barriers, incumbent advantages, discriminatory qualification requirements, exclusive data access, vendor lock-in and opaque evaluation criteria. Conversely, governments may legitimately restrict competition where national security, resilience, confidentiality or technological compatibility genuinely requires it.

The central competition-law question is therefore:

When does the government's design or conduct in procuring digital infrastructure protect legitimate public interests, and when does it unnecessarily distort competition or entrench particular technology suppliers?

1. Relevant Legal Framework

Government digital procurement can engage several overlapping legal regimes:

A. Public procurement principles

Competitive procurement generally requires:

• transparency;
• equal treatment;
• non-discrimination;
• proportionality;
• objective technical specifications;
• genuine opportunities for competing suppliers;
• transparent evaluation criteria; and
• effective review of procurement decisions.

Digital procurement makes these principles more difficult because technical specifications can effectively determine which vendors are capable of bidding.

B. Competition law

Competition law becomes relevant where procurement arrangements:

• exclude rival suppliers;
• facilitate bid rigging;
• create or reinforce dominance;
• confer artificial advantages on incumbents;
• restrict interoperability;
• impose discriminatory access conditions; or
• enable collusion through procurement platforms.

C. State-created competitive distortions

A government itself may not always be acting as an ordinary commercial purchaser. Nevertheless, competition concerns can arise where state measures structure markets in a way that protects incumbents or excludes competitors.

D. Digital-specific concerns

Digital infrastructure introduces additional competition variables:

1. network effects;
2. switching costs;
3. data portability;
4. cloud migration costs;
5. interoperability;
6. proprietary standards;
7. cybersecurity certification;
8. access to government datasets;
9. technical expertise;
10. intellectual-property rights; and
11. long-term maintenance dependence.

2. Market Definition Problems

The first difficulty is determining the relevant market.

A government cloud procurement, for example, could concern:

• general cloud infrastructure;
• sovereign cloud services;
• government-certified cloud services;
• infrastructure-as-a-service;
• platform-as-a-service;
• data-centre capacity;
• cybersecurity services;
• government networking; or
• integrated digital infrastructure.

A procurement authority may define the requirement so narrowly that only one or two suppliers qualify.

For example, a tender requiring a particular proprietary architecture, certification history, hardware ecosystem and geographic footprint could effectively transform a competitive market into a single-supplier market.

Competition analysis should therefore distinguish between:

genuine functional requirements and requirements that unnecessarily reproduce an incumbent's existing technology.

3. Vendor Lock-In

Vendor lock-in is one of the most important competition concerns.

A government may initially select a supplier through a competitive tender. However, subsequent dependence can make future competition practically impossible.

This may occur through:

• proprietary APIs;
• incompatible databases;
• proprietary data formats;
• expensive migration;
• long-term licensing;
• proprietary security architecture;
• specialized hardware;
• exclusive technical expertise; and
• accumulated institutional dependence.

The initial procurement may therefore be competitive while subsequent procurement becomes effectively non-competitive.

Competition implication

The authority should consider lifecycle competition, not merely competition at the moment of the initial tender.

4. Proprietary Technical Specifications

A tender specification can indirectly favour a particular supplier.

For example:

"The system must be compatible with Vendor X's proprietary architecture."

Such a specification may eliminate otherwise capable competitors without an objective technological justification.

More neutral specifications would ordinarily focus on performance outcomes, such as:

• processing capacity;
• security level;
• latency;
• availability;
• interoperability;
• encryption;
• resilience; and
• recovery time.

This is commonly described as the difference between technology-specific procurement and function-based procurement.

5. Interoperability and Open Standards

Interoperability is particularly important in digital infrastructure.

If government systems cannot communicate with competing systems, the incumbent supplier may acquire significant market power.

Examples include:

• cloud-to-cloud interoperability;
• identity-system interoperability;
• API interoperability;
• government payment systems;
• health-data systems;
• public-sector databases;
• digital identity;
• smart-city infrastructure; and
• cybersecurity systems.

Competition authorities may therefore examine whether interoperability restrictions have the practical effect of foreclosing adjacent suppliers.

6. Data Advantages

Government procurement can create significant data advantages for incumbent contractors.

A contractor may obtain access to:

• operational government data;
• citizen-service data;
• transport information;
• infrastructure information;
• cybersecurity information;
• procurement information; or
• administrative datasets.

If the contractor can subsequently use those datasets commercially while competitors cannot obtain comparable access, the procurement can produce data-based competitive advantages.

The issue becomes particularly serious where data is:

• exclusive;
• non-replicable;
• continuously updated;
• necessary for competing services; or
• technically difficult to migrate.

7. Incumbency Advantage

An existing government contractor often possesses:

• institutional knowledge;
• historical datasets;
• security clearances;
• government-specific integrations;
• personnel familiarity;
• established infrastructure;
• knowledge of legacy systems; and
• relationships with government departments.

These advantages can make rebidding difficult.

A procurement authority should therefore consider whether tender design unintentionally gives the incumbent an artificial head start.

Potential safeguards include:

• standardized documentation;
• disclosure of relevant technical information;
• data portability;
• transition assistance;
• open APIs;
• independent evaluation;
• separation of incumbent knowledge from evaluation;
• and realistic migration periods.

8. Bundling and Vertical Integration

Digital infrastructure procurement frequently involves large integrated contracts.

A government might procure:

cloud + cybersecurity + networking + identity + data analytics + AI infrastructure

from a single supplier.

Bundling can produce efficiencies, but it can also exclude specialist competitors.

A large integrated contract may prevent:

• smaller cloud suppliers;
• cybersecurity firms;
• networking companies;
• AI infrastructure providers;
• open-source specialists; and
• local technology firms

from competing for individual components.

Competition test

Authorities should ask:

1. Is integration technically necessary?
2. Are separate lots feasible?
3. Does bundling produce measurable efficiencies?
4. Does bundling exclude capable competitors?
5. Can interoperability achieve the same benefits?

9. Excessive Qualification Requirements

Qualification requirements can become barriers to entry.

Examples include:

• very high minimum turnover;
• excessive previous-government-contract requirements;
• specific certifications;
• requirements for an existing national infrastructure footprint;
• excessive financial guarantees;
• proprietary technology certifications;
• mandatory experience with a particular platform.

Some requirements may be justified by cybersecurity or resilience concerns.

However, if they substantially exceed what is necessary to perform the contract, they may unnecessarily reduce competition.

10. Cybersecurity and Competition

Cybersecurity presents a difficult balancing problem.

Government agencies may legitimately require:

• security clearances;
• domestic data storage;
• certified encryption;
• incident-response capabilities;
• security audits;
• supply-chain security;
• resilience requirements.

But cybersecurity requirements can also inadvertently exclude smaller or foreign competitors.

The relevant principle is proportionality.

A security requirement should be sufficiently strict to protect government systems while not being more restrictive than reasonably necessary.

11. Sovereign Cloud and Digital Sovereignty

Government cloud procurement increasingly involves sovereignty requirements.

Governments may require:

• domestic data centres;
• domestic control of encryption keys;
• local ownership;
• domestic personnel;
• local incident response;
• restrictions on foreign governmental access.

These requirements may protect national security and strategic autonomy.

However, they can also:

• reduce the number of eligible suppliers;
• raise entry barriers;
• favour domestic incumbents;
• fragment international cloud markets; and
• increase procurement costs.

Competition analysis therefore requires separating legitimate sovereignty objectives from protectionist procurement design.

12. Bid Rigging and Collusion

Government digital infrastructure contracts can be particularly attractive targets for cartel behaviour because contracts may be:

• large;
• repeated;
• technically complex;
• concentrated among a small number of suppliers.

Potential conduct includes:

• bid rotation;
• market allocation;
• cover bidding;
• price coordination;
• subcontracting arrangements designed to facilitate collusion;
• exchange of sensitive bidding information.

Digital procurement systems themselves may also make sophisticated cartel detection possible because authorities can analyse:

• historical bids;
• bid timing;
• pricing patterns;
• geographic allocation;
• repeated subcontractors;
• identical technical language; and
• unusual bidding patterns.

13. Government Procurement Platforms and Algorithmic Risks

Electronic procurement platforms increasingly use algorithms to:

• shortlist suppliers;
• rank bids;
• detect suspicious bidding;
• evaluate technical compliance;
• predict supplier performance.

This creates a new competition issue.

If the algorithm:

• systematically disadvantages new entrants;
• relies on incumbent performance data;
• uses opaque scoring;
• embeds historical procurement biases; or
• automatically rejects innovative solutions,

the procurement system itself may become a barrier to entry.

Algorithmic procurement therefore requires transparency and auditability.

14. Cloud Concentration and Government Dependency

Government demand can substantially reinforce already concentrated technology markets.

A government choosing one dominant cloud provider for a nationwide system can provide that supplier with:

• large guaranteed revenues;
• reference-customer status;
• technical ecosystem advantages;
• scale economies;
• data advantages;
• increased developer familiarity.

The resulting market power can extend beyond the government contract into commercial markets.

This creates an important feedback loop:

Government procurement → scale → ecosystem expansion → increased market power → stronger position in future government procurement.

15. Framework Agreements and Long-Term Contracts

Framework agreements can simplify procurement but create competitive risks.

If a framework:

• lasts for many years;
• contains only a few suppliers;
• has broad scope;
• permits extensive call-offs;
• contains restrictive onboarding conditions,

new entrants may be excluded for the entire duration.

The longer the framework, the more important it becomes to preserve mechanisms for:

• new supplier admission;
• periodic competition;
• technology refresh;
• interoperability;
• and re-tendering.

16. Exclusive Government Contracts

An exclusive arrangement can sometimes be justified where:

• security risks are exceptionally high;
• interoperability requires centralized operation;
• emergency response requires one system;
• fragmentation would create unacceptable risks.

But exclusivity can also foreclose competitors.

The competition analysis should therefore examine:

1. duration;
2. scope;
3. market share affected;
4. alternatives available;
5. switching possibilities;
6. justification for exclusivity; and
7. whether less restrictive alternatives exist.

17. Six Important Case Laws

The following cases provide useful principles for analysing government digital infrastructure procurement and related competition issues.

1. Commission v. Italy (Case C-3/88)

The European Court addressed state-created advantages and restrictions associated with reserved activities.

Principle: State measures that reserve economic opportunities to particular entities can raise competition and internal-market concerns.

Relevance: A government cannot automatically assume that technological infrastructure arrangements are competitively neutral merely because they arise from public policy.

2. Telaustria and Telefonadress GmbH v Telekom Austria (Case C-324/98)

The Court emphasized transparency requirements in public procurement where a public authority awards a contract capable of attracting cross-border interest.

Principle: Procurement arrangements must provide sufficient transparency to permit meaningful competition.

Digital relevance: Government digital infrastructure contracts should not be structured so opaquely that potential technology suppliers cannot realistically compete.

3. Coname (Case C-231/03)

The Court considered public contracting and the obligation of transparency.

Principle: Even where detailed procurement directives may not apply, public authorities can be subject to transparency obligations where a contract has potential cross-border interest.

Digital relevance: Technology infrastructure contracts involving significant economic value should be designed with meaningful competitive access rather than purely formal tendering.

4. Pressetext Nachrichtenagentur GmbH v Republik Österreich (Case C-454/06)

This case concerned substantial modification of a public contract.

Principle: Material changes to a contract can amount to a new procurement requirement rather than merely an amendment of the original contract.

Digital relevance: A government should not use amendments to transform a limited IT contract into a substantially broader cloud, data or digital-infrastructure monopoly without renewed competitive scrutiny.

5. European Commission v Federal Republic of Germany – Stadtwerke Hamburg (Case C-480/06)

The case concerned public-sector cooperation and procurement obligations.

Principle: Public cooperation can fall outside ordinary procurement requirements in appropriately structured circumstances.

Digital relevance: Governments cannot automatically avoid competitive procurement merely by describing a digital infrastructure arrangement as public-sector cooperation. The precise institutional and economic structure matters.

6. Maxima Latvija (Case C-345/14)

The Court examined restrictive contractual arrangements and the distinction between restrictions by object and restrictions requiring effects analysis.

Principle: Not every potentially restrictive arrangement is automatically unlawful; its legal and economic context must be examined.

Digital relevance: Long-term exclusivity, interoperability restrictions or infrastructure commitments should be assessed according to their actual competitive effects rather than by labels alone.

18. Additional Important Authorities

Several competition cases outside traditional government procurement are also highly relevant by analogy.

Bronner v Mediaprint (Case C-7/97)

The Court established the demanding conditions for an essential-facilities type obligation.

Digital relevance: A government or government contractor controlling indispensable digital infrastructure may raise access questions, although the legal threshold for compulsory access remains demanding.

Microsoft v Commission (Case T-201/04)

The case involved interoperability information and exclusionary conduct.

Digital relevance: Interoperability can be central to competition where a dominant technology ecosystem controls an important interface.

Slovak Telekom v Commission (Joined Cases C-165/19 P and C-166/19 P)

The case concerned access and exclusionary conduct in telecommunications.

Digital relevance: Network infrastructure access conditions can have foreclosure effects when controlled by an undertaking with significant market power.

19. Competition Assessment Framework

A useful analytical framework is:

Stage 1 — Identify the procurement market

Determine:

• suppliers;
• substitutable technologies;
• geographic scope;
• market concentration;
• entry barriers.

Stage 2 — Examine tender design

Ask whether specifications:

• are technology-neutral;
• permit equivalent solutions;
• unnecessarily require proprietary technology;
• favour the incumbent.

Stage 3 — Examine structural effects

Assess:

• market foreclosure;
• concentration;
• entry barriers;
• network effects;
• data advantages;
• switching costs.

Stage 4 — Examine contract duration

Long contracts require greater scrutiny where they concern rapidly developing technology.

Stage 5 — Examine interoperability

Determine whether:

• APIs are open;
• data can be exported;
• migration is feasible;
• competing suppliers can connect.

Stage 6 — Assess justification

Government should identify legitimate objectives such as:

• national security;
• resilience;
• privacy;
• cybersecurity;
• continuity of government;
• cost efficiency.

Stage 7 — Apply proportionality

Ask:

Could the same legitimate governmental objective be achieved through a less competition-restrictive procurement design?

20. Remedies

Potential remedies include:

Structural remedies

• dividing large contracts into lots;
• separating infrastructure and software procurement;
• preventing excessive vertical integration.

Contractual remedies

• shorter contract periods;
• periodic re-tendering;
• termination rights;
• transition assistance;
• migration obligations.

Technical remedies

• open APIs;
• common data formats;
• interoperability requirements;
• portability;
• standards-based architecture.

Competition remedies

• independent procurement review;
• supplier-neutral specifications;
• transparent evaluation;
• competitive dialogue;
• multiple-supplier frameworks.

Data remedies

• government ownership of data;
• portability;
• restrictions on secondary commercial use;
• equal access where appropriate.

21. Key Competition Risks at a Glance

Conclusion

Government digital infrastructure procurement presents a distinctive competition-law challenge because procurement decisions can shape the structure of technology markets for many years. The problem is not simply whether the government obtains the lowest price in an individual tender. A procurement decision may determine who controls cloud infrastructure, data, APIs, cybersecurity systems, digital identity, government networks and other foundational technologies.

The most important principles are therefore:

1. Technology neutrality — specifications should focus on legitimate functional requirements.
2. Interoperability — systems should permit meaningful competition where technically feasible.
3. Portability — government data should not become a mechanism for permanent vendor lock-in.
4. Proportionality — security and sovereignty requirements should not unnecessarily exclude competitors.
5. Lifecycle competition — competition must be preserved beyond the initial tender.
6. Contractual flexibility — long-term arrangements should not unnecessarily foreclose future entrants.
7. Transparency — procurement design and evaluation should permit genuine competitive participation.
8. Structural awareness — governments should consider how major digital contracts affect the wider technology market.

Ultimately, competitive government digital procurement is not merely a purchasing objective; it is a market-design objective. A government that repeatedly awards foundational digital infrastructure to the same vertically integrated suppliers may unintentionally transform temporary procurement advantages into durable technological market power.