Skip to main content

Enterprise Blockchain

Production networks for regulated industries

Permissioned and public enterprise blockchain networks for institutions, governments, and large enterprises. We design the architecture, build the network, and operate it under contract.

Book a discovery callSee frameworks
Protocols supported
7+
Permissioned + sovereign
Permissioned + public
Hybrid
Anchor to Ethereum or Polygon
Deployment
Multi-cloud
AWS, GCP, Azure
Enterprise IAM
SAML · OIDC
And Active Directory

Choosing between Corda and Fabric

Most enterprise blockchain networks land on Corda or Fabric. The choice follows from your privacy model, what your regulator expects to see, and the systems the network has to integrate with.

R3 Corda logo

R3 Corda

Maintained by R3 · Apache 2.0

Built for regulated finance

Corda is a permissioned DLT designed for regulated capital markets. Transactions are shared peer-to-peer only with parties that need to see them. There is no global broadcast, no global ledger, and no global state.

Model
Permissioned · Peer-to-peer
Consensus
Notary (validating / non-validating)
Finality
Deterministic, near-instant
Contracts
Kotlin / Java (JVM)
Privacy
Need-to-know per-transaction
Identity
X.509 PKI via Network Map Service

Best for

  • Inter-bank settlement and tokenized deposits
  • Capital markets post-trade (DvP, corporate actions)
  • Syndicated lending and trade finance
  • Insurance: reinsurance and parametric claims

Framework deployments, past and present (not Instanodes clients)

  • HSBC
  • SDX
  • Contour
  • B3i
  • Spunta Banca DLT
Hyperledger Fabric logo

Hyperledger Fabric

Linux Foundation · Apache 2.0

The consortium blockchain workhorse

Fabric is a modular permissioned blockchain platform. Pluggable consensus, channels for private sub-ledgers, and execute-order-validate transaction flow make it the default choice for multi-party enterprise networks that need flexibility.

Model
Permissioned · Modular
Consensus
Raft or BFT (pluggable orderer)
Finality
Deterministic, configurable
Contracts
Go · Node.js · Java (chaincode)
Privacy
Channels + private data collections
Identity
MSP with X.509 + Fabric CA

Best for

  • Supply-chain provenance and trade documentation
  • Healthcare data sharing and consent
  • Cross-border trade and customs networks
  • Loyalty, rewards, and tokenized assets in retail

Framework deployments, past and present (not Instanodes clients)

  • IBM Food Trust
  • TradeLens
  • we.trade
  • Aadhaar pilots
  • Honeywell GoDirect

What usually decides it

Privacy model

Corda
Need-to-know peer-to-peer
Fabric
Channels + private collections

Throughput profile

Corda
Bounded by notary capacity
Fabric
Tuned via orderer and endorsement policy

Smart-contract team

Corda
JVM (Kotlin/Java) shop
Fabric
Polyglot (Go/Node/Java)

The Hyperledger frameworks we run in production

Hyperledger is a family of open-source frameworks maintained by the Linux Foundation. We build and operate 4 of them, each suited to a different kind of enterprise network.

Modular permissioned blockchain

Hyperledger Fabric

The flagship Hyperledger framework. Channels, private data collections, and pluggable consensus make Fabric the default for consortium networks.

  • Channels for sub-ledgers
  • MSP identity
  • Chaincode in Go/Node/Java
  • Raft ordering

Enterprise Ethereum client

Hyperledger Besu

Java-based Ethereum client built for enterprise. Run permissioned networks with IBFT 2.0 or QBFT consensus while keeping full EVM compatibility.

  • EVM-compatible
  • IBFT 2.0 / QBFT / Clique
  • On-chain permissioning
  • Private transactions (Tessera)

Decentralized identity ledger

Hyperledger Indy

Purpose-built for sovereign decentralized identity. Schemas, credentials, and revocation registries, used in government and sector identity networks.

  • W3C DIDs + Verifiable Credentials
  • Zero-knowledge proofs
  • Plenum BFT consensus
  • Aries agents

EVM with BFT finality

Hyperledger Burrow

A permissioned smart-contract execution environment that pairs EVM compatibility with Tendermint-style BFT consensus for deterministic, instant finality.

  • EVM execution
  • Tendermint BFT
  • Native permissioning
  • Burrow Deploy tooling

R3 Corda sits outside Hyperledger but is built and operated by the same engineering team. We pick it when finality, peer-to-peer confidentiality, and JVM tooling matter most.

The reference architecture behind every network we deliver

Frameworks and clients change between engagements. The 6 layers below, what each is responsible for, and where its audit boundary sits stay the same.

  1. L1

    Applications & Integrations

    Customer dashboards, regulator portals, ERP connectors, and partner APIs. Data migrates in from existing ledgers or off-chain systems.

    • React / Next.js
    • SAP / Oracle
    • Mobile clients
    • REST · GraphQL
  2. L2

    Smart Contracts & Chaincode

    Business logic. DvP, KYC gates, settlement workflows, tokenization rules.

    • Corda Flows (Kotlin)
    • Fabric Chaincode (Go)
    • Solidity (Besu)
    • Indy schemas
  3. L3

    Consensus & Ordering

    Deterministic finality, sized to the throughput the network has to carry.

    • Raft ordering
    • IBFT 2.0 / QBFT
    • Notary clusters
    • Plenum BFT
  4. L4

    Identity & Membership

    Who can read, write, and operate. Every action tied to a verified institution.

    • MSP / Fabric CA
    • Network Map Service
    • HSM-backed keys
    • SAML / OIDC SSO
  5. L5

    Storage & State

    World-state databases, off-chain stores, and selective archival under retention policy.

    • LevelDB · CouchDB
    • PostgreSQL vault
    • IPFS attachments
    • Encrypted backups
  6. L6

    Infrastructure & Operations

    Where the network runs and how the operations team keeps it running.

    • Kubernetes
    • FIPS-validated HSM
    • Prometheus · Grafana
    • SOC 2 Type II

Across every layer · Compliance

Designed against the framework your auditor uses.

Every layer is documented with the controls, data flows, and key custody paths your compliance team needs. SOC 2 Type II certified infrastructure, designed against the regimes below.

  • GDPR
  • MiCA
  • DORA
  • HIPAA
  • ISO 27001
  • SOC 2 Type II
  • PCI DSS

Deliverables

  • Architecture document signed off by your regulator-facing team
  • Threat model with mitigations mapped to each layer
  • Operational runbook + tabletop incident-response drills
  • Regular performance and reliability reviews
  • Optional knowledge transfer to your in-house team, on your timeline

The engagement, phase by phase

  1. Discovery and architecture

    Workshop your business case, regulatory perimeter, and integration surface. Decide permissioned vs. sovereign, framework, validator topology, governance, and key custody.

  2. Network design and review

    Detailed network design covering consensus, identity, access, data model, audit, and disaster recovery, delivered with a written architecture document and risk register.

  3. Build, test, and audit

    Implementation against your design. Internal QA, third-party security review, and load testing against your target throughput. Documentation handed over to your operations team.

  4. Operate under contract

    We run the network: validator nodes, observability, incident response, and framework upgrades, under a contractual uptime SLA with regular performance reviews.

Where Instanodes fits beside an agency or an in-house team

Each model is the right one for some teams. An agency suits a one-off build when you already have operators; an in-house team suits long-term ownership with staff to hire. Instanodes fits when you want the network built and then run under contract.

  • Best fit

    Development agency
    A defined build, with your own ops team to take it over
    In-house team
    Long-term ownership, with budget to hire protocol engineers
    Instanodes
    A production network without building a blockchain ops team

  • Who runs production

    Development agency
    Your team, after hand-off
    In-house team
    Your team
    Instanodes
    Instanodes, under a contractual uptime SLA

  • Frameworks

    Development agency
    Set by the agency's experience
    In-house team
    Set by who you hire
    Instanodes
    7 permissioned and sovereign frameworks

  • Audit documentation

    Development agency
    Scoped in the statement of work
    In-house team
    Written by your team
    Instanodes
    Architecture document and runbook in every engagement, on SOC 2 Type II certified infrastructure

  • Cost shape

    Development agency
    Build fee
    In-house team
    Salaries, hardware, and on-call
    Instanodes
    Fixed build fee plus a managed-operations subscription

  • Time to first production network

    Development agency
    Set per vendor
    In-house team
    Starts after hiring
    Instanodes
    4 – 5 weeks

The framework follows the workload

The 7 industries we deliver into most often, mapped to the frameworks suited to their privacy, finality, and regulator-facing requirements.

  • Banking

    Workload
    Inter-bank settlement · Tokenized depositsPermissioned networks for inter-bank settlement, tokenized deposits, and money-market funds. Designed against MiCA, DORA, and local regulator expectations.
    Frameworks
    CordaFabric
    Outcome
    T+0 settlement on a shared ledger
    Proof point
    MiCA / DORA mapped

  • Capital Markets

    Workload
    Post-trade · DvP · Corporate actionsT+0 settlement, atomic delivery-versus-payment, and on-chain corporate actions. Integrated with existing custody, CSDs, and order-management systems.
    Frameworks
    Corda
    Outcome
    Atomic delivery-versus-payment
    Proof point
    CSD integration ready

  • Government

    Workload
    Land registry · Identity · Vital recordsLand registry, vital records, supply-chain provenance, and credential issuance. Sovereign identity and offline operation modes.
    Frameworks
    IndyFabric
    Outcome
    Sovereign credentials with ZK proofs
    Proof point
    Offline operation modes

  • Healthcare

    Workload
    Consent · Clinical-trial integrityHIPAA- and GDPR-aligned networks for consent management, clinical-trial data integrity, and credentialing across providers and payers.
    Frameworks
    IndyFabric
    Outcome
    Cross-provider consent registry
    Proof point
    HIPAA + GDPR aligned

  • Supply Chain

    Workload
    Provenance · Trade finance · CustomsMulti-jurisdiction provenance ledgers for high-value goods. Trade finance instruments, bills of lading, and customs integration on permissioned rails.
    Frameworks
    Fabric
    Outcome
    Multi-jurisdiction provenance ledger
    Proof point
    ERP + customs connectors

  • Energy

    Workload
    Grid settlement · REC + carbonPeer-to-peer energy settlement, REC and carbon-credit issuance, and emissions audit trails. Built for utilities, regulators, and corporate buyers.
    Frameworks
    BesuFabric
    Outcome
    P2P energy settlement + audit trail
    Proof point
    Regulator-facing reporting

  • Insurance

    Workload
    Parametric · Reinsurance settlementMulti-party claims networks with auditable workflows. Reinsurance settlement, oracles for parametric triggers, and regulator-facing reporting.
    Frameworks
    CordaFabric
    Outcome
    Multi-party claims with oracles
    Proof point
    Auditable workflows

What procurement and compliance teams ask

Need something specific? Talk to an engineer.

  • The engagement covers operations as well as the build. We design networks against your regulatory perimeter, build them with the controls your auditors expect, and then either run them under contract or hand them to your team with the runbooks.

  • Permissioned: R3 Corda, Hyperledger Fabric, Hyperledger Besu, Hyperledger Indy, and Hyperledger Burrow. Sovereign and public-modular: Cosmos SDK and Substrate. We pick the framework based on your finality model, identity requirements, regulator expectations, and integration surface.

  • You do. Network governance, validator keys, and admin contracts stay with your organization or your nominated custodian. Instanodes operates under contract; you can take operations in-house or move providers at any time without code or data lock-in.

  • We deliver an architecture document, threat model, and audit-ready operational runbook with every engagement. Infrastructure is SOC 2 Type II certified and designed against ISO 27001, MiCA, DORA, GDPR, HIPAA, and sector-specific frameworks. Where required, we coordinate directly with your regulator-facing teams and external auditors.

  • Discovery and architecture come first, then build, audit, and the cut-over to operations, scoped to your requirements. A first production network typically goes live in 4 – 5 weeks. Multi-phase rollouts (additional jurisdictions, new participants) extend from that baseline.

  • Yes. ERP (SAP, Oracle), custody platforms (Fireblocks, Copper, BitGo), settlement and payments rails (SWIFT, ISO 20022, real-time gross settlement), identity providers (SAML, OIDC, Active Directory), and existing data warehouses are all in scope.

  • Two components: a fixed-fee build engagement scoped during discovery, and an ongoing managed-operations subscription based on network size, throughput, and SLA tier. Both are quoted per engagement and delivered in writing before contracting.

    Request a quote →

  • Yes. Many production networks combine a permissioned core (settlement, identity, sensitive data) with selective anchoring or settlement to a public chain (Ethereum, Polygon) for auditability or interop. We design these patterns with the trust assumptions documented for regulators.

Put a permissioned network into production.

Discovery starts with your business case and regulatory perimeter, and ends with a written architecture proposal your auditors can review.

Book a discovery callSee pricing model