How to Run Hedera Local Node in a Cloud Development Environment (CDE)

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 before then. Learn more.

The Hedera Local Node project enables developers to establish their own local network for development and testing. The local network comprises the consensus node, mirror node, JSON-RPC relay, and other Consensus Node services be set up without Docker and draining your computer’s resources by using .Cloud Development Environments (CDEs). CDEs allows developers to work from any device without the need to maintain static and brittle local development environments.

Available Services

The Hedera local node comes with various services, each serving different functions, and accessible locally. These are the endpoints for each service:

Type	Endpoint
Consensus Node Endpoint	http://localhost:50211/
Mirror Node GRPC Endpoint	http://localhost:5600/
Mirror Node REST API Endpoint	http://localhost:5551/
JSON RPC Relay Endpoint	http://localhost:7546/
JSON RPC Relay Websocket Endpoint	http://localhost:8546/
Mirror Node Explorer (HashScan)	http://localhost:8080/devnet/dashboard
Grafana UI	http://localhost:3000/
Prometheus UI	http://localhost:9090/

You may access these services on localhost, and these endpoints are set up to be accessed from your own computer as if they were running locally. Since Gitpod and Codespaces are cloud-based development environments, “localhost” here refers to a virtual environment on cloud servers that you’re accessing through your browser. Gitpod and Codespaces redirects these local addresses to your cloud workspace, making it feel as though you’re working on a local setup.

Set Up a Hedera Local Node using the NPM CLI Run a Local Node in Gitpod

⌘I

​Available Services

Available Services