> For the complete documentation index, see [llms.txt](https://docs.energyweb.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.energyweb.org/ewc-validator-documentation/guides/set-up-your-validator-node-in-minutes-with-ew-launchpad.md).

# Set-up your Validator node in minutes with EW Launchpad

Validators who opt to install and run their nodes externally can use [**Launchpad by Energy Web**](https://launchpad.energyweb.org/login) to install and host their Validator Nodes. This presents major advantages as the platform will fully support your node and handle the technical requirements. Additionally, spinning up your nodes using Launchpad is a lot quicker and does not require a high technical proficiency.

Energy Web members still benefit from 1 EWC and 1 Volta node even when using Launchpad. There is the option to chose to bring your own cloud (BYOC) or to use a managed cloud in which case there is a hosting fee.

**Find detailed instructions in our** [**Quick Start Guide**](https://docs-launchpad.energyweb.org/launchpad-by-energy-web/blockchain-infrastructure/validator-nodes/quick-start-guide)**.**


---

# 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.energyweb.org/ewc-validator-documentation/guides/set-up-your-validator-node-in-minutes-with-ew-launchpad.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.
