Platform implementation

Hyperledger Fabric

We build Hyperledger Fabric networks in which each member runs its own peers and certificate authority, and chaincode changes only when the agreed organisations approve.

Empty data centre aisle between rows of server racks

Fabric suits consortia that want privacy built into the design: channels separate business lines, private data collections keep details between two members, and each organisation's MSP decides who acts for it. Members can host peers in their own data centres, which helps with data residency in both markets, and bank pilots often start in SAMA's regulatory sandbox or ADGM's RegLab.

Fabric's chaincode lifecycle shapes the delivery: chaincode is packaged, approved by each organisation and committed with an endorsement policy that reflects who must agree. We run the ordering service on Raft, or on BFT ordering from Fabric v3, issue identities through Fabric CA or the member's own PKI, and connect applications through the Fabric Gateway.

Hyperledger Fabric and related product names may be trademarks of their respective owners.

How we implement Hyperledger Fabric

Implementation, customisation, deployment and ongoing support, with governance your steering committee can follow.

  • Blueprint and governance

    Every founding member's technical and risk leads sign off the channel layout, endorsement policies, private data collections and certificate hierarchy before the network is built.

  • Endorsement policy design

    Policies stating which organisations must endorse each transaction type, tested against real business disputes.

  • Member onboarding kit

    A packaged process and scripts for a new member to join a channel, set up peers and approve chaincode.

  • Certificate renewal plan

    Expiry tracking and renewal for every node and admin certificate, a common cause of Fabric outages.

  • Hypercare and managed support

    We keep the network on a Fabric long-term support release, run chaincode upgrades through the approval process, renew certificates ahead of expiry and watch orderer and peer health.

When Fabric fits the consortium

Consortia of known organisations, such as banks, trade partners or government entities, choose Fabric when they need fine-grained privacy and no cryptocurrency in the design.

  • Founding members ready to run their own peers
  • Business rules that say which parties must agree to each transaction
  • A certificate plan per member, through Fabric CA or its own PKI
  • Data that some members must not see

Plan Hyperledger Fabric with Hosn Al Tomoh

Tell us what the platform needs to do and when. We will propose a first phase with scope, team and an itemised quotation.

Talk to our team