Dojima Cluster Launcher is a free, open source utility for Windows that sets up ready-to-go Kubernetes clusters for deploying a HermesNode on selected cloud providers. It is aimed at node operators and developers who want a repeatable, scripted way to build the infrastructure a node runs on, instead of assembling every component by hand. The program is available as a Windows build or installer, and the project also lists macOS as a supported platform.
Most of the work happens in a terminal. You open the Local Terminal, follow the project's steps, and let the launcher create the cluster on the provider you selected. The AWS path has the most documented prerequisites: an AWS account, a configured AWS CLI, AWS IAM Authenticator and wget for the EKS module. The project's last code update is dated June 2024, so review recent activity on GitHub before relying on it for anything important.
What Problem a Cluster Launcher Solves
Setting up a node by hand usually means provisioning servers, configuring a cluster orchestrator, wiring up networking and access rules, and then deploying the node software itself. Each step has its own documentation and its own failure modes. A cluster launcher compresses the infrastructure part into a sequence of guided commands.
The main value is repeatability. If you need to stand up the same environment twice, for example once for testing and once for a live node, a scripted launcher produces the same layout both times. That makes it easier to compare results, rebuild after a mistake and document the procedure for others.
The launcher does not replace understanding what it builds. You still need to know which region, account and resources you are creating, because those choices determine where your node runs and what it costs to keep running. Treat the launcher as a faster way to follow a known architecture, not as a substitute for knowing that architecture.
Who Is Dojima Cluster Launcher For?
The launcher suits people who already plan to run a HermesNode and want the surrounding infrastructure handled consistently. Typical readers include node operators who are comfortable in a terminal, developers testing deployments and small teams that need a procedure others can repeat.
It is less suited to people who have never used a command line or never created a cloud account. The AWS path asks you to create an IAM user, configure credentials and install several supporting tools before the launcher does any useful work. Beginners can still learn from the process, but should expect a learning curve.
If your target is a different blockchain client, such as Geth for Ethereum or Bitcoin Core for Bitcoin, this launcher is not built for that job. Those programs run a node directly on a machine you already control, while this tool focuses on building the cluster that hosts a HermesNode.
Kubernetes and Node Hosting in Plain Terms
Kubernetes is a system for running containerized applications across one or more machines. It schedules workloads, restarts them when they fail and lets you scale them up or down. A cluster is the group of machines and control components that work together under that system.
For a blockchain node, the appeal is operational. A node needs stable storage, predictable networking and a way to recover from crashes. Kubernetes provides building blocks for those needs, but it is also complex. Misconfigured networking or permissions are common sources of trouble, which is why a tested cluster template can be valuable.
Beginners often underestimate how much of the work is ongoing maintenance, including upgrades, monitoring and access control. A launcher sets up the initial state, but you remain responsible for what runs on the cluster afterward.
Cloud Accounts, Permissions and Responsibility
Because the AWS workflow creates real resources in your own account, you are accountable for them. Use an IAM user with only the permissions the task requires, rather than the root account. Scoped permissions limit the damage if a key leaks and make it clearer what the tool is allowed to change.
AWS offers a free tier that many people use to experiment. Check its current terms on the AWS website before creating resources, because free-tier coverage does not apply to every service, and a cluster can accumulate charges when left running.
Keep a list of what you create, including regions, clusters and networking components, and delete what you no longer need. This habit matters more with automated tools, because resources can be created faster than you notice them.
Key features
Ready-to-go Kubernetes clusters
Focus on HermesNode deployment
Selection of supported providers
Terminal-based workflow
Dedicated AWS EKS module
Free and open source code
Supported coins
Dojima Cluster Launcher is built around deploying a HermesNode on selected providers. The integration the project documents in most detail is Amazon Web Services, using Amazon Elastic Kubernetes Service through a dedicated EKS module. Other provider integrations may need additional tools, which the project outlines in the documentation for each provider, so check that page before you start.
How to install Dojima Cluster Launcher on Windows
- 1
Get the Windows build or installer
Download the Windows build or installer only from the official website or the project's GitHub Releases page at github.com/dojimanetwork/dojima-cluster-launcher. Avoid mirrors and file-sharing sites. A modified copy of a tool that handles cloud credentials is a serious risk.
- 2
Verify the file
If the release page publishes a SHA-256 checksum or a signature, compare it with your download. In PowerShell, the Get-FileHash cmdlet with the SHA256 algorithm prints the hash of a file. If the value does not match the published one, do not run the file.
- 3
Install the program
Run the installer, or extract the Windows build to a folder you control. Keep the program in a location you can find later, since you will reopen it to rebuild or update clusters.
- 4
Prepare the AWS prerequisites
Create or sign in to an AWS account, install the AWS CLI and create an IAM user with permissions for the resources you plan to create. Configure that user's credentials locally. Install AWS IAM Authenticator and wget as well, because the EKS module depends on them.
-
Open the Local Terminal
Open the Local Terminal and follow the project's steps in order. Read each command's output before moving on, and stop if an error appears rather than retrying blindly.
System requirements
- Windows, using the Windows build or installer
- An AWS account for the AWS-based workflow
- AWS CLI installed, with an IAM user that has permissions to create the required resources
- AWS credentials configured in the CLI before you start
- AWS IAM Authenticator installed and available in the terminal
- wget, required for the EKS module
- Some other provider integrations may need additional tools, as described in each provider's documentation
How to use Dojima Cluster Launcher
Before you start, confirm that your AWS CLI works with the credentials you configured, because the launcher relies on them. Then work through the process in order. The steps below describe the general flow, and the project's own documentation contains the exact commands.
- Open the Local Terminal and confirm your AWS credentials are active.
- Choose the provider you want to deploy to. For the AWS path, this means the EKS module.
- Check that wget and AWS IAM Authenticator are installed and available in your terminal session.
- Run the launcher's cluster creation steps and wait for each stage to finish before moving on.
- Confirm the cluster exists in your AWS console before deploying anything to it.
- Deploy the HermesNode according to the project's instructions.
- Record the region, cluster name and the location of your credentials in a private note, so you can rebuild or remove the setup later.
- Delete the cluster and its resources when you no longer need them, to avoid ongoing charges.
Pros & cons
- Free and open source, with the code published on GitHub
- Targets a specific workload, HermesNode, rather than a generic setup
- Cluster creation is scripted, which makes setups easier to repeat
- Windows build or installer available, and macOS is also listed
- Terminal workflow that is easy to document and share
- The last code update is dated June 2024, so development activity may be limited
- Requires AWS knowledge and several supporting tools before it works
- Provider setup depends on each provider's own documentation
- A cluster left running in the cloud can create ongoing costs
- The command-line focus may be a barrier for non-technical users
Is Dojima Cluster Launcher safe?
This tool handles cloud credentials, so treat it with the same care as any program that can create resources in your account. Download it only from the official website or the project's GitHub Releases page, and verify the SHA-256 checksum or signature when one is published. Never enter a seed phrase or wallet recovery phrase into a launcher or any website, because no infrastructure tool has a legitimate reason to ask for one. Use an IAM user with limited permissions, avoid sharing access keys and rotate them if you suspect exposure. The last code update was in June 2024, so review recent activity on GitHub before deploying anything important.
- Official source only. Download from github.com/dojimanetwork/dojima-cluster-launcher. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
Dojima Cluster Launcher solves a different problem from most entries in this catalog. Geth, Bitcoin Core, Nethermind and Agave each run a blockchain client or validator directly on a machine you manage. The launcher works one layer below that: it builds the Kubernetes cluster where a HermesNode can be deployed. If you want to run an Ethereum execution client, Geth or Nethermind are the relevant programs. If you want infrastructure for a HermesNode on a cloud provider, this launcher is the relevant one. Choose based on the workload you need to run rather than on the tool name.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- —
- Last update
- 10 Jun 2024
- Windows support
- Yes (Windows build or installer)
- Source code
- github.com/dojimanetwork/dojima-cluster-launcher
Frequently asked questions
Yes. The program is listed as free and open source, and its source code is published on GitHub. Free access to the launcher does not cover the cloud resources it creates. Amazon Web Services bills for clusters, instances and networking you create in your account, so check AWS pricing before you begin and remove resources you no longer need.
Yes. The project provides a Windows build or installer and also lists macOS as a supported platform. Follow the installation steps on this page, then open the Local Terminal to begin. On Windows you still need the supporting AWS tools, including the AWS CLI, AWS IAM Authenticator and wget, because the EKS module depends on them.
It can be, if you obtain it from the official source and protect your credentials. Get the file from the official website or GitHub Releases, verify the checksum or signature, and use a limited IAM user. Never enter a seed phrase into any launcher or website. The safety section on this page covers the full checklist.
HermesNode is the node that the launcher deploys. The launcher prepares the Kubernetes cluster that will host it, while the node software and its configuration come from the project's own instructions. Read those instructions carefully before you run the deployment step, since the cluster setup is only one part of getting a node running.
The AWS path described for the program requires one. You need an AWS account, a configured AWS CLI, an IAM user with suitable permissions and AWS IAM Authenticator. The AWS free tier can be useful for experimenting, but free-tier coverage varies by service, so review the AWS terms before creating anything.
wget is required for the EKS module, so it must be installed and available in your terminal before you run that module. The module depends on it during its setup steps. Other providers may need different tools, which are listed in their respective documentation.
Not easily. The workflow is terminal-based and assumes some understanding of cloud accounts, permissions and Kubernetes concepts. Beginners can follow the steps with patience, but it helps to practice on a small, temporary cluster and delete it afterward so you learn the cleanup process too.
The project's last code update is dated June 2024. That does not mean the software is broken, but it does mean you should check the GitHub repository for recent commits, open issues and release notes before relying on it for a live deployment.
Verdict
Dojima Cluster Launcher is a focused, free, open source tool for anyone who wants to create Kubernetes clusters for deploying a HermesNode on a supported provider. It rewards people who already understand their cloud account and are comfortable in a terminal. It is less suitable for complete beginners or for anyone looking for a general-purpose cluster manager. Given the June 2024 code update, review recent activity on GitHub and check the latest version on the official website before committing to a deployment.