> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hedera.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Localnet
**Hiero Local Node Deprecation (September 2026)**
Hiero Local Node is entering a 6-month deprecation period. Support ends September 2026. Migrate local testing and CI workflows to [Solo](https://solo.hiero.org/docs/) before then. [Learn more](https://hedera.com/blog/hiero-local-node-deprecation-6-month-transition-to-solo/).
## Introduction
The Hedera Localnet provides developers with a comprehensive framework for locally testing and refining Hedera-based applications. By operating outside the public networks, Localnet eliminates network I/O bottlenecks, minimizes shared resource conflicts, and gives you complete control over network configurations. The recommended local development 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.
**Migrating from Local Node?** Hiero Local Node is in a 6-month deprecation period ending September 2026. Solo is the supported replacement. See the [Local Node section below](#local-node-deprecated) for instructions that remain valid through the deprecation window.
***
## 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.
### What Solo runs
A Solo deployment includes the same stack you find on Hedera mainnet and testnet:
* [**Consensus node**](/support/glossary#consensus): processes transactions and participates in Hashgraph consensus
* [**Mirror node**](/support/glossary#mirror-nodes): stores transaction history and serves REST, gRPC, and Web3 APIs
* [**Block node**](/support/glossary#block-node): streams record files from the consensus node and makes them available to downstream consumers
* [**JSON-RPC relay**](/support/glossary#json-rpc-relay): translates Ethereum JSON-RPC into Hedera transactions, enabling EVM tooling (MetaMask, Hardhat, Foundry, Ethers.js)
* [**Mirror Node Explorer**](/support/glossary#network-explorer): web-based block explorer for auditing transactions and accounts locally
### Get started
Quickstart, installation, and configuration guides for Solo.
Install Solo and start your first local network in minutes.
Configure the JavaScript, Java, and Go SDKs to point at a Solo network.
Connect MetaMask, Hardhat, and Foundry to a local Solo network.
Port mappings and endpoints for the consensus node, mirror node, and relay.
***
## Local Node (deprecated)
Hiero Local Node is in a 6-month deprecation period. Support ends September 2026. Migrate local testing and CI workflows to [Solo](#solo) before then.
The Local Node replicates a Hedera network comprised of a single node (or few if configured) on a developer’s local machine, offering a controlled environment for developing, testing, and experimenting with [decentralized applications (dApps)](/support/glossary#decentralized-application-dapp). This local setup utilizes [Docker Compose](https://docs.docker.com/compose/) to create multiple containers, each with a specific role within the network, including but not limited to:
* **Consensus Node**: Simulates the behavior of Hedera’s consensus mechanism, processing/ordering transactions and participating in the network’s consensus algorithm.
* [**Mirror Node**](/support/glossary#mirror-nodes)**:** Provides access to the historical data, transaction records, and the current state of the network without participating in consensus. This is useful for querying and analytics.
* [**JSON-RPC Relay**](/support/glossary#json-rpc-relay): Offers a local JSON-RPC implementation of the [Ethereum](/support/glossary#ethereum) JSON-RPC APIs for Hedera to enable interactions with smart contracts and accounts. This is particularly useful for developers familiar with Ethereum tooling and ecosystem.
* [**Mirror Node Explorer**](/support/glossary#network-explorer): A web-based interface that allows developers to audit transactions, accounts, and other network activities visually.
### Setup and Configuration
Single-node configuration simulates the network’s functions on a smaller scale (on a single node), ideal for debugging, testing, and prototype development. Multi-node configuration distributes multiple instances of the Hedera network nodes across a single machine using Docker containers, intended for advanced testing and network emulation.
➡ [**Single Node Configuration**](/networks/localnet/single-node)
➡ [**Multinode Configuration**](/networks/localnet/multinode)
### Operational Modes
Local Node offers two modes depending on a developer’s needs:
Full mode is activated with the `--full` flag, and the system is designed to capture and store comprehensive data. Here’s how it works:
* **Data Upload**: Each node within the network generates record stream files during operation. Record stream files are a sequence of transaction records grouped together over a specific interval. The Hedera network periodically consolidates these transaction records into stream files, which are then made available to the network nodes and mirror nodes. In full mode, these files are systematically uploaded to their own directory within the `minio` bucket. MinIo is an object storage platform that provides dedicated tools for storing, retrieving, and searching blobs. This process is managed by specific uploader containers assigned to each node, namely:
* `record-streams-uploader-N`(contains record streams)
* `account-balances-uploader-N` (contains account balances files)
* `record-sidecar-uploader-N` (contains a list of `TransactionSidecarRecords` that were all created over a specific interval and related to the same `RecordStreamFile`.
Turbo mode is the default setting when running the local node. This mode prioritizes efficiency and speed, with the following key characteristics:
* **Local Data Access**: Instead of uploading data to the cloud, record stream files are read directly from their corresponding local directories on each node. This method significantly reduces latency and resource consumption, making it ideal for scenarios where immediate data access and high performance are prioritized over long-term storage and external accessibility.
With these two options, users can tailor the local node’s operation to suit their needs best, whether ensuring comprehensive data capture and backup or optimizing for performance and speed.
***
## Additional Resources
* [**Solo Repository**](https://github.com/hiero-ledger/solo)
* [**Solo Documentation**](https://solo.hiero.org/docs/)
* [**Hiero Local Node Repo**](https://github.com/hiero-ledger/hiero-local-node) *(deprecating September 2026)*
* [**Docker Compose Documentation**](https://docs.docker.com/compose/intro/features-uses/)
* [**Run a Local Node in Gitpod**](/native/local-dev/cde/gitpod) **\[tutorial]**
* [**Run a Local Node in Codespaces**](/native/local-dev/cde/codespaces) **\[tutorial]**