Competition Law and Antitrust Implications of Ecosystem Capability Platforms

1. Introduction

An Ecosystem Capability Platform (ECP) can be understood as a digital or technological platform that provides a common infrastructure through which multiple businesses obtain, combine, develop, or deploy capabilities such as:

computing;

data;

artificial intelligence;

payments;

identity verification;

logistics;

cloud infrastructure;

APIs;

software tools;

analytics;

distribution;

advertising;

financial services; and

specialized business functions.

Unlike a conventional marketplace, an ecosystem capability platform may not merely connect buyers and sellers. It can become an underlying capability layer on which numerous businesses depend.

For competition law, this creates an important question:

Can control over a critical capability platform be used to influence competition in the markets that depend upon it?

The principal antitrust concerns involve platform dominance, vertical leveraging, tying, self-preferencing, interoperability restrictions, access discrimination, data accumulation, exclusionary contracts, switching costs, network effects, algorithmic coordination, and acquisitions of complementary capabilities.

There is no large body of reported jurisprudence specifically using the term "ecosystem capability platform." The most relevant legal principles therefore come from cases involving dominant digital platforms, interoperability, essential facilities, tying, self-preferencing, data access and ecosystem foreclosure.

2. Structure of an Ecosystem Capability Platform

An ecosystem capability platform can be represented as:

Core platform

↓

Data + APIs + computing infrastructure

↓

Capability modules

↓

Third-party businesses

↓

Downstream products and services

For example, an AI ecosystem platform could provide:

cloud computing;

foundation models;

identity services;

payment infrastructure;

data analytics;

developer APIs;

advertising;

distribution.

A business using that ecosystem may consequently become dependent on several capabilities supplied by the same undertaking.

This creates the possibility of multi-layer market power.

3. Relevant Market Definition

Competition authorities would first need to determine the relevant market or markets.

An ecosystem capability platform could participate in several distinct markets.

A. Platform market

The market for operating the ecosystem itself.

B. Capability market

Examples:

cloud computing;

AI models;

payment processing;

digital identity;

advertising technology.

C. Downstream market

Examples:

online retail;

travel;

financial services;

logistics;

enterprise software.

D. Complementary application markets

Third parties may use the platform to provide:

analytics;

automation;

cybersecurity;

business software;

financial products.

The existence of an ecosystem does not automatically mean that all these activities constitute one relevant market.

4. Market Power Through Ecosystem Control

A company may have relatively moderate market share in an individual capability market while possessing considerable ecosystem power.

For example:

Cloud infrastructure

AI model

identity

payments

advertising

distribution

may create a competitive position stronger than the company's share in any one component suggests.

Relevant factors can include:

network effects;

economies of scope;

data advantages;

switching costs;

interoperability;

vertical integration;

user multi-homing;

technical standards;

ecosystem scale;

access to complementary products.

5. Case Law

Case 1: Microsoft Corp. v Commission

Case T-201/04, Microsoft Corp. v Commission

Microsoft is one of the foundational European competition cases for technology ecosystems.

The case concerned Microsoft's dominance in PC operating systems and its conduct concerning interoperability information and the integration of Windows Media Player.

The European Commission found that Microsoft's withholding of interoperability information restricted competing work-group server products.

Relevance to ecosystem capability platforms

An ecosystem capability platform can control:

APIs;

technical specifications;

data interfaces;

authentication systems;

interoperability protocols.

If competing capability providers cannot effectively operate without access to those interfaces, restrictions can potentially produce exclusionary effects.

The Microsoft principle therefore demonstrates that technical interoperability can itself become a competition-law asset.

6. Case 2: Bronner v Mediaprint

Case C-7/97, Oscar Bronner GmbH & Co. KG v Mediaprint

Bronner is a leading refusal-to-supply and essential-facilities case.

The Court adopted a demanding standard before requiring a dominant undertaking to provide access to infrastructure.

The relevant considerations included whether:

the facility was indispensable;

duplication was impossible or economically unreasonable;

refusal would eliminate effective competition; and

there was no objective justification.

Application

Suppose an ecosystem capability platform operates the only commercially viable:

authentication infrastructure;

enterprise API;

specialized data network;

cloud environment.

A competitor cannot automatically demand access merely because access would be commercially advantageous.

Bronner remains important because competition law should not convert every successful platform into a mandatory infrastructure provider.

7. Case 3: IMS Health v NDC Health

Case C-418/01, IMS Health GmbH & Co. OHG v NDC Health GmbH & Co. KG

IMS Health involved a proprietary pharmaceutical-sales database and the circumstances under which refusal to license intellectual property could amount to abuse of dominance.

The Court emphasized the exceptional circumstances required for compulsory access.

Ecosystem relevance

An ecosystem capability platform may possess:

proprietary datasets;

AI training data;

specialized analytical models;

industry-specific databases;

proprietary technical architecture.

A competitor's request for access to such resources would need to be examined under the established refusal-to-supply framework.

The case therefore helps distinguish:

valuable competitive asset

from

legally indispensable input.

That distinction is central to ecosystem-platform regulation.

8. Case 4: Tetra Pak v Commission

Tetra Pak International SA v Commission, Case T-83/91

Tetra Pak is important for understanding how dominance in one market can potentially be leveraged into a related market.

The case concerned interconnected markets involving packaging equipment and packaging materials.

Application to ecosystem capability platforms

An ecosystem platform may operate simultaneously in:

infrastructure;

software;

analytics;

distribution;

complementary services.

A dominant provider might attempt to leverage its position in one capability into another.

For example:

dominant cloud platform
→ requires use of its AI services
→ requires use of its identity system
→ restricts competing AI providers.

The legal analysis would examine whether the integration constitutes unlawful tying, leveraging or foreclosure rather than assuming that integration itself is unlawful.

9. Case 5: Google Android

Google and Alphabet v Commission, Case T-604/18

Google Android is highly relevant to ecosystem competition.

The case concerned Google's conduct involving Android, Google Search, Google Play, Chrome, device manufacturers and mobile-network operators.

The General Court examined several forms of conduct involving:

tying;

exclusivity-related arrangements;

anti-fragmentation obligations.

Ecosystem relevance

The case illustrates how competition law can examine a portfolio of interconnected products rather than treating each digital service in isolation.

An ecosystem capability platform could similarly connect:

operating system;

cloud;

AI;

payments;

advertising;

identity;

app distribution.

The competitive issue becomes whether control over one layer can restrict competitors at another layer.

10. Case 6: Google Shopping

Google and Alphabet v Commission, Case T-612/17

Google Shopping concerned preferential positioning of Google's own comparison-shopping service within Google's general search results.

The case is significant for understanding self-preferencing in vertically integrated digital ecosystems.

Application

Imagine an ecosystem capability platform providing:

infrastructure to third-party businesses;

a marketplace for those businesses;

its own competing products.

The platform could theoretically favor its own products by providing:

better ranking;

superior access to data;

preferential APIs;

better technical functionality;

lower fees;

preferential recommendations.

The Google Shopping litigation demonstrates why a platform's dual role as infrastructure provider and downstream competitor can raise competition-law issues.

11. Case 7: Android Auto

Alphabet Inc. and Others v Autorità Garante della Concorrenza e del Mercato (AGCM), Case C-233/23

Android Auto is particularly relevant to ecosystem capability platforms because it concerns interoperability.

The Court of Justice considered a dominant platform's refusal to make its system interoperable with a third-party application.

The Court recognized that competition analysis can take account of potential competition in a downstream market that is still developing.

Ecosystem relevance

An ecosystem capability platform may provide an environment in which third parties need access to:

APIs;

hardware functions;

authentication;

operating-system functionality;

technical interfaces.

If the platform refuses interoperability, the result could be exclusion of emerging downstream competitors.

The Android Auto reasoning is therefore highly relevant to nascent ecosystem capabilities.

12. Case 8: Clearstream Banking AG v Commission

Case T-301/04, Clearstream Banking AG v Commission

Clearstream concerned access to infrastructure and the conduct of a dominant undertaking providing essential financial-market infrastructure.

The case provides useful guidance concerning:

access restrictions;

discriminatory treatment;

infrastructure dependency;

dominant-platform obligations.

Ecosystem application

Where an ecosystem capability platform becomes an important infrastructure layer for downstream businesses, competition authorities may examine whether it:

refuses access;

discriminates among users;

imposes unreasonable conditions;

selectively provides technical capabilities.

The case is particularly useful for analyzing platforms operating as market infrastructure.

13. Tying and Bundling

Ecosystem capability platforms are particularly susceptible to tying.

A dominant platform could potentially condition access to one capability upon acceptance of another.

Examples:

Cloud + AI

A customer purchasing cloud services is required to use the provider's AI model.

Identity + payments

Access to identity services requires adoption of the platform's payment service.

Operating system + advertising

Platform access is conditional upon using the provider's advertising technology.

Marketplace + logistics

Businesses using the marketplace must use the platform's logistics service.

The relevant competition-law questions include:

Are the products distinct?

Is the undertaking dominant?

Is there coercion?

Is competition foreclosed?

What proportion of the market is affected?

Are there objective efficiencies?

14. Self-Preferencing

Self-preferencing becomes particularly important where the platform is both:

infrastructure provider

and

competitor.

Consider:

Ecosystem platform
↓
provides AI APIs to startups
↓
operates its own AI applications
↓
controls rankings and access
↓
favors its own applications.

Potential discriminatory mechanisms include:

search ranking;

recommendation systems;

API quotas;

processing priority;

pricing;

data access;

visibility;

certification.

This resembles the structural concern examined in Google Shopping.

15. Access Discrimination

An ecosystem platform can discriminate through technical or commercial mechanisms.

For example:

The discrimination does not necessarily have to be an explicit contractual prohibition.

It may be embedded in:

algorithms;

technical architecture;

pricing;

interface design.

16. Data Advantages

Data is one of the most significant competitive assets of an ecosystem platform.

A platform serving millions of businesses may collect information concerning:

customer behavior;

transaction patterns;

demand;

prices;

product performance;

advertising conversion;

logistics;

business operations.

The platform may then use this information to improve its own competing services.

This can generate a feedback loop:

More users

↓

More data

↓

Better capability

↓

Better service

↓

More users

Such feedback loops can strengthen market power and increase entry barriers.

However, data superiority by itself is not equivalent to an antitrust violation. The competition analysis must focus on the conduct through which the data advantage is acquired or exploited.

17. Ecosystem Lock-In

Ecosystem platforms can create significant switching costs.

A business may integrate:

APIs;

databases;

cloud infrastructure;

authentication;

payment systems;

AI models;

employee workflows.

After several years, moving to another ecosystem may become expensive.

This can reduce customer mobility.

Potential competition concerns arise where a dominant platform deliberately creates unnecessary switching barriers through:

restrictive data-export mechanisms;

incompatible formats;

contractual restrictions;

technical limitations;

excessive termination costs.

18. Interoperability

Interoperability is one of the most important competition issues.

A capability platform can either:

Facilitate interoperability

creating opportunities for:

innovation;

entry;

multi-homing;

competition.

Or:

Restrict interoperability

creating:

lock-in;

switching costs;

dependency;

foreclosure.

Interoperability restrictions can concern:

APIs;

data formats;

authentication;

payment interfaces;

operating-system functions;

cloud portability.

Microsoft and Android Auto provide particularly useful precedents.

19. Algorithmic Coordination

Ecosystem capability platforms may also facilitate coordination among competitors.

Suppose several competing businesses use the same platform to determine:

prices;

production;

inventory;

delivery charges.

If the platform's algorithms incorporate competitors' commercially sensitive information, competition concerns may arise.

Potentially problematic situations could involve:

direct information exchange;

coordinated pricing algorithms;

common pricing rules;

deliberate use of the platform to facilitate coordination.

The fact that an algorithm is technologically sophisticated does not remove ordinary competition-law principles.

20. Network Effects

Ecosystem capability platforms often benefit from direct and indirect network effects.

Direct network effect

More users make the platform more valuable to other users.

Indirect network effect

More businesses attract more complementary service providers, which attracts more businesses.

For example:

More developers

→ more applications

→ more customers

→ more developers.

Network effects can produce substantial economies of scale.

They can also make markets tip toward one or a small number of ecosystems.

21. Vertical Foreclosure

An ecosystem capability platform can potentially foreclose competitors upstream or downstream.

Input foreclosure

A dominant platform denies rivals access to:

data;

APIs;

infrastructure;

distribution.

Customer foreclosure

The platform prevents customers from using rival capabilities.

Downstream foreclosure

The platform favors its own applications.

Upstream foreclosure

The platform acquires or controls important suppliers.

22. Exclusivity

Exclusive contracts can be especially significant where network effects already exist.

For example:

A dominant ecosystem requires major software developers to provide their applications exclusively through its platform.

Potential effects include:

reduced multi-homing;

reduced rival platform attractiveness;

higher entry barriers;

reduced distribution opportunities.

The legal analysis would depend on:

duration;

market coverage;

dominance;

foreclosure effects;

contractual alternatives;

efficiencies.

23. Merger-Control Implications

Ecosystem capability platforms raise distinctive merger concerns.

A platform may acquire:

an AI startup;

a cybersecurity company;

a payment provider;

an identity provider;

an analytics platform.

Even where the target has limited current revenue, authorities may examine whether the acquisition eliminates a potential competitive constraint.

Relevant theories include:

Data consolidation

Combining unique datasets.

Capability consolidation

Combining complementary technologies.

Vertical foreclosure

Restricting rivals' access to the acquired capability.

Ecosystem strengthening

Making the platform substantially harder to compete against.

Nascent competitor acquisition

Removing an emerging alternative before it develops.

24. Essential-Facilities Concerns

Not every ecosystem capability is an essential facility.

The demanding principles in Bronner and IMS Health remain important.

A platform is more likely to raise essential-facilities concerns where:

competitors cannot realistically duplicate it;

alternatives are unavailable;

access is technically indispensable;

refusal eliminates effective competition;

access can reasonably be provided.

This prevents competition law from imposing excessive access obligations on ordinary successful businesses.

25. Objective Justification

A platform may have legitimate reasons for restricting access.

Examples include:

cybersecurity;

privacy;

intellectual-property protection;

system stability;

fraud prevention;

technical limitations;

safety;

regulatory requirements.

The critical question is whether the restriction is:

necessary and proportionate

to the legitimate objective.

A dominant platform should not necessarily be required to sacrifice security or system integrity merely to facilitate competition.

26. Remedies

Where anticompetitive conduct is established, possible remedies could include:

Structural remedies

separation of platform and downstream operations;

divestiture in exceptional circumstances.

Behavioral remedies

non-discriminatory access;

interoperability;

API access;

data portability;

transparency requirements;

restrictions on exclusivity.

Technical remedies

open APIs;

standardized interfaces;

interoperability protocols;

export functionality.

Data-related remedies

data portability;

restrictions on combining datasets;

access to particular datasets under defined conditions.

27. Indian Competition-Law Perspective

Under the Competition Act, 2002, ecosystem capability platforms could potentially raise issues under:

Section 3

Agreements that cause or are likely to cause appreciable adverse effect on competition.

Potential examples include:

exclusivity;

market-sharing;

restrictive distribution arrangements;

coordinated platform conduct.

Section 4

Abuse of dominant position.

Potential theories include:

unfair or discriminatory conditions;

denial of market access;

tying;

leveraging;

discriminatory access;

exclusionary conduct.

Sections 5 and 6

Combinations involving acquisition of:

emerging AI platforms;

cloud technologies;

data-intensive businesses;

complementary capability providers.

The CCI would need to examine the actual competitive structure rather than treating ecosystem size alone as proof of dominance.

28. Major Antitrust Issues at a Glance

29. Comparative Case-Law Principles

The principal lessons from the cases can be summarized as follows:

30. Conclusion

Ecosystem capability platforms represent a particularly important development in competition law because they combine infrastructure, data, software, algorithms and complementary services into an interconnected competitive environment.

The central competition concern is not simply that a company operates a large ecosystem. Large ecosystems can generate substantial efficiencies and consumer benefits.

The critical legal question is whether an undertaking with substantial market power uses control over one capability to foreclose competition in another market or to make competing ecosystems unable to operate effectively.

The most significant areas of antitrust scrutiny are therefore likely to be:

interoperability restrictions;

API and technical-access discrimination;

tying and bundling;

self-preferencing;

exclusive ecosystem arrangements;

data accumulation and data-based foreclosure;

switching costs and ecosystem lock-in;

refusal to supply critical capabilities;

algorithmic coordination;

vertical leveraging; and

acquisitions of complementary or nascent competitors.

The jurisprudence of Microsoft, Bronner, IMS Health, Tetra Pak, Google Android, Google Shopping, Android Auto and Clearstream provides a strong conceptual framework for analyzing these issues. The most important lesson is that competition law increasingly has to examine the architecture of an ecosystem, rather than looking at individual products or services in complete isolation.