> For the complete documentation index, see [llms.txt](https://docs.constellationnetwork.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.constellationnetwork.io/run-a-node/validator-node-guides/build-your-node/turn-your-vps-into-a-node.md).

# Turn your VPS into a Node

This guide will help you create your node using nodectl.

## nodectl Installation Types

### Introduction[​](https://docs-v1.constellationnetwork.io/validate/automated/install/nodectl-install-types#introduction) <a href="#introduction" id="introduction"></a>

The following documentation will help guide a new Node Operator understand the differences between turning a newly created VPS into a Constellation Network validator node with the use of `nodectl`.

There are three options:

{% content-ref url="/pages/wlMqKRzurlj8FwQ3ztJ0" %}
[Quick Install Guide](/run-a-node/validator-node-guides/build-your-node/turn-your-vps-into-a-node/quick-install-guide.md)
{% endcontent-ref %}

{% content-ref url="/pages/ziaFxv6fwgKJc1xnezUS" %}
[Normal Install Guide](/run-a-node/validator-node-guides/build-your-node/turn-your-vps-into-a-node/normal-install-guide.md)
{% endcontent-ref %}

{% content-ref url="/pages/dPQjqXGzMl6iYpFGCyLf" %}
[Manual Installation](/run-a-node/validator-node-guides/build-your-node/turn-your-vps-into-a-node/manual-installation.md)
{% endcontent-ref %}

## **Normal Install**[**​**](https://docs-v1.constellationnetwork.io/validate/automated/install/nodectl-install-types#normal-install)

A normal installation is a more detailed and interactive method of installing `nodectl` on your VPS. The process will guide you through each step of the installation interactively with details on each step, along the way.

## **Quick Installation**[**​**](https://docs-v1.constellationnetwork.io/validate/automated/install/nodectl-install-types#quick-installation)

This installation method installs `nodectl` with minimal prompts or user interaction. You will only be asked a few questions:

* Which cluster you would like your node to join
* Whether you want to migrate an existing `.p12` keystore
* Passphrase for the `.p12` keystore:
  * Create a new one if needed
  * Enter the passphrase if using an existing keystore
* New password for the Node Administrator

#### [Understanding passphrases and passwords](/run-a-node/validator-node-guides/build-your-node/node-operator-notes.md#understanding-passphrase-and-passwords).

## **Manual Installation**[**​**](https://docs-v1.constellationnetwork.io/validate/automated/install/nodectl-install-types#manual-installation)

This new installation can be preformed [manually](https://docs-v1.constellationnetwork.io/validate/manual/manual-install-getting-started) if desired by advanced users.

**nodectl is recommended.**


---

# 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.constellationnetwork.io/run-a-node/validator-node-guides/build-your-node/turn-your-vps-into-a-node.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.