> 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/veyra-browser.md).

# Veyra Browser

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

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

The **Veyra Browser** is a Chromium-based browser built specifically to access the true web. Unlike standard browsers that depend on extensions or centralized DNS, Veyra Browser has native support for Veyra domains and hosting. It provides a direct, censorship-resistant way to access sites without add-ons or third-party gateways.

***

#### Key Features <a href="#key-features" id="key-features"></a>

**1. Native Domain Resolution**

* Veyra domains (e.g., `project.anon`, `site.true`, `app.veyra`) resolve directly in the address bar.
* No plugins, no hacks, no redirects.
* Just type the domain name and the browser connects to the site.

**2. Peer-to-Peer Hosting Integration**

* Connects directly to Veyra’s peer-to-peer node network.
* Automatically selects healthy nodes to load content.
* Supports failover: if one node is offline, another serves the site seamlessly.

**3. Multiple Access Paths**

* **Direct Node Connections**, connects straight to peer-to-peer hosting.
* **Mirrors**, falls back to community portals if nodes are unavailable.
* **Tor**, built-in Tor support for censorship-resistant browsing.

**4. Privacy First**

* No hidden analytics, no trackers.
* Ships with strict privacy defaults.
* Local resolution, queries are verified against the blockchain, not sent through a central service.

**5. Open Source**

* Fully open-source and auditable.
* Anyone can fork, modify, or build their own version.
* Transparent development ensures trust by design.

***

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

1. A user installs Veyra Browser.
2. They type `myapp.veyra` into the address bar.
3. The browser checks the on-chain records for `myapp.veyra`.
4. It fetches hosting data and connects to the peer-to-peer network.
5. If no nodes respond, it automatically tries trusted mirrors or Tor.
6. The site loads, privately and without relying on centralized DNS or registrars.

***

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

Extensions are fragile, they depend on app stores like Chrome Web Store or Firefox Add-ons, which can remove them without warning. Veyra Browser removes that risk by baking support directly into the browser.

It isn’t about replacing Chrome or building a new ecosystem from scratch. It’s about ensuring that the true web can always be reached, directly, without gatekeepers.


---

# 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/veyra-browser.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.