Competition Law and Vertical Integration in Software Markets

1. Introduction

Vertical integration occurs when a firm operates at multiple successive levels of a supply chain—for example, a company that controls an operating system, app store, cloud infrastructure, software applications, advertising technology, or distribution platform simultaneously.

Software markets are particularly susceptible to competition concerns because vertical integration can create ecosystem effects. A dominant firm controlling an upstream software layer may be able to disadvantage competitors operating downstream, while control over a downstream application or distribution channel may reinforce power in the upstream market.

Vertical integration is not inherently unlawful. Competition law generally distinguishes between legitimate efficiencies—such as lower transaction costs, better interoperability, security and innovation—and conduct that uses control at one level to foreclose competitors at another level.

The principal concerns include:

• tying and bundling;
• discriminatory access to APIs or interoperability;
• refusal or degradation of interoperability;
• self-preferencing;
• exclusive dealing;
• discriminatory licensing;
• raising rivals' costs;
• foreclosure through control of operating systems or app stores;
• leveraging software ecosystem power into adjacent markets;
• vertical mergers and acquisitions;
• acquisition of important complementary software;
• restrictions on portability and switching.

2. Why Vertical Integration Is Important in Software Markets

Traditional industries often have relatively clear production stages. Software ecosystems are different because several layers can be technologically interconnected.

A simplified structure may be:

Hardware → Operating System → APIs → App Store → Applications → Cloud/Platform Services → Advertising/Data

A single undertaking may participate in several of these layers.

For example, a vertically integrated software company could:

1. develop an operating system;
2. operate the app marketplace;
3. provide its own applications;
4. control essential APIs;
5. provide cloud infrastructure;
6. operate an advertising platform; and
7. collect data across the ecosystem.

This creates the possibility of leveraging market power from one layer into another.

3. Relevant Competition-Law Framework

A. Abuse of Dominance

Under Article 102 TFEU, Section 2 of the Sherman Act, and comparable national laws, vertical integration becomes particularly significant when a dominant undertaking uses its position to exclude competitors.

The important distinction is:

Vertical integration itself is generally lawful; exclusionary conduct resulting from vertical integration may be unlawful.

Authorities may investigate:

• tying;
• bundling;
• exclusive arrangements;
• discriminatory access;
• refusal to supply;
• interoperability restrictions;
• predatory pricing;
• margin squeeze;
• self-preferencing; and
• discriminatory technical design.

B. Vertical Restraints

A vertically integrated software firm can impose contractual restrictions on distributors, developers or customers.

Examples include:

• prohibiting installation of rival applications;
• requiring exclusive use of the firm's payment system;
• preventing developers from using competing stores;
• imposing parity obligations;
• restricting access to APIs;
• requiring minimum purchases;
• granting preferential technical access to affiliated products.

The competitive analysis normally depends on market power, foreclosure effects, duration, coverage, entry barriers and efficiencies.

4. Tying and Bundling

One of the most important vertical-integration risks is tying.

Suppose Firm A controls a dominant operating system and separately supplies a messaging application.

If access to the operating system or a major distribution channel is conditioned upon taking the messaging application, competitors may lose access to customers.

The classic elements examined include:

1. separate products;
2. dominance in the tying product;
3. coercion or conditioning;
4. foreclosure of competitors; and
5. absence of sufficient objective justification or efficiencies.

Software ecosystems make tying especially significant because the tying product can have enormous distribution advantages.

5. Interoperability and API Control

Vertical integration can also allow a firm to control technical interfaces.

For example:

Dominant OS → API access → Third-party applications

If the dominant firm provides its own applications with superior access to APIs while restricting rivals, the competitive harm may arise without an explicit contractual exclusion.

Potential concerns include:

• delayed API access;
• incomplete documentation;
• discriminatory technical standards;
• superior access to system data;
• degraded interoperability;
• restrictions on competing software;
• preferential treatment of affiliated services.

This is especially important in cloud computing, cybersecurity, mobile operating systems and enterprise software.

6. Six Major Case Laws

1. United States v. Microsoft Corp. — 253 F.3d 34 (D.C. Cir. 2001)

Facts

Microsoft possessed substantial power in the market for personal-computer operating systems.

The case concerned Microsoft's conduct toward competing technologies, particularly Netscape's browser and Java.

Microsoft used various contractual, technical and distribution arrangements involving computer manufacturers, Internet access providers and software developers.

Competition Issue

The central question was whether Microsoft had unlawfully maintained its operating-system monopoly through exclusionary conduct.

Decision

The D.C. Circuit upheld important findings that Microsoft had engaged in exclusionary conduct violating Section 2 of the Sherman Act, although it modified portions of the district court's judgment and remedy.

Relevance to Vertical Integration

The case demonstrates how control over one software layer can affect competition in another.

The operating system constituted a crucial distribution and technical platform. Microsoft's ability to influence OEMs, applications and middleware created opportunities for foreclosure.

Principle

Control over a critical software platform can generate leverage over complementary software markets.

2. European Commission v Microsoft — Case COMP/C-3/37.792

Facts

The European Commission investigated Microsoft's conduct involving Windows and competing work-group server operating systems and media-player software.

Microsoft possessed a dominant position in the PC operating-system market.

Competition Issues

The case involved:

• interoperability information;
• refusal to provide information necessary for interoperability;
• tying Windows with Windows Media Player.

Decision

The European Commission found infringements of EU competition law and imposed remedies, including requirements concerning interoperability information and a version of Windows without Media Player.

Vertical-Integration Significance

Microsoft simultaneously controlled the operating-system platform and competed in complementary software markets.

This created the possibility that Windows could be used to disadvantage competing server software or media players.

Principle

A dominant platform provider may have special competition-law responsibilities when its control over interoperability affects downstream competitors.

3. Google Android — Google LLC and Alphabet Inc. v European Commission, Case T-604/18

The General Court's 2022 judgment concerned Google's Android ecosystem.

Facts

Google operated several interconnected components:

• Android operating system;
• Google Play Store;
• Google Search;
• Chrome; and
• other mobile services.

The Commission identified separate but interconnected markets and examined Google's contractual arrangements with device manufacturers and mobile network operators.

Competition Issues

The investigation concerned:

• tying;
• exclusivity payments;
• anti-fragmentation obligations; and
• leveraging Android-related power into search.

Decision

The General Court largely upheld the Commission's findings, while modifying the Commission's fine.

Vertical-Integration Significance

This is one of the clearest modern examples of ecosystem-based vertical integration.

The operating system, app store, search engine and browser were complementary products. Control over one layer could therefore affect competitive conditions at another.

The Court also recognised the interconnected nature of the relevant markets and Google's strategy of promoting search through its broader ecosystem.

Principle

Competition analysis in digital ecosystems may need to consider how vertically connected products reinforce one another rather than examining each product in complete isolation.

4. Microsoft Teams and Microsoft 365 — European Commission

This matter provides a particularly direct modern example of vertical integration in enterprise software.

Facts

Microsoft supplied dominant productivity applications such as:

• Word;
• Excel;
• PowerPoint; and
• Outlook,

while also supplying Microsoft Teams as a communications and collaboration product.

The Commission's 2024 Statement of Objections preliminarily considered Microsoft's bundling of Teams with Microsoft 365/Office 365.

Competition Concern

The Commission's preliminary assessment was that customers were unable to obtain certain Microsoft 365/Office 365 suites without Teams, giving Teams a distribution advantage over competing collaboration products.

Interoperability was also relevant.

Subsequent Commitments

Microsoft subsequently agreed to commitments addressing the Commission's concerns, including:

• unbundled suites;
• pricing differences;
• interoperability measures;
• integration opportunities for competing services;
• data portability.

The commitments were agreed in 2025.

Principle

Vertical integration can create competitive concerns where a dominant productivity ecosystem gives an affiliated product an automatic distribution advantage.

5. FTC v. Microsoft/Activision Blizzard

Facts

Microsoft operated:

• Xbox;
• Game Pass;
• cloud gaming services,

while Activision Blizzard owned major game content, including highly valuable gaming franchises.

The FTC challenged Microsoft's proposed acquisition.

The FTC alleged that the transaction could enable Microsoft to disadvantage competing consoles and gaming services by controlling important content.

Competition Issue

The case illustrates vertical foreclosure through acquisition.

Microsoft was active downstream in gaming platforms and services, while Activision Blizzard was a major supplier of gaming content.

The concern was therefore:

Content ownership → gaming platform → subscription/cloud distribution

Significance

The case illustrates why competition authorities may scrutinise vertical acquisitions involving strategically important software or digital content.

Principle

A vertical acquisition may create competition concerns when an integrated firm gains control over an important input that competing platforms require.

Importantly, the FTC's allegations were contested and the legal proceedings did not establish a general rule that vertical integration itself is unlawful. The concern was about the potential competitive effects of the particular transaction.

6. Google Shopping — Google Search and Shopping, Case AT.39740

Facts

Google operated the dominant general search engine while also operating its own comparison-shopping service.

Competition Issue

The Commission examined whether Google gave preferential treatment to its own comparison-shopping service in search results while disadvantaging competing comparison-shopping services.

Decision

The European Commission found an infringement of Article 102 TFEU and imposed a substantial fine.

Vertical-Integration Significance

The case illustrates self-preferencing within a vertically integrated digital ecosystem.

Google controlled the upstream search-distribution environment while simultaneously competing downstream with comparison-shopping services.

Principle

A platform operator that also competes with businesses using its platform may have incentives and opportunities to favour its own downstream service.

7. Additional Important Case: Intel — Intel v Commission

Although not purely a software case, Intel v Commission is useful for understanding vertical foreclosure in technology markets.

Intel supplied CPUs while dealing with computer manufacturers and distributors.

The EU proceedings examined rebates and their potential exclusionary effects on competitors.

The case demonstrates that vertical commercial relationships can become problematic where incentives effectively restrict competitors' access to important customers.

The broader lesson for software markets is that exclusive or loyalty-inducing commercial arrangements may reinforce vertical integration and increase foreclosure risks.

8. Major Forms of Vertical-Integration Abuse in Software

9. Vertical Foreclosure

Vertical foreclosure can operate in two principal directions.

A. Input Foreclosure

A vertically integrated company controls an important upstream input.

Example:

Cloud infrastructure → SaaS application

The integrated firm might make the input more expensive or technically difficult for competing SaaS providers to obtain.

B. Customer Foreclosure

A vertically integrated firm controls an important downstream distribution channel.

Example:

Operating system → App store → Applications

The platform could potentially make it difficult for competing applications to reach users.

10. Raising Rivals' Costs

A vertically integrated software company may not completely exclude competitors.

Instead, it can make competing products more expensive or less effective.

Examples include:

• charging competitors for API access;
• delaying interoperability;
• imposing technical restrictions;
• limiting data access;
• reducing compatibility;
• imposing discriminatory licensing terms.

This can reduce the ability of rivals to compete even when they remain formally present in the market.

11. Data Advantages

Vertical integration can also create a significant data advantage.

Suppose a company operates:

1. an operating system;
2. an app store;
3. cloud services; and
4. advertising services.

It may obtain information from several layers of the ecosystem.

This can create competition concerns involving:

• access to commercially valuable data;
• data aggregation;
• discriminatory data access;
• preferential use of platform data;
• competitor intelligence;
• targeted advertising advantages.

The competition question is not simply whether the integrated firm possesses data, but whether its control of data creates or reinforces market power and produces exclusionary effects.

12. Vertical Mergers in Software

Vertical integration can arise organically or through acquisition.

A merger may connect:

Upstream software infrastructure + downstream application

or:

Operating system + application developer

or:

Cloud platform + SaaS provider

Authorities may examine:

Input foreclosure

Will competitors lose access to an important input?

Customer foreclosure

Will rival suppliers lose access to an important distribution channel?

Raising rivals' costs

Can the integrated company disadvantage competitors?

Information advantages

Will the merged company obtain commercially sensitive information about competitors?

Innovation effects

Could integration reduce incentives to innovate or maintain compatibility?

13. Efficiency Justifications

Vertical integration can generate substantial efficiencies.

Possible benefits include:

• better interoperability;
• improved cybersecurity;
• reduced transaction costs;
• faster innovation;
• integrated customer support;
• improved product quality;
• reduced duplication;
• better privacy controls;
• more efficient infrastructure investment.

For example, integrating an operating system with security software may allow vulnerabilities to be addressed more quickly.

Therefore, competition law generally should not treat integration itself as proof of anticompetitive conduct.

The critical question is whether the claimed efficiency requires the restrictive conduct and whether the benefits outweigh the foreclosure effects under the applicable legal test.

14. Network Effects and Vertical Integration

Software markets often exhibit strong network effects.

The value of a platform can increase as:

• more users join;
• more developers create applications;
• more complementary services become available.

This can create a feedback loop:

More users → More developers → More applications → More users

Vertical integration can reinforce that loop.

A dominant platform may therefore gain an advantage not merely from its current market share but from control over the ecosystem surrounding the platform.

15. Switching Costs

Vertical integration may also increase switching costs.

Examples include:

• proprietary file formats;
• non-portable data;
• API dependencies;
• application compatibility;
• cloud migration costs;
• subscription bundles;
• enterprise licensing arrangements.

If customers cannot easily migrate from the integrated ecosystem, competitors may face substantial barriers even if their products are technically superior.

16. Competition-Law Test

A useful analytical framework is:

Step 1 — Define the markets

Identify:

• upstream market;
• downstream market;
• complementary products;
• platform/ecosystem relationships.

Step 2 — Establish market power

Consider:

• market shares;
• entry barriers;
• network effects;
• switching costs;
• data advantages;
• interoperability;
• customer dependency.

Step 3 — Identify the vertical relationship

Determine whether the firm controls:

• an input;
• distribution;
• infrastructure;
• operating system;
• API;
• app store;
• cloud platform;
• complementary application.

Step 4 — Identify the conduct

Examples:

• tying;
• bundling;
• exclusivity;
• discriminatory access;
• self-preferencing;
• refusal to interoperate;
• discriminatory pricing.

Step 5 — Examine foreclosure

Ask:

Does the conduct materially reduce competitors' ability or incentive to compete?

Step 6 — Examine effects

Consider:

• prices;
• quality;
• innovation;
• consumer choice;
• entry;
• interoperability;
• switching.

Step 7 — Consider efficiencies

Examine whether integration creates genuine:

• security;
• innovation;
• interoperability;
• cost;
• quality

benefits.

17. Remedies

Competition authorities can employ several remedies.

Structural Remedies

In exceptional circumstances:

• divestiture;
• separation of business units;
• prohibition of acquisition.

Behavioural Remedies

More commonly:

• interoperability obligations;
• API access;
• non-discrimination;
• unbundling;
• licensing requirements;
• data portability;
• restrictions on exclusivity;
• technical access commitments.

The Microsoft Teams matter illustrates the modern importance of unbundling, interoperability and portability remedies.

18. Key Case-Law Principles

19. Conclusion

Vertical integration in software markets is a double-edged phenomenon. Integration can improve interoperability, security, innovation and efficiency, but it can also give a powerful software undertaking the ability and incentive to disadvantage competitors operating at adjacent levels.

The central competition-law concern is therefore not:

“Is the company vertically integrated?”

but rather:

“Does its control over one level of the software ecosystem enable it to foreclose, disadvantage or raise the costs of competitors at another level?”

The major cases—particularly Microsoft, Google Android, Google Shopping, Microsoft Teams/Microsoft 365, and the Microsoft/Activision merger proceedings—show how competition authorities and courts increasingly examine software markets as interconnected ecosystems rather than isolated products. The Google Android judgment expressly recognised the complementary and interconnected nature of the relevant markets within Google's ecosystem.

Thus, the principal legal concepts for studying vertical integration in software markets are leveraging, tying, bundling, self-preferencing, interoperability, foreclosure, raising rivals' costs, network effects, switching costs, data advantages and vertical merger control.