> For the complete documentation index, see [llms.txt](https://docs.nodebox.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nodebox.cloud/overview/why-use-nodebox.md). # Why use Nodebox? While it's possible to run nodes on your own, it's important to consider the following factors: **Complexity** * Setting up and managing nodes can be difficult, especially for those without extensive technical expertise * For example, you need some knowledge about UNIX, IT, DevOps, Server configuration, CLI tools, Docker, Git, programming languages and scripting * Setting up nodes from scratch can take time. **Nodebox** offers pre-configured solutions for quick deployment, saving users valuable time **Upgrades and Maintenance** * Managing nodes requires ongoing maintenance and troubleshooting * You need to follow the node project's announcements closely and update the binaries regularly * **Nodebox** handle software updates, ensuring that nodes are running the latest versions. You don't need to worry about the regular maintenance tasks associated with node operation. **Reliability** * Most nodes require close to 100% uptime, otherwise your node might get blacklisted or you won't get any rewards * You cannot just run a node on your personal computer and think that this will be enough to ensure the required level of reliability. What happens when there is electricity outage, or your OS crashes and needs rebooting, or some hardware component fails, etc? Also you need remote access to your server to manage your node properly. * **Nodebox** guarantees uptime and reliability Choosing **Nodebox** as your Node-as-a-Service provider can be a strategic decision based on factors such as expertise, resources, and the specific needs of the user or project.\ \ We pride ourselves in offering the **most competitive prices** on the market and the best support we can give to our users. --- # 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.nodebox.cloud/overview/why-use-nodebox.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.