> For the complete documentation index, see [llms.txt](https://docs.mayaprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mayaprotocol.com/node-docs/bare-metal-node-guides.md).

# Bare Metal Node Guides

An overview of guides made for bare metal setups

Bare Metal nodes come with several advantages over cloud provider nodes. Although the initial costs for purchasing all node equipment are higher, the monthly costs are eventually much lower, and thus the nett yield is higher. Bare Metal nodes are also more resilient. They can't be taken down by hosting services in the case of governmental bans on crypto infrastructure.

Several guides have been made for purchasing and setting up bare metal nodes.

### THORChain Validators Migration **- by @D5Sammy**

{% embed url="<https://medium.com/@d5sammy/thorchain-validator-migration-the-exhaustive-guide-2d0b9823857f>" %}

### Part 2: Multi-Node using MicroK8s - by @D5Sammy

{% embed url="<https://medium.com/@d5sammy/thorchain-bare-metal-validator-part-2-multi-node-using-microk8s-e5f98ec2c82c>" %}

### Part 3: Maya’s Chocolate- by @D5Sammy

{% embed url="<https://medium.com/@d5sammy/thorchain-bare-metal-validator-part-3-mayas-chocolate-d61cbdfe2d04>" %}

### Build your own THORChain Validator Node - by @Scorch

{% embed url="<https://medium.com/@scorch_ed/build-your-own-thorchain-validator-node-step-by-step-guide-a516e6c67b9f>" %}

### Bare-metal MAYANode - by @Runetard

{% embed url="<https://medium.com/@Runetard/bare-metal-mayanode-the-comprehensive-n00b-guide-c0da8af0c941>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mayaprotocol.com/node-docs/bare-metal-node-guides.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.