> For the complete documentation index, see [llms.txt](https://docs.veyraprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veyraprotocol.io/peer-to-peer-hosting/veyra-nodes.md).

# Veyra Nodes

<figure><img src="/files/mSC5K9yPjxOINiiqTlcL" alt=""><figcaption></figcaption></figure>

#### Overview <a href="#overview" id="overview"></a>

Veyra Nodes are the backbone of the peer-to-peer hosting network. They store and serve content for Veyra domains, making websites and applications resilient against takedowns and downtime. Anyone can run a node, from developers hosting their own apps to community members who want to help keep the true web online.

***

#### Key Properties <a href="#key-properties" id="key-properties"></a>

**1. Decentralized Hosting**

* Nodes replicate and serve website content.
* No single server or company controls uptime.
* More nodes = stronger, faster, and more resilient network.

**2. Always-On Redundancy**

* If one node goes offline, others step in automatically.
* Load balancing ensures users are always routed to healthy nodes.
* Prevents downtime from single points of failure.

**3. Staking & Incentives**

* To run a node, operators stake VEY tokens as “skin in the game.”
* Honest nodes earn stablecoin fees from hosting + VEY rewards for uptime.
* Malicious nodes can be slashed, ensuring the network stays trustworthy.

**4. Verifiable Hosting**

* Nodes serve content tied to on-chain domain records.
* Users and clients can verify that files are authentic.
* Prevents spoofing, phishing, or content injection.

**5. Open Participation**

* Anyone can spin up a node using standard hardware or a VPS.
* Nodes can run at home, in data centers, or even on lightweight devices.
* Guides and tools make setup simple (Docker images, config templates).

***

#### Example Workflow <a href="#example-workflow" id="example-workflow"></a>

1. A developer deploys their app and points their domain `myapp.veyra` to peer-to-peer hosting.
2. Content is distributed across multiple Veyra Nodes.
3. A user visits `myapp.veyra` in the Veyra Browser.
4. The browser queries the node network and connects to healthy nodes.
5. The site loadsm, even if some nodes are offline.

***

#### Why Run a Node? <a href="#why-run-a-node" id="why-run-a-node"></a>

* **Earn Rewards** - stablecoin payments + VEY incentives.
* **Support the Network** - keep the true web online for everyone.
* **Be Sovereign** - host your own projects without relying on big tech.

Running a Veyra Node means becoming part of the backbone of the true web.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.veyraprotocol.io/peer-to-peer-hosting/veyra-nodes.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.