# Running in CLI

## Hardware Requirements

**Minimum:**

* CPU with 1+ cores
* 2GB RAM
* 4 MBit/sec download Internet service

**Recommended:**

* Fast CPU with 2+ cores
* 4GB+ RAM
* 8+ MBit/sec download Internet service

{% hint style="info" %}
The verifier node does not need a static IP address or open ports.
{% endhint %}

{% hint style="info" %}
The verifier node does not require significant storage capacity. The minimum storage needed is merely for the software and its configuration, which should be less than 100MB.
{% endhint %}

#### **Running in Desktop App**

You can operate your nodes on any OS by using the Desktop App. Check [Running in Desktop App](/carv-ecosystem/verifier-nodes/join-mainnet-verifier-nodes/operating-a-verifier-node/running-in-desktop-app.md)for more details.

#### **Starting with Source Code**

If you prefer to start with the source code, you can choose one of the following methods:

* [Using Source Code](/carv-ecosystem/verifier-nodes/join-mainnet-verifier-nodes/operating-a-verifier-node/running-in-cli/using-source-code.md)
* [Using Docker](/carv-ecosystem/verifier-nodes/join-mainnet-verifier-nodes/operating-a-verifier-node/running-in-cli/using-docker.md)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.carv.io/carv-ecosystem/verifier-nodes/join-mainnet-verifier-nodes/operating-a-verifier-node/running-in-cli.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.