Skip to main content

​
Introduction

A Hedera localnet gives you a network you fully control. Running outside the public networks removes network I/O bottlenecks and shared resource conflicts, and lets you configure the network however your tests need it. The recommended path is:
  1. Solo (recommended): Start local development and CI workflows on Solo, a Kubernetes-native network that fully mimics a production Hedera environment.
  2. Previewnet: Test against Hedera Previewnet for early exposure to upcoming code changes.
  3. Testnet: Validate against the stable test network before deploying to Hedera Mainnet.

​
Solo

Solo is a Kubernetes-native tool for spinning up a private Hedera network that fully mirrors a production environment. It is the recommended local development environment for new projects and the migration target for teams moving off Hiero Local Node, which is deprecated and no longer supported.

​
What Solo runs

A Solo deployment includes the same stack you find on Hedera mainnet and testnet:
  • Consensus node: processes transactions and participates in Hashgraph consensus
  • Mirror node: stores transaction history and serves REST, gRPC, and Web3 APIs
  • Block node: streams record files from the consensus node and makes them available to downstream consumers
  • JSON-RPC relay: translates Ethereum JSON-RPC into Hedera transactions, enabling EVM tooling (MetaMask, Hardhat, Foundry, Ethers.js)
  • Mirror Node Explorer: web-based block explorer for auditing transactions and accounts locally

​
Default endpoints

On Solo 0.63 and later, solo one-shot single deploy exposes: These are defaults, not guarantees. Solo forwards to the next free port when one is taken, and the assignments changed in 0.63. Confirm what your deployment exposes with solo deployment config ports --deployment <deployment-name>.

​
Get started

Local Development

Install Solo, start a network, and connect your tooling.

Solo quickstart

Install Solo and start your first local network in minutes.

Using Solo with Hiero SDKs

Configure the JavaScript, Java, and Go SDKs to point at a Solo network.

Using Solo with EVM tools

Connect MetaMask, Hardhat, and Foundry to a local Solo network.

Accessing Solo services

Port mappings and endpoints for the consensus node, mirror node, and relay.

​
Additional Resources