Comparing IBM and Microsoft Blockchain-as-a-Service Platforms: Governance, Protocol Choices, and Market Implications

This article, originally published in CoinDesk Weekly, uses a tennis tournament metaphor to frame the competition between IBM and Microsoft as they build commercial blockchain‑as‑a‑service (BaaS) platforms.

Both companies are leveraging their cloud offerings to support enterprise blockchain applications, positioning themselves as market leaders in a rapidly evolving field.

IBM recently introduced its first commercial IBM Blockchain offering, a suite of cloud services that help customers create and manage blockchain networks.

Microsoft has integrated a BaaS module into its Azure cloud platform since 2015, making the service broadly available to all Azure users as of last year.

While the two platforms appear similar—modular, cloud‑based, built on open‑source code, and supported by large ecosystems—significant underlying differences exist.

Microsoft’s BaaS shows a clear preference for the Ethereum protocol, having launched its service around Ethereum in 2015.

Microsoft’s partnerships are largely startup‑focused, and the company is a founding member of the Enterprise Ethereum Alliance (EEA), which explores commercial uses of public blockchains.

In contrast, IBM has largely stayed away from public blockchains; its BaaS is built on the Hyperledger Fabric codebase, to which IBM contributed extensively.

The distinction goes deeper than public versus private blockchains; both firms develop private applications on open‑source protocols.

Different Focus

The primary difference lies in governance.

Ethereum is governed by the Ethereum Foundation, of which Microsoft is not a member, creating a risk that the foundation could change the underlying code without Microsoft’s input.

Hyperledger’s codebase is overseen by a steering committee that includes IBM as a key member, while Microsoft does not belong to the Hyperledger consortium.

Public interaction levels also differ: bugs in Ethereum become public events that can shake confidence in enterprise systems built on it, whereas issues in Fabric are typically resolved quickly within the consortium.

Proponents of public blockchains cite a broad developer base and interoperability potential as advantages.

Like a tightly contested tennis match, the competition between IBM and Microsoft is ongoing, and a clear winner may not emerge soon.

For decades IBM and Microsoft have co‑existed as IT leaders, continuously adapting strategies and seizing new opportunities; agility remains crucial in emerging technology domains, and market size and entry barriers are significant factors.

In the blockchain arena, the game is just beginning.