> 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.md).

# Peer-to-Peer Hosting

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

Veyra Hosting is built on a **peer-to-peer network of nodes** rather than a single provider. This makes websites and apps more resilient: if one node goes offline, others continue to serve the content. Hosting is distributed, censorship-resistant, and verifiable through the Veyra protocol.

***

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

**1. Decentralized by Default**

* Websites and apps are stored and served across many independent nodes.
* No single company or server has control over uptime.
* Nodes can run anywhere , from home devices to data centers.

**2. Self-Healing Network**

* If one node is shut down, others automatically step in.
* The resolver chooses healthy nodes to keep sites online.
* Content is replicated for redundancy and faster delivery.

**3. Integration with Domains**

* Every Veyra domain can be linked directly to peer-to-peer hosting records.
* When someone visits `example.veyra` or `example.anon`, the resolver fetches the site from the node network.
* This ensures that domains and hosting are tightly coupled into a single resilient system.

**4. Verifiable Delivery**

* Nodes don’t just serve files, they serve proofs.
* Users can verify that the content matches the on-chain record.
* Prevents tampering, spoofing, or malicious replacements.

**5. Incentivized Participation**

* Anyone can run a node by staking VEY.
* Nodes earn stablecoin fees (from developers who host sites) plus VEY rewards for uptime.
* Malicious nodes can be penalized or slashed, ensuring the network stays honest.

***

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

1. A developer deploys their app to Veyra Hosting.
2. The content is distributed across multiple nodes.
3. They link their domain `myapp.true` to the hosting record.
4. A user types `myapp.true` in the Veyra Browser.
5. The resolver checks the hosting record and connects to available nodes.
6. The site loads, even if some nodes are offline.

***

#### Why It Matters <a href="#why-it-matters" id="why-it-matters"></a>

Traditional hosting is fragile: one provider or data center can take you down. Veyra’s peer-to-peer hosting flips that model. Content is spread across the network, nodes are incentivized to stay honest and online, and domains are permanently tied to resilient infrastructure.

This means websites, apps, and communities can finally exist without the risk of being quietly switched off.


---

# 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.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.