> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/general-render-network/what-role-am-i/how-to-get-started-1.md). # How to get started as a Node Operator Joining the network, setting up your node and understanding Render Network To join the network as a node operator, complete the [Render Network Interest Form](https://renderfoundation.com/gpu)[ ](https://renderfoundation.com/gpu)and you will be added to the on-boarding queue. When your node is ready to be added, The Render Network Team will follow up with more on-boarding information. ## Recommended Hardware Please see [**Hardware FAQs**](https://help.otoy.com/hc/en-us/articles/360054367272-Hardware-Guide-for-OctaneRender) for more detailed hardware information, while general recommendations are: * A CUDA-enabled NVIDIA® GPU and a minimum of CUDA® 10.1 [drivers](https://www.nvidia.com/download/index.aspx?lang=en-us) with support for [compute capability 3.0 or higher](https://www.nvidia.com/download/index.aspx?lang=en-ushttps://developer.nvidia.com/cuda-gpus) (the minimum driver version is 566.36). We recommend a minimum 6GB of VRAM, and 8+GB VRAM is preferred. Higher VRAM is key to better performance on the network. * 32+ GB System Memory (RAM) is a recommended minimum with more RAM helping your node process more complex scenes. * Strong Network Connectivity is required to download and upload assets. * 100GB Free Disk Space is recommended. SSDs and non-mechanical hard drives are also preferred for faster read/write speeds. Render Network uses a node's C-Drive, so if you have multiple drives, please use the faster Drive or SSD as the Temp Folder in the C-Drive, and ensure there is sufficient space. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://know.rendernetwork.com/general-render-network/what-role-am-i/how-to-get-started-1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.