Skip to content

Permissioned Blockchain Networks for Business Partners

Hyperledger Fabric and Besu networks, chaincode and integrations that let known organisations share trusted records without a public token.

Book a free consultationWhat we build
chaincode/shipments.go
Sample code

Hyperledger development for enterprise data sharing

Hyperledger is a family of open-source enterprise blockchain projects hosted by the Linux Foundation. Hyperledger Fabric provides permissioned networks with private channels, pluggable consensus and chaincode written in Go, Java or JavaScript. Hyperledger Besu is an Ethereum client that can run private, permissioned EVM networks. Both let known organisations share a tamper-evident record without exposing data to the public.

Hyperledger fits consortiums and enterprises in supply chain, trade finance, certification, healthcare records and government services, where participants are known and data privacy matters. Public chains like Ethereum or Solana make more sense when you need open participation or tokens. And when a single organisation controls all data, a well-audited database is usually simpler, which we will tell you upfront.

Nexzem designs Fabric and Besu networks, writes and tests chaincode, and builds the APIs, dashboards and integrations that connect the ledger to existing ERP and document systems. We containerise network nodes with Docker and Kubernetes, document governance for adding members, and keep the architecture simple enough for your IT team to operate.

Read Hyperledger, the way we write it

A short, idiomatic sample. Scroll and the editor types each part while the note beside it explains why it is written that way.

chaincode/shipments.go
Sample code
package main
import (
"encoding/json"
"fmt"
"github.com/hyperledger/fabric-contract-api-go/contractapi"
)
// Chaincode: business rules every permissioned peer runs the same way
type Shipments struct{ contractapi.Contract }
// Each write is endorsed according to the channel policy
func (s *Shipments) Record(ctx contractapi.TransactionContextInterface, id, status string) error {
data, err := json.Marshal(map[string]string{"id": id, "status": status})
if err != nil {
return fmt.Errorf("encode shipment %s: %w", id, err)
}
return ctx.GetStub().PutState(id, data)
}
func main() {
cc, err := contractapi.NewChaincode(&Shipments{})
if err != nil {
panic(err)
}
// Start serves the chaincode to the peer
if err := cc.Start(); err != nil {
panic(err)
}
}

  1. line 10-12

    Chaincode: business rules every permissioned peer runs the same way

  2. line 13-26

    Each write is endorsed according to the channel policy

  3. line 27-31

    Start serves the chaincode to the peer

What we build with Hyperledger

Private, permissioned blockchain networks on Hyperledger Fabric and Besu for enterprise data sharing.

  1. 01

    Fabric Network Setup

    Design and deployment of Hyperledger Fabric networks with organisations, peers, ordering service, channels and certificate authorities configured for your consortium.

  2. 02

    Chaincode Development

    Smart contracts in Go, Java or JavaScript that encode asset rules, approvals and endorsement policies, with unit tests and versioned upgrades.

  3. 03

    Hyperledger Besu Networks

    Private, permissioned EVM networks on Besu for teams that want Solidity tooling without exposing data on a public chain.

  4. 04

    Supply Chain Traceability

    Track batches, shipments and certificates across suppliers, manufacturers and distributors with tamper-evident records and QR-based verification that buyers and inspectors can check themselves.

  5. 05

    Integration APIs

    REST APIs and event listeners that connect the ledger to ERPs, document systems and partner portals without forcing users onto new tools.

  6. 06

    Network Operations

    Kubernetes deployment, monitoring, certificate rotation, backups and member onboarding procedures so the network keeps running reliably as members join, leave or upgrade software.

Why teams pick Nexzem for Hyperledger

The checks every engagement has to pass before we call it done.

.github/PULL_REQUEST_TEMPLATE.md4/4 checked

  • - [x] Privacy between partners

    Channels and private data collections share only what each member should see.

  • - [x] Tamper-evident records

    Every change is endorsed and recorded, which supports audits and dispute resolution.

  • - [x] No public token needed

    Permissioned networks avoid cryptocurrency exposure and gas fees.

  • - [x] Fits existing systems

    APIs connect the ledger to the ERP and document tools your partners already use.

When a permissioned blockchain makes sense

A permissioned blockchain such as Hyperledger Fabric or Besu is worth considering when several independent organizations need to share a record, none of them is trusted by all the others to run a central database, and the history must be tamper-evident and auditable. Typical examples include supply chains, consortia of banks or insurers and registries shared between agencies.

If one organization can host the data and others are comfortable trusting it, a well-secured shared database with audit logs is usually cheaper, faster and simpler. A blockchain adds governance overhead, specialized skills and infrastructure in every participating organization, so it must solve a real trust problem to justify itself. An honest assessment at the start saves money either way.

Permissioned networks also suit cases where data must stay private between subsets of participants, which public blockchains handle poorly. Fabric's channels and private data collections, and Besu's privacy features, let consortium members share only what each relationship requires. This selective sharing is often what convinces competitors to join the same network.

Designing a Hyperledger Fabric network

A Fabric network is made of organizations, each running peers that hold ledger copies and execute chaincode, and an ordering service, typically using Raft consensus, that sequences transactions. Identities come from certificate authorities managed per organization, and endorsement policies define which organizations must approve each type of transaction before it is committed.

Chaincode is written in Go, Java or JavaScript, and large documents are stored off-chain with only their hashes recorded on the ledger, keeping the chain lean while proving documents have not changed. Applications connect through gateway SDKs, and integration APIs let participants' ERP and logistics systems read and write without users touching the blockchain directly.

  • Organizations, peers and a Raft ordering service.
  • Channels and private data collections for confidentiality.
  • Endorsement policies matching business rules.
  • Off-chain document storage with on-chain hashes.
  • Integration APIs for existing enterprise systems.

Governance and operations

Technology is rarely the hardest part of a consortium network; governance is. Members must agree who can join, how chaincode changes are approved, who pays for shared infrastructure, how disputes are resolved and what happens when a member leaves. Fabric's chaincode lifecycle supports this by requiring approvals from organizations before new code is used.

Operations need ongoing ownership: monitoring nodes, rotating certificates, upgrading Fabric or Besu versions, backing up ledgers and supporting new members during onboarding. The Hyperledger projects are now part of the Linux Foundation's decentralized trust initiative, which provides long-term open governance for the software itself.

Start with a pilot involving a small number of committed members and one clear process, such as tracking a single product line or document type. Measure time saved, errors avoided and member effort, then use the results to agree funding and governance before scaling to the wider consortium.

  • Written consortium agreement covering membership and costs.
  • Approval process for chaincode and configuration changes.
  • Certificate management and key protection per member.
  • Monitoring, backups and version upgrade plans.

How Hyperledger projects run

$ git log --graph --oneline main..delivery

  1. 5569731

    feat: consortium and use case review

    We confirm participants, data flows, trust needs and whether a ledger is justified.

  2. a7ad21e

    feat: network and data design

    Organisations, channels, endorsement policies and private data defined.

  3. 2c3b053

    feat: build chaincode and APIs

    Chaincode, integration APIs and dashboards developed and tested together.

  4. fcf3434

    merge: pilot and expand

    Pilot with a small group of members, then onboarding and production rollout.

What teams build with Hyperledger

  • Pharmaceutical supply chain traceability

    Manufacturers, distributors and pharmacies record each batch's movement on a shared ledger, letting regulators and partners verify authenticity and trace recalled batches quickly without any single company controlling the record.

  • Trade finance document sharing

    Banks, exporters and importers share letters of credit and shipping documents through a permissioned network, reducing paper handling and fraud risks while each bank sees only the transactions it participates in.

  • Academic credential verification

    Universities record degree certificates as hashes on a shared ledger, and employers verify a candidate's credentials instantly online, reducing fake certificates and the manual verification requests that burden university offices.

  • Carbon credit registry

    Project developers, verifiers and buyers track carbon credit issuance, transfers and retirement on a permissioned network, preventing double counting and giving buyers an auditable record of every credit they retire.

  • Multi-party reconciliation for insurers

    Insurers and reinsurers share claims and settlement records on a common ledger, replacing periodic spreadsheet reconciliation with a single agreed record and reducing disputes over who owes what and when.

Where Hyperledger sits in your stack

The tools we pair it with, layer by layer. Select a layer to see what it is responsible for.

Technologies often used with Hyperledger

All 32 technologies

More in Cloud & Web3

Hyperledger development FAQs

Something else on your mind? Ask a consultant and get a reply within one business day.

Hyperledger or a public blockchain?

Hyperledger suits known participants who need private, permissioned data sharing without tokens. Public chains like Ethereum or Solana suit open participation, tokens and public verifiability. If only one organisation controls the data, a conventional database may be best.

Fabric or Besu?

Fabric offers private channels and flexible endorsement for complex consortiums. Besu suits teams wanting Ethereum-compatible Solidity contracts on a private network. We choose based on privacy needs and team skills.

What drives Hyperledger project cost?

Number of member organisations, chaincode complexity, privacy requirements, integrations, hosting model and governance needs drive effort. A fixed quote follows a free consultation.

How long does a Hyperledger pilot take?

A focused pilot with a few organisations and core chaincode typically takes a few months, depending on integrations and member coordination. We plan pilots to prove value before full rollout.

Who runs the network after launch?

Usually each member runs its own nodes, or one party hosts on behalf of others. We provide deployment scripts, runbooks and optional support so the network stays healthy.

Do we really need a blockchain, or would a shared database work?

If one trusted party can run the system and others accept its records, a shared database with strong audit logs is usually simpler and cheaper. Blockchain is justified when several organizations must share a record without trusting any single operator, and tamper-evident history matters.

What are private data collections in Hyperledger Fabric?

Private data collections let a subset of organizations on a channel share confidential data among themselves, while only a hash of that data goes to the shared ledger. Others can verify the data existed and was not altered, without seeing its contents.

We work with clients across the USA, UK, Australia, UAE, New Zealand and India.

Where we work

Tell us what you're building.

A solutions consultant replies within one business day with a recommended stack, a rough estimate and a suggested team.

Book a free consultation+91-7302622997