specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Hyperledger
providerId: hyperledger
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: true
tags:
  - FinOps
  - FOCUS
  - Blockchain
  - Open Source
description: 'FOCUS-aligned FinOps for Hyperledger: open-source frameworks have no vendor invoice;
  cost surfaces are infrastructure (cloud / on-prem) for self-hosting plus optional vendor-managed
  offerings billed by ecosystem partners.'
sources:
  - https://lfdecentralizedtrust.org/projects
  - https://www.hyperledger.org/
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
publisherName: The Linux Foundation (LF Decentralized Trust)
serviceCategory: Blockchain & Distributed Ledger
billingModel:
  pricingCategory: Open Source (no foundation cost)
  billingFrequency: N/A (foundation) / Vendor-defined (managed offerings)
  billingCurrency: USD
  chargeCategories:
    - Usage
    - Purchase
focusColumns:
  ServiceName: Hyperledger
  ServiceCategory: Blockchain & Distributed Ledger
  ProviderName: Hyperledger / LF Decentralized Trust
  PublisherName: The Linux Foundation
  InvoiceIssuerName: varies (cloud provider for self-hosted; vendor for managed)
  BillingCurrency: USD
  ChargeCategory: Usage
meters:
  - name: node_compute_hours
    description: Compute-hours for self-hosted Hyperledger nodes (peers, orderers, validators); billed
      by underlying cloud or on-prem infrastructure rather than the foundation.
    unit: instance-hour
    aggregation: sum
    dimensions:
      - framework
      - cloud
      - region
      - node_role
  - name: ledger_storage
    description: GB-month of ledger / world-state / chaindata storage attached to nodes.
    unit: GB-month
    aggregation: avg
    dimensions:
      - framework
      - tier
  - name: network_egress
    description: Network egress for peer-to-peer gossip and external API consumers.
    unit: GB
    aggregation: sum
    dimensions:
      - framework
      - region
  - name: vendor_managed_service
    description: Managed-blockchain billing line items charged by ecosystem vendors (IBM Blockchain,
      AWS Managed Blockchain, Kaleido, Oracle Blockchain).
    unit: varies
    aggregation: sum
    dimensions:
      - vendor
      - sku
  - name: transactions_submitted
    description: Operational throughput meter; useful for unit economics even though not directly
      billed.
    unit: transaction
    aggregation: sum
    dimensions:
      - framework
      - channel
      - chaincode
principles:
  - name: Visibility
    description: Hyperledger itself produces no invoice. Track cost via the underlying cloud or on-prem
      infrastructure billing (AWS Cost Explorer, Azure Cost Management, GCP Billing, Kubernetes cost
      tools like OpenCost). For managed offerings, use the vendor's billing portal.
  - name: Allocation
    description: Tag node infrastructure by network / consortium / channel so that cost can be allocated
      back to the participating organization. Use Kubernetes namespaces and labels when running Fabric
      / Besu under K8s.
  - name: Optimization
    description: Right-size peer and orderer nodes; use spot/preemptible nodes for non-critical peers;
      consolidate networks where governance allows; consider managed offerings only when in-house
      operational cost exceeds vendor markup.
  - name: Accountability
    description: Establish per-consortium and per-channel cost ownership. For managed offerings,
      review monthly vendor invoices and validate node count, transaction volume, and storage size
      against expectations.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com