Hyperledger blockchain development services build permissioned networks on open-source Hyperledger software, mostly Hyperledger Fabric and Hyperledger Besu. This guide explains how Fabric and Besu work, what a development firm delivers in each project phase, what drives cost, and which questions to ask a firm before you sign.
The Hyperledger projects in 2026
Hyperledger is a family of open-source projects, not a single blockchain. In September 2024 the Hyperledger Foundation became part of LF Decentralized Trust, a Linux Foundation umbrella. LF Decentralized Trust also hosts identity, cryptography and interoperability projects, including Hiero, the open-source codebase behind Hedera.
The main projects keep the Hyperledger name, but some older projects are archived, for example Hyperledger Composer, so check the release history of any project before you build on it.
| Project | What it is | Typical use |
|---|---|---|
| Fabric | Permissioned ledger with chaincode, channels and private data | Workflows shared by several organizations that need strict privacy and no token |
| Besu | Java Ethereum client for public Ethereum and private EVM networks | Teams that want Solidity, EVM tools and a route to public chains |
| FireFly | Middleware that adds APIs, events, tokens and data exchange on top of Fabric or EVM chains | Teams that do not want to write their own integration layer |
| Cacti | Interoperability framework | Moving assets or data between different ledgers |
| Indy and AnonCreds | Identity ledger and a credential format | Verifiable credentials with privacy-preserving proofs |
| Iroha | Permissioned ledger with built-in asset commands | Simple asset registries |
For the history and core concepts, read Hyperledger development explained; this page covers the build itself.
Fabric or Besu: how to choose
Fabric fits a network where each participant may see only part of the data, and it lets you write endorsement rules, such as "the buyer's and the seller's organizations must both sign." Choose Fabric when the data will never need to reach a public chain.
Besu fits a team that already writes Solidity, and it works with standard Ethereum wallets, libraries and audit firms. Choose Besu when tokens may later move to a public network.
Besu once offered private transactions through the Tessera transaction manager. Besu 25.6.0 removed Tessera privacy and on-chain (smart contract) permissioning, and Besu 25.7.0 removed the EEA and PRIV privacy APIs. Privacy on a Besu network now comes from node permissioning, separate networks for separate groups, or sensitive data kept off-chain.
Corda and Quorum compete for the same projects. GoQuorum, the original Quorum client, is archived, and new Quorum-style networks run on Besu. See Corda blockchain and Quorum development for those platforms.
How Hyperledger Fabric development works
Most blockchains order transactions first and execute them after. Fabric uses an execute-order-validate model instead:
- A client application sends a transaction proposal to endorsing peers.
- Each peer runs the chaincode against its copy of the world state and returns a signed read-write set, committing nothing.
- The client collects enough endorsements to meet the endorsement policy, then sends the transaction to the ordering service.
- The orderers put transactions into blocks. Raft tolerates crashed nodes, and the SmartBFT orderer added in Fabric 3.0 also tolerates dishonest orderer nodes.
- Every peer checks the endorsements and checks that the data the transaction read has not changed since (the MVCC check), then commits the valid transactions.
Fabric 3.0 shipped in September 2024 and removed the system channel, the Solo and Kafka orderers, and the legacy chaincode lifecycle. A network on Fabric 1.x or an early 2.x release must migrate those parts before an upgrade. Fabric 2.5 is the long-term support release, and in June 2026 the project shipped Fabric 3.1.5 and 2.5.16.
A Fabric network has these parts:
- Organizations and MSPs. Each organization runs a certificate authority, often Fabric CA, and a Membership Service Provider (MSP) defines which identities belong to the organization.
- Channels. A channel is a separate ledger shared by a subset of organizations. Each channel adds operating work, so most networks keep the number low.
- Private data collections. Authorized organizations share private data directly between their peers, while the channel ledger stores only a hash of that data.
- World state database. LevelDB gives fast key-value access, while CouchDB adds rich JSON queries but runs slower.
Writing and deploying chaincode
Chaincode is Fabric's name for smart contracts, written in Go, Java, or JavaScript and TypeScript. It reads keys, applies business rules, writes keys and emits events.
Chaincode must be deterministic. Calls to external APIs, the local clock, random numbers or Go map iteration give different results on different peers, so the endorsements disagree and the transaction fails.
Key design also matters, because many transactions that update the same key at once cause MVCC conflicts. Composite keys spread writes across many keys and remove most of these conflicts. Fabric 3.1 added read and write batching to chaincode, which reduces the number of round trips between chaincode and peer.
Fabric deploys chaincode through a lifecycle with four steps: a developer packages the chaincode, each organization installs the package on its peers, enough organizations approve the definition, and one organization then commits it to the channel.
An upgrade follows the same steps with a new sequence number, so a chaincode change needs approval from member organizations. On Kubernetes, teams often run chaincode as an external service instead of letting peers build containers.
Client applications use the Fabric Gateway client API, available for Go, Node.js and Java, which works with Fabric 2.4 and later. The Fabric documentation has current guides for the lifecycle and the Gateway.
Building a private network with Besu
A private Besu network uses proof-of-authority consensus. Besu 26.4.0 removed Clique, so new private networks use QBFT or IBFT 2.0. The Besu documentation recommends QBFT for enterprise networks, because it tolerates dishonest validators and gives immediate finality among a known set of validators.
Local permissioning lists, or a permissioning plugin, control which nodes can connect and which accounts can send transactions. Development after that is standard EVM work: Solidity contracts, Foundry or Hardhat, OpenZeppelin libraries, and normal wallets or custody providers.
A private network can set the gas price to zero, and gas metering still stops a contract that loops without end. Besu's code now lives in the besu-eth/besu repository, and release 26.9.0 shipped in 2026. The general practices in private blockchain development also apply to Besu.
What Hyperledger blockchain development services deliver
A Hyperledger development firm usually splits a project into four phases, and the table lists the output of each phase and the people involved.
| Phase | Deliverables | Typical duration | Typical team |
|---|---|---|---|
| Discovery and network design | Platform choice, list of organizations, channel and data-privacy design, endorsement policies, integration map | 3 to 6 weeks | Architect, business analyst |
| Pilot | Network with 2 or 3 organizations, core chaincode, one system integration, test suite | 2 to 4 months | 2 or 3 backend engineers, 1 DevOps engineer |
| Production hardening | Security review, HSM key storage, monitoring, backups, upgrade runbooks | 2 to 4 months | The pilot team plus security and site reliability engineers |
| Member onboarding and support | Onboarding kits for new organizations, operations support | Ongoing | Support and operations staff |
These durations are estimates for a workflow of moderate complexity, not quotes from any firm.
The pilot phase takes 3 or 4 people for 2 to 4 months, which is about 6 to 16 person-months. Multiply that range by a firm's monthly rate for a first budget figure.
Four things change the budget most: the number of organizations, integration with ERP or core banking systems, the privacy design with channels and collections, and who runs the nodes.
Legal agreements and member onboarding often slow a multi-organization network more than the engineering does. A firm that offers blockchain consulting can help with the consortium agreement.
Running a Hyperledger network in production
A live Hyperledger network needs this operating work:
- Certificate management. Expired TLS or enrollment certificates often cause Fabric outages, so automate renewal and send alerts well before expiry. Fabric 3.1.2 lets BFT orderers rotate enrollment certificates without a configuration update when the public key stays the same.
- Kubernetes deployment. Tools such as Hyperledger Bevel deploy peers, orderers and certificate authorities with Helm charts or an operator. Bevel supports Fabric, Besu, Corda, Indy and Quorum.
- Key protection. Fabric supports hardware security modules through PKCS#11 for organization signing keys.
- Monitoring. Peers and orderers expose Prometheus metrics, so track block height, endorsement latency and ledger size.
- Backup and recovery. Write down how a peer rejoins the network or rebuilds its ledger from other members.
- Governance. The consortium agreement says who can add organizations, change policies and approve chaincode upgrades.
Fabric 3.0 deprecated block distribution through gossip, so new peers should receive blocks directly from the ordering service, as the release notes describe.
When FireFly saves time
Most Fabric and Besu projects need the same supporting code: an API for business applications, listeners that push ledger events into queues, and storage for documents that stay off-chain. Many projects also need private messages between organizations and token handling.
Hyperledger FireFly packages these functions as a "supernode" that each organization runs next to its blockchain node, giving existing systems REST APIs and event streams.
FireFly can remove months of work from a multi-party build, but it is also one more large component to run and upgrade. A project that sends only a few transaction types may not need it.
Where Hyperledger projects fail
- No partners join. A consortium network needs written commitments from partners before production starts.
- Too many channels. Dozens of channels add operating work, and private data collections often solve the same privacy problem.
- A database problem. Fabric is slower and more complex than a database, and a ledger helps only when the organizations do not trust a single operator with the data.
- Skipped upgrades. A network that stays on an old Fabric release for years faces a hard migration, as the 3.0 removals show. Plan regular upgrades within supported releases.
Fabric has seen real use in trade and supply chain traceability, and in workflows between banks or insurers. See supply chain development for traceability projects. Enterprise blockchain solutions covers whether a permissioned ledger suits your case at all.
Questions to ask a Hyperledger development firm
- Which Fabric or Besu versions has the firm run in production, and how did it handle upgrades?
- How does the firm design chaincode keys to avoid MVCC conflicts?
- How does the firm issue, rotate and monitor certificates across organizations?
- Will each member organization run its own nodes, or will one party host all of them?
- Who owns the code, the network configuration and the certificate authorities when the contract ends?
- Will the chaincode get an independent review? See smart contract audits.
Frequently asked questions
Is Hyperledger still maintained?
Yes. Fabric, Besu, FireFly, Cacti and other projects continue under LF Decentralized Trust. Fabric shipped versions 3.1.5 and 2.5.16 in June 2026. Some older projects, such as Composer, are archived.
Does Hyperledger Fabric have a cryptocurrency?
No. Fabric has no native token and no gas fees, though chaincode can model a token if an application needs one.
Which language should I use for Fabric chaincode?
Go has the widest use and the most documentation, and Java and TypeScript have full support. Choose the language your team will maintain, and avoid libraries that give non-deterministic results.
Can Fabric connect to Ethereum or other chains?
Not natively. Hyperledger Cacti or middleware such as FireFly can connect networks or anchor data on a public chain.
Should I choose Besu or Fabric for asset tokenization?
Most tokenization projects choose Besu or a public EVM chain, where ERC token standards, wallets and custody tools all work. Fabric suits private workflow data more than assets that must circulate.