# Deploy on your own hardware

This guide will help you deploy and run a Hybrid Integrity Node on your own server or local machine.\
Ideal for technical users who want full control and direct self-hosting.

{% hint style="info" %}
⚠️ Note:\
Make sure your operator address is funded with ETH on Arbitrum (ARB) to respond to challenges.\
If the ETH balance is insufficient, your node may experience reduced uptime!
{% endhint %}

{% embed url="<https://www.youtube.com/watch?v=08AJpDxFl6k>" %}

***

#### Pre-requisites

Before you begin, make sure you have:

✅ **Docker & Docker Compose installed**

* The easiest option is Docker Desktop, which bundles both.
* Alternatively, you can install them separately:
  * [Docker Engine Installation Guide](https://docs.docker.com/engine/install/)
  * [Docker Compose Installation Guide](https://docs.docker.com/compose/install/)

✅ **A wallet with your Operator Private Key**, funded with a small amount of ETH on Arbitrum to pay for gas.

***

#### Step 1: Clone the Repository

Open a terminal on your machine and run:

```bash
git clone https://github.com/buildonhybrid/integrity-node.git
cd integrity-node
```

This downloads the latest Hybrid Integrity Node source code and moves you into its directory.

***

#### Step 2: Review the Repository

You can explore the cloned folder in your file manager or a text editor.\
The structure should match what’s shown in the repository’s README.

***

#### Step 3: Create a `.env` Configuration File

In the root of the repository, create a new file named `.env`.\
This will hold your node’s settings.

Add the following lines:

```env
RPC_URL=https://arb1.arbitrum.io/rpc
OPERATOR_PRIVATE_KEY=your_private_key_here
PROTOCOL_CONTRACT_ADDRESS=0x070Af5bcE820f61e409417AfF9b4C1B15B6537df
```

✅ **Notes:**

* `RPC_URL`: Use any Arbitrum RPC endpoint. The above is a reliable public one.
* `OPERATOR_PRIVATE_KEY`: Your wallet’s private key that will operate the node.\
  ⚠️ Ensure this wallet has enough ETH on Arbitrum for gas.
* `PROTOCOL_CONTRACT_ADDRESS`: Provided in the repository’s README.

***

#### Step 4: Start the Node with Docker Compose

In the same terminal, run:

```bash
docker compose up -d
```

This does the following:

* Pulls the latest Docker images.
* Starts your node in detached mode (runs in the background).

✅ **What’s running:**

* `hybrid-node`: Core job processor.
* `watchtower`: Monitors for new container updates and auto-updates every 3 hours.

***

#### Step 5: Monitor Node Logs

You can view live logs to confirm your node is running properly:

```bash
docker compose logs -f hybrid-node
```

***

#### Step 6: Delegate Licenses

1. Go to the [Hybrid Delegation Dashboard](https://nodes.buildonhybrid.com/dashboard).
2. Connect the wallet that holds your Integrity Node License NFTs.
3. Click **“Delegate NFT”**, input your `OPERATOR` address (the wallet from `.env`), and choose how many licenses to delegate (up to 50 per operator).

***

#### Step 7: Restarting or Stopping Your Node

* To stop your node:

```bash
docker compose down
```

* To pull the latest images and restart:

```bash
docker compose up -d --pull always
```

***

#### ✅ You’re Done!

Your Integrity Node is now fully operational, securing the Hybrid network and earning rewards.\
You can check your node status anytime on the Delegation Dashboard.


---

# 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.buildonhybrid.com/manage-integrity-nodes/deploy-on-your-own-hardware.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.