> For the complete documentation index, see [llms.txt](https://docs.netsepio.com/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.netsepio.com/latest/erebrus/nodes.md).

# Nodes

Erebrus Nodes empower a distributed, secure, and scalable network, enabling users to share compute, storage, and connectivity while earning rewards. Each node serves a distinct function, forming a robust ecosystem for AI, VPN, and high-performance workloads.

1. Astro Node – A lightweight, client-mode node that allows users to deploy AI agents and host light weight webapp services locally. It enables resource sharing while earning rewards through staking, operating without a static IP.
2. Beacon Node – A decentralized VPN gateway, running as a Docker container with a static IP. It allows clients to connect securely and does not require a node license, making it a simple yet essential entry point into the network.
3. Nexus Node – A full-scale orchestrator that requires a domain and static IP. It manages VPN access, firewalls, DNS assignment, and production app deployment for global connectivity. Running a Nexus Node requires staking and a node license.
4. Titan Node – A high-performance compute node designed for AI model execution, GPU workloads, and intensive applications. It requires a powerful workstation with a static IP and necessitates staking and a node license.
5. Zenith Node – A private enterprise-grade VPN network designed for businesses. It establishes a secure, last-mile firewall and VPN infrastructure, deployable on-premises or in the cloud. No staking is required, but a license fee applies, with additional monthly fees for NetSepio cloud deployments.

## Supported Blockchains

* Solana
* Peaq
* Monad (Testnet)
* Rise Sepolia (Testnet)

## Supported Nodes

* Beacon
* Nexus


---

# 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.netsepio.com/latest/erebrus/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.