Skip to content

Service · Blockchain

Private Blockchain Development Services

Commission us to design and stand up a permissioned network that a group of identified organisations can run together. We cover membership and identity, data privacy between members, the business logic on the ledger and how each party operates its nodes.

Fabric and Besu both considered

Governance written before code

Per-member node runbooks

Deliverables

What a private blockchain development engagement delivers.

01Delivered

Consortium governance model

Who may join, who approves new members, how chaincode or contract upgrades are agreed, and what happens when a member leaves, written as a document the members sign off.

02Delivered

Network topology

Organisations, peers or validators, ordering or consensus nodes, and channels or privacy groups, sized for fault tolerance and mapped to which member runs what.

03Delivered

Identity and certificate setup

Certificate authorities per organisation for Fabric, or node permissioning and account allowlists for Besu, with documented issuance and revocation.

04Delivered

Ledger business logic

Chaincode in Go or TypeScript for Fabric, or Solidity contracts on Besu, with endorsement or validation rules that reflect how members actually approve transactions.

05Delivered

Integration adapters

Services that connect each member’s existing ERP, document or reporting systems to the network, so staff keep working in tools they know.

Early decisions

Technical decisions we settle early in private blockchain development.

01Decided

Fabric or Besu

Fabric suits channel-based privacy and flexible endorsement between organisations; Besu suits teams that want Ethereum tooling, Solidity and a possible path to public networks.

02Decided

Privacy mechanism

Separate channels, private data collections with hashes on the shared ledger, or Besu privacy groups, each with different implications for who sees what and how disputes are evidenced.

03Decided

Consensus and fault tolerance

Raft ordering for Fabric or QBFT for Besu, sized so the network survives the loss of the nodes you expect to fail or misbehave.

04Decided

Hosting model

Every member runs its own nodes, one operator hosts on behalf of all, or a mix. This decides how decentralised the network really is.

05Decided

Endorsement policy

Which organisations must sign before a transaction counts, balanced so one absent member cannot halt business but one rogue member cannot act alone.

Engagement

How a private blockchain development engagement runs.

  1. 01Phase 1

    Member workshops

    We meet representatives from each organisation to agree the shared process, the data each party contributes, what must stay confidential and who arbitrates disputes.

  2. 02Phase 2

    Network blueprint

    Topology, privacy design, identity scheme and governance rules are written up and reviewed by every member’s technical and compliance contacts.

  3. 03Phase 3

    Build on a staging network

    Chaincode or contracts, adapters and monitoring are built on a multi-organisation staging network that mirrors the production layout, including certificate rotation.

  4. 04Phase 4

    Member onboarding

    Members bring nodes online one at a time with a runbook, while we verify endorsement, privacy boundaries and recovery before the first real transaction.

Fit

When a private blockchain is the right choice.

01Good fit

Competitors must share a process

Organisations that do not fully trust each other need one agreed record of shipments, claims, certificates or settlements.

02Good fit

Data cannot be public

Commercial terms or personal records rule out a public chain, yet a shared, tamper-evident history is still required.

03Good fit

Participants are known and accountable

Every member can be identified, contracted with and removed, so open participation offers nothing useful.

Governance is the hardest deliverable

Technology rarely sinks a consortium network. Disagreement does: over who pays for nodes, who can add members, and how an upgrade is approved when one party is slow to respond. We write these rules down with the members before building, because retrofitting them into endorsement policies is painful.

Choosing between Fabric and Besu

Hyperledger Fabric was designed for enterprise consortia, with channels, pluggable endorsement and chaincode in general-purpose languages. Besu is an Ethereum client that can run permissioned networks, which suits teams that already know Solidity or want compatibility with public Ethereum tooling.

Neither is universally better; the choice follows the privacy model and the skills each member already has.

Privacy has layers

Putting data in a channel limits it to that channel’s members, but administrators of those peers can still read it. Private data collections narrow it further. We map each data type to the narrowest audience that still lets the process work, and document that mapping for each member’s compliance team.

Each member must be able to run its part

A network where one vendor operates every node is decentralised only on paper. We aim for members to run their own peers or validators, with monitoring, certificate renewal and backup procedures they can follow without us.

FAQ

Questions to resolve before the build.

01Is a private blockchain just a shared database?

It is closer to a shared database where no single member holds the admin password. The value comes from members validating each other’s writes. If one party could run it for everyone, a database with audit logs is often enough.

02Can the network connect to a public chain later?

Besu makes that path easier because it uses Ethereum tooling. Fabric can anchor hashes to a public chain through an integration. Either way, plan for it up front rather than retrofitting.

03Who owns the network once it is live?

The members do, according to the governance document agreed at the start. We hand over runbooks and can stay on to support operations, but we do not become a hidden central operator.

04How is confidential data kept from other members?

Through channels, private data collections or privacy groups, depending on the platform. Only authorised members hold the data itself; others may see a hash proving it existed at a given time.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
  2. 02

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.