Blockchain-As-a-Service (BaaS)

Blockchain-as-a-Service (BaaS) is a cloud computing model in which a provider sets up, hosts and maintains blockchain infrastructure on behalf of its customers. Businesses use the provider's tools to create networks, deploy smart contracts and connect applications, paying a subscription or usage fee instead of buying servers and hiring specialists to run nodes. The model mirrors software-as-a-service and platform-as-a-service offerings for other technologies.

BaaS first grew in the late 2010s, when large technology companies offered managed versions of enterprise frameworks such as Hyperledger Fabric and Ethereum-based networks for consortiums of banks, insurers and supply chain firms. Today the term also covers node and API providers that give developers access to public blockchains, as well as platforms for issuing tokens and stablecoins. It should not be confused with Banking-as-a-Service, which shares the same abbreviation but refers to licensed banks offering banking products through partners.

Think of renting a fully equipped commercial kitchen rather than building your own restaurant kitchen. The landlord provides the ovens, maintains the gas and electricity and fixes broken equipment, while you bring the recipes and cook. You can start quickly and pay as you go, but you depend on the landlord's rules and reliability.

Blockchain-as-a-Service works the same way. A cloud company runs the computers, software and security needed for a blockchain, and a business plugs its own application into them. The business does not need a team of blockchain engineers to keep nodes running, but it trusts the provider to keep the service up and to handle data properly.

A typical BaaS offering includes:

• Network deployment. Templates to launch a private or consortium blockchain, or to join an existing one, with a few configuration choices.
• Managed nodes. The provider runs validating or full nodes, applies software updates and monitors performance.
• Identity and access. Tools to manage members, permissions and certificates, important for permissioned blockchains.
• Developer tools. Software kits, dashboards and an API for deploying contracts, reading data and connecting to existing systems.
• Key management. Secure storage of signing keys, sometimes using a hardware security module.

For public blockchains, BaaS providers often focus on node access, letting applications read and write data to networks such as Ethereum through hosted endpoints instead of running their own full nodes.

Microsoft launched blockchain services on its Azure cloud in 2015 and later a managed Azure Blockchain Service, which it retired in 2021. Amazon Web Services introduced Amazon Managed Blockchain in 2019, supporting Hyperledger Fabric and access to Ethereum, and IBM built a blockchain platform around Hyperledger Fabric, used in projects such as trade finance and food supply chains. Oracle, SAP and several specialist firms also offered services. The first wave of enterprise projects slowed after 2020, as many consortium pilots failed to reach production. Since then, demand has shifted towards infrastructure for public chains, tokenization and stablecoin issuance, with providers offering node access, wallets, custody connections and compliance tools for banks and payment companies.

Businesses have used BaaS for:

• Trade and supply chains. Shared records of shipments, documents and certifications among trading partners, linked to trade finance.
• Financial services. Settlement experiments, tokenization of assets, tokenized deposits and internal ledgers.
• Identity and credentials. Verifiable records of certificates and licences.
• Loyalty and payments. Programmes that issue tokens to customers or move value between partners.
• Web3 applications. Start-ups building decentralized applications rely on hosted nodes and APIs to reach public chains.

BaaS reduces up-front cost, shortens development time and gives access to specialist skills. It lets organisations experiment with distributed ledger technology without committing to infrastructure. However, it also introduces trade-offs:

• Centralization. If a single cloud provider runs most nodes, the network depends on that provider, which can undermine the point of a shared ledger.
• Vendor lock-in. Proprietary tools may make it hard to move to another provider.
• Service retirement. As the Azure case showed, providers can withdraw services, forcing customers to migrate.
• Outages. Several public blockchain applications have stopped working when a major node provider had an outage.
• Data and compliance. Firms must consider where data is stored, who can access it and how it fits rules on data protection and outsourcing.

Regulated institutions using BaaS usually treat it as a critical third-party service, applying outsourcing, resilience and vendor risk management controls. Many also run some nodes themselves to reduce reliance on any single provider.