> 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.md). # Services HPEC DAO delivers infrastructure and operational capabilities through **autonomous, outcome-based services**. Services are not exposed as servers, instances, or manual workflows.\ They are delivered through **two composable service layers**, executed on decentralized infrastructure and governed by the DAO. Clients consume **results**, not resources. *** ### Dual Service Layers HPEC DAO services are built on two primary layers: #### ANaaS — Autonomous Node as a Service ANaaS provides decentralized compute, storage, and networking capacity through DAO-governed Node Factories. It transforms independently operated nodes into: * Autonomous infrastructure capacity * Redundant execution environments * SLA-driven service outcomes ANaaS is the **foundation** of all HPEC DAO services. → **Learn more:** [#anaas-autonomous-node-as-a-service](#anaas-autonomous-node-as-a-service "mention") *** #### AaaS — Agents as a Service AaaS provides autonomous agents that operate on top of ANaaS. Agents are responsible for: * Planning and executing workloads * Monitoring performance and availability * Handling scaling, recovery, and optimization * Escalating only when human intervention is required AaaS replaces traditional DevOps and manual operations with **autonomous execution**. → **Learn more:** [#aaas-agents-as-a-service](#aaas-agents-as-a-service "mention") *** ### Composable Service Consumption Clients may consume: * **ANaaS only**\ Infrastructure capacity with guaranteed outcomes * **ANaaS + AaaS**\ Fully autonomous operations and service delivery This allows services to scale from infrastructure-level usage to fully autonomous systems. *** ### Production Services HPEC DAO services are delivered as **production-grade outcomes**, not experimental tooling. #### Autonomous Web Infrastructure **( AWI )** Autonomous Web Infrastructure is HPEC DAO’s first production service. It delivers: * Decentralized website and application deployment * Redundant execution across Node Factories * SLA-based availability * Autonomous operations via agents This service combines ANaaS and AaaS into a single, fully autonomous offering. → **Learn more:** [#anaas-autonomous-node-as-a-service](#anaas-autonomous-node-as-a-service "mention") *** ### Service Governance All services are: * Defined by HPEC DAO * Executed on DAO-governed Node Factories * Monitored through CMHPEC * Monetized transparently * Subject to DAO-approved rules and upgrades No single operator controls service definition or execution. *** ### Summary HPEC DAO services: * Abstract infrastructure complexity * Eliminate manual operations * Preserve decentralization * Align incentives through governance Services are **composable, autonomous, and DAO-native**. --- # 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.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.