Introduction to HashSpheres
HashSpheres are enterprise-grade, private, permissioned deployed instance of the Hedera networks. They are designed for organizations that require the advanced capabilities of Hedera's technology but are unable to use the public mainnet due to specific regulatory, operational, or governance constraints.
What is a HashSphere?
HashSpheres provide a dedicated ledger environment, enabling organizations to meet requirements such as:
Data privacy: restrict network access and visibility.
Permissioned access: control who can submit transactions and run nodes.
Custom governance: align policies, operations, and approvals to your model.
Data residency: keep infrastructure in a required region.
Technology foundation
A HashSphere is a private instance of the same open-source Hiero codebase that powers the Hedera public mainnet. This code, managed by the Linux Foundation's Decentralized Trust (LFDT), ensures that HashSpheres benefit from the same core features and developer tools available on the public network.
Applications built on a HashSphere can leverage Hedera's full suite of network services:
Hedera Smart Contract Service (HSCS): Fully EVM compatible layer with bridging capability between EVM Smart contracts and Hedera's Native services.
Hedera Token Service (HTS): Offers fast, affordable token creation and transfers without complex smart contracts.
Hedera Account Service (HAS): Transfer private network tokens between accounts.
Hedera Consensus Service (HCS): High-throughput event ordering and messaging to support auditable workflows.
Hedera File Service (HFS): Store small files on ledger (~1024 KB).
For SDK usage and protocol behavior, use the Hedera documentation as the source of truth.
HashSphere Managed Service
HashSpheres are offered as a fully managed service, operated by the operations team at Hashgraph. Customers receive a private Hedera network configured to their unique requirements and backed by enterprise-grade support. HashSpheres are deployed on either Amazon Web Services (AWS) or Google Cloud Platform (GCP) within a segregated and secure cloud account. A typical deployment includes:
A typical deployment includes:
Four Consensus nodes across multiple AZs.
One Mirror node for optimized read access and history.
One JSON-RPC relay that enable submissions of EVM transactions to the network.
A private network explorer for viewing accounts, transactions, and on-ledger activity.
A network console monitoring tool for observing the overall health and performance of the network and its components.
Depending on your requirements, it may also include:
Upgrade and maintenance processes.
Backup and restore capabilities.
Monitoring integrations.
Enhanced support workflows.
Learn more
Please contact the HashSphere Business Development team through the contact page on the main HashSphere Website.
Last updated