> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/scalability/separating-nodes-from-hardware.md). # Separating Nodes from Hardware Keeta's architecture separates [nodes](/components/nodes.md) from servers, allowing multiple servers to support a single node. This design enables both vertical and horizontal scaling without downtime, maintaining consistent transaction throughput under heavy loads and avoiding common network bottlenecks. Unlike traditional blockchain systems where nodes and servers are combined—requiring nodes to go offline for hardware upgrades—Keeta's approach permits hardware upgrades while keeping the network operational. This method delivers high performance without compromising decentralization or efficiency. By decoupling nodes from the underlying hardware, Keeta ensures that scaling and upgrades can be performed without disrupting network availability. This flexible architecture sets Keeta apart from competitors, providing continuous operation at full capacity during expansion or maintenance activities.

By separating nodes from servers, Keeta Network delivers high performance without compromising decentralization or efficiency.

--- # 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://docs.keeta.com/scalability/separating-nodes-from-hardware.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.