> 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/basics-execution-layer/markdown/anaas-agents-nodes-as-a-service.md). # ANaaS - Agents Nodes as a Service Definition: **ANaaS (Autonomous Node as a Service)** is the foundational infrastructure service layer of HPEC DAO. ANaaS provides decentralized compute, storage, and networking capacity through DAO-governed Node Factories.\ Infrastructure is orchestrated autonomously and delivered as **service capacity**, not as raw machines. Clients do not deploy, configure, or manage nodes.\ They consume **guaranteed infrastructure outcomes**. *** ### What ANaaS Provides ANaaS delivers: * Decentralized compute execution * Persistent and ephemeral workloads * Redundant task execution * High-availability infrastructure * Secure networking and access control * SLA-driven service guarantees All execution occurs on **independently operated nodes**, coordinated through CMHPEC. *** ### How ANaaS Works ANaaS operates by: 1. Abstracting physical nodes into service capacity 2. Grouping nodes into DAO-governed Node Factories 3. Orchestrating workloads autonomously 4. Enforcing redundancy and availability rules 5. Delivering outcomes instead of infrastructure access Clients interact with **services**, not servers. *** ### Node Factories in ANaaS Node Factories are the execution units of ANaaS. A Node Factory: * Is a logical cluster of nodes * Operates under shared governance and economic rules * Is managed by declared Node Operator Authorities * Is economically productive Node Factories may include: * HyperAIBoxes * Oracle / state nodes * Gateway and edge nodes * Specialized compute nodes ANaaS workloads are routed to Node Factories based on capacity, health, and policy. *** ### Autonomy & Reliability ANaaS infrastructure is designed to operate autonomously. This includes: * Automated workload placement * Redundant execution across nodes * Failure detection and recovery * Capacity balancing across factories Human operators are only involved when: * Governance requires intervention * Physical maintenance is needed * Exceptional conditions occur *** ### ANaaS as Economic Infrastructure ANaaS transforms infrastructure into a **yield-generating asset**. Revenue generated from ANaaS services is distributed according to DAO-approved rules, typically across: * Infrastructure Providers (HyperAIBox Node Runners ) * Node Factory participants ( Active Ambassadors ) * DAO Treasury * Reinvestment and expansion pools Infrastructure providers earn **ongoing yield**, not one-time fees. *** ### Service Guarantees ANaaS services are delivered with DAO-defined guarantees, including: * Availability targets * Redundancy requirements * Performance thresholds * Recovery expectations Guarantees are enforced through: * Autonomous orchestration * Monitoring agents * Governance oversight *** ### What Clients Do *Not* Manage With ANaaS, clients do **not** manage: * Servers or instances * Operating systems * Networking configuration * Scaling logic * Manual failover These responsibilities are handled autonomously by the network. *** ### ANaaS and Higher-Level Services ANaaS is the foundation for all higher-level HPEC DAO services. It enables: * AaaS (Agents as a Service) * Autonomous Web Infrastructure * Future agent-driven services Without ANaaS, autonomous services cannot exist. *** ### Summary ANaaS replaces traditional infrastructure provisioning with **autonomous, DAO-governed execution**. It delivers: * Decentralized capacity * Predictable outcomes * Economic alignment * Long-term infrastructure value > ANaaS provides the capacity.\ > AaaS provides the intelligence. --- # 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/basics-execution-layer/markdown/anaas-agents-nodes-as-a-service.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.