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.
Already decided on Besu? Follow our step-by-step tutorial to create a Besu network in 2 minutes. Not sure whether Besu or Fabric fits your use case? Read our Hyperledger Fabric vs Besu comparison.
What Are the Products Available to Deploy Hyperledger Besu?
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.
What Are the Managed BaaS Platforms for Besu?
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
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
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
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
- Terraform provider for declarative infrastructure-as-code
- 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.
What Are the Kubernetes and Infrastructure-as-Code Tools for Besu?
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
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
- Multi-protocol support (5 blockchain platforms)
- Production-tested with Ansible automation
Limitations:
- Steep learning curve — requires Ansible, Helm, Flux, and Kubernetes expertise
- Setup takes days, not minutes
- Complex dependency chain (Ansible + Helm + Flux + K8s)
- 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.
Consensys Quorum-Kubernetes
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
- Cloud-native key management (AWS Secrets Manager, Azure Key Vault)
- IAM integration for pod-level identity and access control
- Prometheus metrics and Grafana dashboards included
- BlockScout explorer integration
Limitations:
- Requires existing Kubernetes cluster and Helm expertise
- Production support officially limited to AWS and Azure (as of 2026)
- No built-in automation — charts must be managed manually or integrated with CI/CD
- NAT for K8s deprecated in Besu v24.12.0 (requires
--nat-method=NONE)
Best for: Teams running AWS EKS or Azure AKS that want the official Consensys Helm charts with cloud-native secrets and IAM integration.
Besu Kubernetes Operator
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.
ChainLaunch Terraform Provider
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 planandterraform 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.
How Do You Deploy Besu Manually?
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.
Docker Compose
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.
Binary Installation
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.
How Do You Choose the Right Besu Deployment Product?
The right tool depends on three factors: your team's DevOps maturity, your infrastructure preferences, and your timeline to production.
| Team Profile | Recommended Product | Why |
|---|---|---|
| Small team, no DevOps | ChainLaunch or Kaleido | Managed platforms handle infrastructure complexity |
| Enterprise with compliance needs | Kaleido or Zeeve | SOC 2, ISO 27001 certifications |
| Platform engineering team | Hyperledger Bevel | GitOps-native, multi-protocol automation |
| AWS/Azure Kubernetes team | Quorum-Kubernetes | Official Consensys charts with cloud-native integrations |
| Terraform-first organization | ChainLaunch Terraform | IaC workflow with terraform plan/apply |
| Developer/POC | Docker Compose | Fastest local setup, no infrastructure needed |
| Multi-cloud consortium | Zeeve | Broadest cloud provider support |
Decision Flowchart
- 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.
How Do the Products Compare on Features?
| Feature | Kaleido | Zeeve | ChainLaunch | Bevel | Quorum-K8s | Besu Operator |
|---|---|---|---|---|---|---|
| QBFT support | Yes | Yes | Yes | Yes | Yes | Yes |
| IBFT 2.0 support | Yes | Yes | Yes | Yes | Yes | Yes |
| Clique support | Yes | Unknown | No | Yes | Yes | Yes |
| Key management | Platform-managed | Platform-managed | Database + KMS | Manual / Vault | AWS SM, Azure KV | Manual |
| Monitoring | Built-in | Built-in | Built-in | Prometheus + Grafana | Prometheus + Grafana | Manual |
| Terraform support | No | No | Yes | No | No | No |
| Self-hosted option | No | No | Yes | Yes | Yes | Yes |
| Multi-protocol | Besu, Fabric, Corda | Besu, Fabric | Besu, Fabric | 5 protocols | Besu, GoQuorum | Besu only |
| Free tier | 60-day trial | Contact sales | Unlimited, no time limit | Open source | Open source | Open source |
| Compliance certs | SOC 2, ISO 27001 | SOC 2, ISO 27001, GDPR | Not yet | N/A | N/A | N/A |
What Consensus Algorithms Does Each Product Support for Besu?
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.
For a deeper dive into QBFT configuration, see our QBFT consensus guide.
Does AWS Offer a Managed Hyperledger Besu Service?
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.
FAQ
What is the easiest way to deploy Hyperledger Besu?
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.
Can I deploy Besu without Kubernetes?
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.
What is the cost of managed Besu deployment?
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.
What is the difference between Besu and GoQuorum for deployment?
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.
Which Besu deployment tool supports the most cloud providers?
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.