Hyperledger Besu Networks
Deploy Hyperledger Besu Networks in Minutes
Launch enterprise-grade Hyperledger Besu networks with EVM compatibility, AI-powered smart contract development, and enterprise privacy features. Deploy public or private Ethereum-compatible networks instantly.
EVM Compatibility
Your Ethereum toolchain, on a private network
Besu is a full Ethereum client. Every tool your team already knows works without modification — the only difference is you control who participates.
Works unchanged on Besu
Zero code changes needed
// Same deployment script works on mainnet and Besu
const provider = new ethers.JsonRpcProvider(
"https://your-besu.chainlaunch.dev"
);
const factory = new ContractFactory(abi, bytecode, signer);
const contract = await factory.deploy();
await contract.waitForDeployment();Point JsonRpcProvider at your ChainLaunch Besu endpoint — nothing else changes.
What Besu adds over public Ethereum
- Deterministic finality — no reorgs, BFT consensus guarantees
- Permissioned participant list — only approved addresses can transact
- Zero gas costs — no ETH required for internal networks
- Private transactions via Tessera — payload never touches the main chain
- On-chain access control via smart-contract permissioning
- No public mempool — transactions stay inside your network
Migrate existing contracts, tests, and scripts as-is. Add permissioning and privacy on top.
How Besu Works
Deploy Enterprise Hyperledger Besu Networks Effortlessly
# Create Besu testnet with IBFT 2.0 consensus
export CHAINLAUNCH_API_URL=http://localhost:8100/api/v1
chainlaunch testnet besu \
--name enterprise-besu \
--consensus ibft2 \
--validators 4 \
--bootnodes 2 \
--enable-privacy \
--network-id 1337 \
--gas-limit 10000000
# Network ready with:
# - 4 Validator nodes (IBFT 2.0)
# - 2 Bootnode nodes
# - Privacy features enabled
# - EVM-compatible network
# - Custom network ID and gas limitBesu Features
Enterprise Ethereum without the enterprise overhead
QBFT consensus, Tessera private transactions, and on-chain permissioning are what separate Besu from running a public Ethereum node. ChainLaunch configures and manages all three.
QBFT Consensus & Validator Management
QBFT (Quorum Byzantine Fault Tolerant) provides deterministic finality — once a block is committed, it never reverts. The validator set governs who produces blocks. Adding or removing a validator requires a proposal-and-vote round among existing validators, ensuring no single party can unilaterally change network control. ChainLaunch surfaces this as a UI-based governance flow.
- Tolerates up to ⌊(n−1)/3⌋ faulty validators — a 4-node network withstands 1 failure
- Add or remove validators via on-chain proposal and vote — no restart required
- Configurable block time and epoch length per network
- Clique (PoA) support for dev and test networks
- Validator health monitoring with per-node block-signing metrics
Tessera Private Transactions
Hyperledger Tessera is a private transaction manager that sits alongside each Besu node. When a transaction is marked private, the payload never touches the main chain — only a 512-byte hash does. The actual data is encrypted and sent directly to the specified Tessera nodes. Non-participants see the hash but cannot decrypt the content.
- Private transaction payload stored off-chain in Tessera, not on the main ledger
- Specify recipient Tessera nodes per transaction — fine-grained data sharing
- Privacy groups for repeated private interactions between a fixed set of parties
- EEA-compatible private transactions (priv_ JSON-RPC namespace)
- ChainLaunch provisions and wires Tessera to each Besu node automatically
EIP Support & On-chain Permissioning
Besu tracks Ethereum mainnet upgrades — EIP-1559 fee market, EIP-155 replay protection, Shanghai, Cancun — so your Solidity contracts compile and run identically on both networks. Permissioning is enforced at the node and account level through smart contracts deployed at reserved addresses, giving you auditable, on-chain access control.
- Full EIP compliance — ERC-20, ERC-721, ERC-1155, EIP-1559 all work out of the box
- Node permissioning: allowlist which enode URIs can connect
- Account permissioning: restrict which addresses can send transactions
- Smart-contract-based rules — permissioning is auditable on-chain
- JSON-RPC namespaces: eth_, net_, web3_, debug_, priv_, eea_
What's Included
Everything you need, fully managed
Every ChainLaunch managed plan comes with enterprise-grade features built in.
- RBAC + 2FA
Role-based access control with two-factor authentication across all users
- HashiCorp Vault integration
Enterprise-grade key and secrets management out of the box
- Enhanced audit logs
Tamper-evident audit trail for compliance and security monitoring
- Real-time monitoring
Live block, transaction, and node health metrics with alerting
- Federated metrics
Cross-network metrics aggregation and analysis for multi-org deployments
- Advanced analytics
Comprehensive reporting and dashboards across all your networks
- Automated cert management
Certificate lifecycle handled automatically — no manual PKI work
- Priority support
Direct access to the ChainLaunch engineering team during business hours
- Zero-downtime upgrades
Roll out chaincode and orderer upgrades without interrupting transactions
- Enterprise security
Network isolation, encrypted storage, and SOC 2-aligned controls
From the Blog
From someone who's shipped it
David Viejo writes about Hyperledger Fabric and Besu — what works in production, what kills projects, and what the docs leave out.
What Is Hyperledger Besu? Enterprise Ethereum Guide (2026)
Hyperledger Besu powers 9.5-16% of Ethereum mainnet and Nigeria's eNaira CBDC. Architecture, QBFT consensus, privacy, deployment, and enterprise use cases explained.
Deploy a Besu QBFT Network in 2 Minutes, No Genesis File
One command. 4 validators. Pre-funded accounts. No Kubernetes. No manual genesis.json. Copy-paste tutorial with screenshots.
QBFT Consensus in Besu: Genesis, Validators & Block Time
Genesis.json setup, validator add and remove, block time tuning, and the fault tolerance math. QBFT is the default consensus for new Besu networks.
FAQs
Frequently Asked Questions
How quickly can I get a blockchain network running?
What blockchains does ChainLaunch support?
Can I connect nodes from multiple companies?
Can ChainLaunch support production deployments, not just PoCs?
What happens if I need to scale?
How does ChainLaunch handle security and key management?
Ready to Deploy Your Besu Network?
Stop struggling with complex Besu configurations. Deploy enterprise-ready EVM networks in minutes with ChainLaunch.
ChainLaunch Pro Includes AI-powered smart contracts, enterprise privacy, EVM compatibility, and premium support. Pricing tailored to your organization.
Talk to David Viejo
Founder & CTO · 6+ years blockchain · Responds within 24h
Questions about Besu deployment? Contact us
New to Besu? Start with our step-by-step guide:
Create a Besu Network in 2 Minutes →