> For the complete documentation index, see [llms.txt](https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/documentation/readme.md). # Overview ### Hyper Performance Edge Computing (HPEC DAO)
HPEC DAO (Hyper Performance Edge Computing DAO) is a decentralized, autonomous infrastructure network designed to deliver compute-intensive and AI-driven services through a global network of DAO-governed Node Factories. HPEC DAO does not operate as a traditional cloud provider or SaaS platform.\ Instead, it provides **autonomous infrastructure outcomes**, delivered by decentralized nodes and orchestrated by autonomous agents under DAO governance. Clients do not interact with servers, instances, or manual DevOps processes.\ They consume **availability, performance, and execution guarantees** as outcomes. *** ### What HPEC DAO Enables Through **CMHPEC (Clustered Modular Hyper Performance Edge Computing)**, HPEC DAO enables: * Decentralized high-performance compute * Autonomous AI and agent-driven operations * Node Factories as productive infrastructure units * Outcome-based infrastructure services * DAO-governed execution and revenue distribution Infrastructure is treated as a **long-term productive asset**, not a consumable resource. *** ### Core Service Model HPEC DAO is built on two primary service layers: #### ANaaS — Autonomous Node as a Service ANaaS provides decentralized compute, storage, and networking capacity through DAO-governed Node Factories.\ Nodes are orchestrated autonomously and exposed as **service capacity**, not as raw machines. #### AaaS — Agents as a Service AaaS provides autonomous agents that plan, execute, monitor, and optimize workloads running on ANaaS.\ Agents replace manual DevOps and operational workflows with autonomous execution. Together, ANaaS and AaaS form a unified service model that delivers infrastructure **without manual operations**. *** ### Service Stack Overview ``` Client / Organization ↓ AaaS – Agents as a Service ↓ ANaaS – Autonomous Node as a Service ↓ Node Factories ↓ HyperCycle Network ``` Clients experience the top of the stack.\ Infrastructure complexity is handled autonomously below. *** ### Governance & Decentralization All HPEC DAO services are: * Governed by HPEC DAO * Executed on DAO-operated Node Factories * Coordinated through CMHPEC * Monetized transparently * Aligned through on-chain and off-chain governance rules No single entity owns the infrastructure, agents, or services.\ The DAO coordinates participation, authority, and incentives. *** ### What HPEC DAO Is — and Is Not **HPEC DAO is not:** * A centralized cloud provider * A SaaS platform * A hosted DevOps service **HPEC DAO is:** * An autonomous infrastructure network * A DAO-governed execution layer * A foundation for AI, web, and compute-intensive services > “We don’t sell servers.\ > We deliver autonomous outcomes.” *** ### How to Use This Documentation This documentation explains: * How the HPEC architecture is structured * How Node Factories and operators participate * How services are delivered through ANaaS and AaaS * How governance, authority, and economics are enforced Use the **Getting Started** section to understand the architecture,\ then explore **Basics** to learn how the network operates.

:bolt:

ArchitectureArchitectureArchitecture

:leaf:

ServicesServiceshttps://github.com/GitbookIO/gitbook-templates/blob/main/product-docs/broken-reference/README.md

:globe-pointer:

Governance & DAOGovernance & DAOCMHPEC Network
Node OperatorsLearn how to operate or delegate infrastructureNode Operator Authorities | NOA
--- # 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, and the optional `goal` query parameter: ``` GET https://hyper-performance-edge-computing.gitbook.io/hyper-performance-edge-computing-hpec-dao-docs/documentation/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.