8 Besu Deployment Tools Tested: One Deploys in 5 Min, One Took 40 Hours
Written by David Viejo
TL;DR: There are 8 major products to deploy Hyperledger Besu in 2026. Managed BaaS platforms (Kaleido, Zeeve, ChainLaunch) handle provisioning and monitoring for you. Kubernetes automation tools (Hyperledger Bevel, Quorum-Kubernetes Helm charts, Besu Operator) give DevOps teams full control. ChainLaunch also offers a Terraform provider for infrastructure-as-code workflows. Manual deployment via Docker or binaries remains an option for simple setups.
Choosing how to deploy Hyperledger Besu is one of the first decisions enterprise teams face when building on Ethereum-compatible blockchain infrastructure. The wrong choice can mean weeks of manual configuration, unexpected cloud bills, or vendor lock-in that limits your architecture later.
This guide compares every product available for deploying Besu — from fully managed platforms to self-hosted Kubernetes tools — so you can pick the right approach for your team's size, budget, and DevOps maturity.
There are eight products for deploying Hyperledger Besu, falling into three categories: managed BaaS platforms that handle infrastructure for you, Kubernetes-based automation tools for self-hosted deployments, and manual methods using Docker or binaries directly.
Product
Category
Deployment Time
Cloud Support
Open Source
Kaleido
Managed BaaS
30-60 min
AWS, Azure
No
Zeeve
Managed BaaS
Minutes
AWS, Azure, GCP, DO
No
ChainLaunch
Managed + Self-hosted
Under 5 min
Any VPS / bare metal
Yes (core)
Hyperledger Bevel
Kubernetes automation
Hours-days
Any K8s cluster
Yes
Quorum-Kubernetes
Helm charts
Hours
AWS, Azure, GCP, IBM
Yes
Besu Operator
Kubernetes operator
Hours
Any K8s cluster
Yes
Docker Compose
Manual
30-60 min
Any
Yes (Besu itself)
Binary installation
Manual
1-2 hours
Any
Yes (Besu itself)
Each product targets different team profiles. Managed platforms suit teams that want to focus on application development. Kubernetes tools suit DevOps-heavy organizations that need full infrastructure control. Manual methods work for development environments and proof-of-concept deployments.
Free resource
5 QBFT Settings That Make or Break Your Besu Network
Genesis config template + validator key setup guide. Includes the exact block time, epoch length, and gas settings we use for enterprise Besu deployments.
Managed Blockchain-as-a-Service platforms handle node provisioning, monitoring, key management, and upgrades. They trade infrastructure control for faster deployment and lower operational overhead.
Kaleido is the only enterprise maintainer for Hyperledger Besu, with team members who are active maintainers of the Besu codebase. They have provisioned over 30,000 Ethereum nodes for enterprises across multi-region, multi-cloud deployments. Kaleido supports both Besu and GoQuorum (via ConsenSys Quorum), and integrates with their broader Digital Asset and Web3 Middleware products.
Strengths:
Direct Besu maintainer expertise — bug fixes and patches come from the same team
Multi-protocol support (Besu, Fabric, Corda, Polygon Edge)
Built-in token, document, and DeFi services alongside node infrastructure
SOC 2 Type 2 and ISO 27001 compliant
Limitations:
Pricing starts at $0.15/hr per node ($110+/month per node on Developer plan)
No Terraform provider for infrastructure-as-code workflows
Starter tier limited to 2 nodes and 60 days
No self-hosted option — fully SaaS
Best for: Enterprises that want a single vendor for Besu nodes plus middleware services (token APIs, document notarization, DeFi building blocks), and teams that value having Besu maintainers on call.
Zeeve is a Hyperledger Foundation member that offers Besu Infrastructure-as-a-Service with one-click deployment, 24/7 monitoring, and enterprise SLA. They support deployment across AWS, Azure, GCP, Digital Ocean, and private clouds, making them one of the most cloud-flexible managed providers.
Strengths:
Broadest cloud provider support (5+ clouds including private cloud)
ISO 27001, SOC 2 Type 2, and GDPR compliant
Multi-cloud network topology support
Supports both Fabric and Besu with unified management
Limitations:
Pricing not publicly disclosed — requires contacting sales
No open-source self-hosted option
No Terraform or IaC integration documented
Best for: Enterprise consortiums that need to span multiple cloud providers or deploy on private infrastructure, and organizations in regulated industries requiring compliance certifications.
ChainLaunch provides a unified control plane for deploying and managing Besu networks, with support for both managed and self-hosted deployment models. It provisions Besu networks with QBFT or IBFT 2.0 consensus in under 5 minutes, handling validator key generation, genesis block creation, and node networking automatically.
Strengths:
Under 5 minutes to a running 4-node Besu network
Free tier with unlimited nodes and no time limit
Self-hosted option — runs on any VPS or bare metal server
AI-assisted smart contract development (Pro edition)
Supports both Besu and Fabric from a single platform
Limitations:
Newer platform with a smaller community than Kaleido or Zeeve
Enterprise features (RBAC, SSO, federation) require Pro license
No SOC 2 / ISO 27001 certification yet
Best for: Teams that want infrastructure-as-code workflows with Terraform, organizations that need a self-hosted option, and developers who want a free tier without node or time limits. Read the full cost comparison with Kaleido and Kubernetes.
Self-hosted Kubernetes tools give teams full control over their Besu infrastructure. They require more DevOps expertise but avoid vendor lock-in and allow custom configurations that managed platforms may not support.
Hyperledger Bevel is an automation framework maintained by the Linux Foundation that deploys production-grade blockchain networks on Kubernetes. It uses Ansible playbooks and Helm charts with Flux GitOps to provision and manage Besu nodes, and supports five blockchain platforms: Besu, Fabric, Indy, Corda, and GoQuorum.
Strengths:
Official Hyperledger project with Linux Foundation governance
GitOps-native with Flux CD for declarative state management
Limited real-time monitoring compared to managed platforms
Best for: Platform engineering teams already running Kubernetes clusters with GitOps workflows, and organizations that need to deploy multiple blockchain protocols from a single automation framework.
The Quorum-Kubernetes repository provides official Helm charts from Consensys for deploying Besu and GoQuorum on Kubernetes. It supports cloud-native integrations including AWS Secrets Manager, Azure Key Vault, and IAM-based pod identity.
Strengths:
Official Consensys-maintained charts — closest to upstream Besu development
The Besu Operator is a Hyperledger Labs project that provides a Kubernetes operator pattern for managing Besu networks. Instead of Helm charts, it uses Custom Resource Definitions (CRDs) that let you declare your desired Besu network state and the operator reconciles it automatically.
Strengths:
Kubernetes-native operator pattern with CRDs
Automatic reconciliation — the operator manages network state
Simpler than Helm for teams familiar with Kubernetes operators
Foundation for building custom operators for other Hyperledger projects
Limitations:
Hyperledger Labs project (not a full Hyperledger project) — smaller community
Less mature than Quorum-Kubernetes or Bevel
Limited documentation compared to alternatives
Fewer cloud-native integrations
Best for: Teams that prefer the Kubernetes operator pattern over Helm-based deployments, and organizations already using operators for other infrastructure components.
The ChainLaunch Terraform provider enables declarative Besu infrastructure using HashiCorp Terraform. It manages the full lifecycle — organizations, nodes, networks, keys, and chaincode — through standard Terraform resources and data sources.
Strengths:
Full infrastructure-as-code with terraform plan and terraform apply
Integrates with existing Terraform workflows and CI/CD pipelines
Manages Besu and Fabric resources from a single provider
State management, drift detection, and dependency ordering built in
Limitations:
Requires a ChainLaunch instance as the backend
Terraform expertise needed
Newer provider — smaller ecosystem than cloud-native Terraform providers
Best for: Infrastructure teams already using Terraform for cloud provisioning who want to add blockchain networks to their IaC workflow without a separate management tool.
Free resource
5 QBFT Settings That Make or Break Your Besu Network
Genesis config template + validator key setup guide. Includes the exact block time, epoch length, and gas settings we use for enterprise Besu deployments.
Manual deployment methods use Besu's open-source binaries or Docker images directly. They offer maximum flexibility but require the most hands-on configuration and ongoing maintenance.
Besu provides official Docker images that you can orchestrate with Docker Compose for development and small-scale deployments. A typical setup includes a genesis file, validator keys, and a docker-compose.yml that defines each node's configuration, ports, and volume mounts.
Best for: Local development, proof-of-concept testing, and CI/CD pipeline testing environments.
Installing Besu from pre-built binaries or building from source gives full control over the runtime environment. You configure each node individually with command-line flags or configuration files, manage keys manually, and set up your own monitoring stack.
Best for: Learning Besu internals, custom deployments on non-containerized infrastructure, and air-gapped environments.
Do you need a managed service? Yes → Choose between Kaleido (middleware ecosystem), Zeeve (multi-cloud compliance), or ChainLaunch (self-hosted + Terraform).
Do you already run Kubernetes? Yes → Choose between Bevel (GitOps), Quorum-Kubernetes (Consensys charts), or Besu Operator (CRD pattern).
Do you use Terraform? Yes → ChainLaunch Terraform provider integrates blockchain into existing IaC workflows.
Is this for development only? Yes → Docker Compose is the fastest path.
All major deployment products support QBFT and IBFT 2.0, the two primary consensus algorithms for enterprise Besu networks. QBFT is the recommended consensus algorithm for new Besu deployments — it improves on IBFT 2.0 with better liveness guarantees during validator changes and a more formal specification. IBFT 2.0 remains supported for backward compatibility. Clique, a simpler proof-of-authority algorithm, is available in most self-hosted tools but is generally not recommended for production due to its lower fault tolerance.
No. AWS Managed Blockchain supports Hyperledger Fabric and Ethereum (public network access), but does not offer managed Hyperledger Besu deployments as of March 2026. You can deploy Besu on AWS infrastructure using EKS with the Quorum-Kubernetes Helm charts, Bevel, or ChainLaunch, but AWS does not provide a Besu-specific managed service. The same applies to Azure and GCP — neither offers a dedicated Besu managed service.
The easiest way is a managed BaaS platform like ChainLaunch (under 5 minutes, free tier) or Kaleido (30-60 minutes). Both handle genesis block creation, validator key generation, and node networking automatically, eliminating manual configuration.
Yes. ChainLaunch runs on any VPS or bare metal server without Kubernetes. Docker Compose works for local development. Binary installation works on any Linux or macOS machine. Kubernetes is only required if you choose Bevel, Quorum-Kubernetes, or the Besu Operator.
Costs range from free (ChainLaunch free tier) to $438+/month (Kaleido Developer plan for 4 nodes). Self-hosted tools like Bevel and Quorum-Kubernetes are free but require Kubernetes infrastructure ($300-800/month on cloud) plus DevOps engineering time. See our full cost comparison.
Besu is written in Java and is actively maintained as a Linux Foundation project. GoQuorum, written in Go, was deprecated by Consensys in 2023. For new enterprise Ethereum deployments, Besu is the recommended client. The Quorum-Kubernetes Helm charts support both, but new projects should use Besu.
Zeeve supports the most cloud providers out of the box: AWS, Azure, GCP, Digital Ocean, and private cloud. ChainLaunch runs on any VPS or bare metal, giving it the broadest infrastructure flexibility. Quorum-Kubernetes officially supports AWS, Azure, GCP, and IBM for production deployments.
Free resource
5 QBFT Settings That Make or Break Your Besu Network
Genesis config template + validator key setup guide. Includes the exact block time, epoch length, and gas settings we use for enterprise Besu deployments.
