The first clue is the vocabulary. Hashgraph does not call HashSphere a chain, a subnet or a rollup. It calls each private deployment a “Sphere” - a controlled little world with its own validators, geography and rules. The name sounds cosmic. The customer is more likely to be wearing a bank lanyard and carrying a compliance checklist.
Hashgraph is an enterprise software company with roots in Swirlds, the business formed by computer scientist Leemon Baird and Mance Harmon after Baird invented the hashgraph consensus algorithm. That algorithm became the machinery beneath Hedera, the public distributed ledger. Today, the distinction matters: the Hedera Council governs the public network; Hashgraph maintains and develops much of its code and sells products built with the technology.
The company says it now has nearly 200 people across 20 countries. Its job has expanded from tending the engine to building the vehicles. HashSphere is the private infrastructure. Asseto is the dashboard for creating and operating tokenized financial products. CLPR, pronounced “clipper,” is the still-in-development communications layer meant to connect ledgers without the usual custodial bridge. Together they form a practical thesis: institutions will adopt tokenization when the software accommodates regulation, rather than asking regulation to get out of the way.
The awkward customer was the useful one
Public blockchains offer a shared record and assets that can travel. They also make a poor place for a bank to expose balances, counterparties or trading intentions. Traditional private ledgers protect that information, but often create a new island. Hashgraph's product strategy lives in this awkward middle.
The first thing to fail was the forced choice. Financial institutions did not want to publish everything, and they did not want a private network that trapped everything. The workaround - cross-chain bridges that lock assets and rely on extra operators or validator groups - produced concentrated targets for attackers and additional trust assumptions. Hashgraph's diagnosis is that privacy and interoperability have to be designed together.
What changed the company's mind was not one spectacular collapse. It was the slow verdict of the “protocol wars.” Ethereum's virtual machine became the common development environment. Eye-watering throughput claims proved less useful than predictable performance under ordinary conditions. Most important, regulated industries kept asking for selective disclosure and control. Eric Piscini, Hashgraph's chief executive since 2023, distilled the conclusion bluntly: the future would be hybrid.
“The future of distributed systems isn't about choosing between public or private networks.”Hashgraph's case for HashSphere
A stack, not another science project
HashSphere is EVM-compatible, so developers can bring Solidity code and established tooling. Customers can take a managed service or host it themselves, choose the number and size of nodes, restrict operations to a country or cloud provider, and set a validator and governance model. Privacy is cryptographic: Hashgraph describes encrypted balances and zero-knowledge proofs supporting private transfer, delivery-versus-payment and payment-versus-payment. Transactions are meant to settle in roughly three to five seconds.
That addresses the ledger. Asseto addresses the work surrounding it. Developed by Madrid-based ioBuilders and offered by Hashgraph since June 2026, the software combines APIs, smart contracts and a visual back office. A financial institution can configure equities, bonds, funds, loans and digital cash; run primary or secondary workflows; and support atomic settlement. The important word is configure. Tokenizing a bond should not require inventing a small software company every time.
The underlying Asseto technology came with a useful head start: ioBuilders reported more than €6 billion in processed transactions and over 60 delivered projects before the Hashgraph offering. Hashgraph invested in the company and became a seller and service provider. This is a faster route up the stack than building every back-office screen from scratch.
CLPR is the connective tissue and the unfinished piece. Rather than custody assets, the protocol sends messages backed by cryptographic state proofs. In the first phase, dedicated endpoints on each ledger exchange proofs. If an endpoint goes offline, a transfer pauses rather than putting funds at risk. A later design moves that work into the ledgers' validators. HashSphere-to-HashSphere and HashSphere-to-Hedera are the opening routes; other EVM networks are on the map.
The postmaster that never holds the parcel
committed state
verifies state
Here is the sober part. CLPR was still in closed beta in 2026. The protocol cannot repeal software risk: a bug in a verifier contract or a flawed proof implementation could still be consequential, and token issuers must authorize burns, mints, freezes or wrapping. “Bridge-free” means removing an intermediary and its honeypot, not removing the need for audits, key management and careful deployment.
The proof is wearing a regulator's badge
Hashgraph's most persuasive work is not a laboratory transactions-per-second chart. HashSphere participated in Project Acacia, an Australian research program led by the Reserve Bank of Australia and the Digital Finance Cooperative Research Centre. Across the program, participants developed 24 use cases; 19 involved real-world transactions in fixed income, private markets and trade receivables. Hashgraph worked with Australian Payments Plus to explore how tokenized money could meet established national payment infrastructure rather than merely orbit it.
In Qatar, a different consortium put the same architecture beneath a digital receipt system for Shariah-compliant, asset-backed finance. Qatar Financial Centre provided the lab and regulatory setting; Hashgraph ran HashSphere; Blade Labs built contracts and interfaces; AlRayan Bank supplied banking and Shariah expertise; Google Cloud supplied infrastructure. The point was not to sprinkle blockchain over a loan. It was to improve visibility across a multiparty workflow without revealing sensitive data or surrendering governance.
Insurance offers another test. Hashgraph and The Institutes RiskStream Collaborative are developing a property risk portal that keeps sensitive records private while anchoring identifiers to a public ledger. If it works, underwriters, brokers and reinsurers get a shared reference for information that currently arrives fragmented and repeatedly reconciled. It is gloriously unsexy, which is usually a promising sign for infrastructure.
What it costs - and how the company gets paid
Hashgraph does not publish a rate card. HashSphere is sold through direct enterprise engagement as managed or self-hosted infrastructure, with service levels, support, node configuration and implementation shaping the bill. Asseto adds software and servicing; advisory and integration work add more. Hashgraph also performs outsourced engineering and ecosystem work for Hedera. This is enterprise software economics, not a self-serve SaaS checkout.
The one unusually crisp price belongs to the origin story. In 2022, the Hedera Council bought the hashgraph intellectual property from Swirlds for 292.7 million HBAR, valued then at $76,340,420. The Council open-sourced the code under Apache 2.0, and a large part of the operating team moved into Swirlds Labs. Two years later, Swirlds Labs renamed itself Hashgraph. The handoff separated network governance from product development and gave the company room to sell above the protocol.
If one trusted operator owns the workflow, a conventional database will usually be cheaper and simpler. Hashgraph makes sense when several parties need a shared, auditable state and no single party should quietly rewrite it.
The five moves worth stealing
Hashgraph's playbook is available even to companies that never touch Hedera. It is less about cryptography than sequencing.
- Begin with one expensive multiparty workflow. Reconciliation, settlement and shared risk data are better starting points than a vague mandate to “do Web3.”
- Separate private facts from public proofs. Decide which data must stay confidential and which events benefit from shared verification.
- Keep the tools developers already know. HashSphere's EVM compatibility reduces retraining and makes existing code more portable.
- Connect to the rails people actually use. Project Acacia worked beside national payment infrastructure; it did not pretend that infrastructure had vanished.
- Measure before scaling. A controlled proof of concept can expose governance and operational problems before a production commitment hardens them.
The conditions matter. This model is a poor fit when all participants already trust one database owner, when full public transparency is acceptable, or when the asset has no plausible need to move between networks. It also struggles if governance is fuzzy: choosing validators, jurisdictions, recovery procedures and issuer permissions is organizational work disguised as configuration. Cryptography can enforce a rule; it cannot decide whose rule is sensible.
Hashgraph sits in a crowded market. Hyperledger Besu, Corda and enterprise Ethereum systems compete for private deployments. Public networks compete on liquidity and developer mindshare. Chainlink CCIP, LayerZero, Axelar and others attack interoperability. Tokenization vendors attack the application layer. Hashgraph's differentiation is the way it bundles the layers around Hedera's consensus and lets a customer choose public, private or hybrid operation without changing the basic development model.
That bundle is also the risk. HashSphere is generally available, but parts of the wider vision are young. CLPR must prove itself under audit and production load. Asseto must show that configurable instruments survive the delightful edge cases of actual markets. The company has moved beyond selling a consensus story; now it has to win the slower contest of integrations, controls and support tickets. In institutional finance, that is where belief becomes a business.