📝 Solo has a new quick-start command! check it out: Solo User Guide, Solo CLI Commands
An opinionated CLI tool to deploy and manage standalone test networks.
Solo releases are supported for one month after their release date, after which they are no longer maintained. It is recommended to upgrade to the latest version to benefit from new features and improvements. Every quarter a version will be designated as LTS (Long-Term Support) and will be supported for three months.
| Solo Version | Node.js | Kind | Solo Chart | Hedera | Kubernetes | Kubectl | Helm | k9s | Docker Resources | Release Date | End of Support |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 0.43.0 | >= 20.18.0 (lts/iron) | >= v0.26.0 | v0.54.5 | v0.63.9+ | >= v1.27.3 | >= v1.27.3 | v3.14.2 | >= v0.27.4 | Memory >= 12GB, CPU >= 4 | 2025-08-15 | 2025-09-15 |
| 0.42.0 (LTS) | >= 20.18.0 (lts/iron) | >= v0.26.0 | v0.54.5 | v0.63.9+ | >= v1.27.3 | >= v1.27.3 | v3.14.2 | >= v0.27.4 | Memory >= 12GB, CPU >= 4 | 2025-08-11 | 2025-11-11 |
To see a list of legacy releases, please check the legacy versions documentation page.
To run a one-node network, you will need to set up Docker Desktop with at least 12GB of memory and 4 CPUs.
# install specific nodejs version
# nvm install <version>
# install nodejs version 20.18.0
nvm install v20.18.0
# lists available node versions already installed
nvm ls
# switch to selected node version
# nvm use <version>
nvm use v20.18.0
- Run
npm install -g @hashgraph/solo
Contributions are welcome. Please see the contributing guide to see how you can get involved.
This project is governed by the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code of conduct.