> For the complete documentation index, see [llms.txt](https://docs.cerebrum.dev/cerebrum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cerebrum.dev/cerebrum/product-overview/cerebrum-node.md).
# Cerebrum Node
Cerebrum Node is the interface for hardware providers to enter our network easily. This platform makes a simple way for registering GPUs as nodes, paving the way for everyone to do so-from individual enthusiasts to large data centers.
The Cerebrum Node software will be compatible with both Linux and Windows operating systems initially, followed shortly by the Mac. It will be available as a downloadable executable for the full product release, while the Beta mode will be accessed through the Cerebrum Docker account. The detailed step-by-step setup to set up his/her nodes with efficiency during our Beta Release is given in our "Cerebrum Node Setup and Registration Process" section.
**Onboarding Process**
During the onboarding process, Cerebrum runs extensive tests to ensure each node meets our standards:
1. Hardware Verification: We verify the make and operational status of the GPUs to make sure they meet the threshold requirements for network tasks..
2. Latency Testing: By geolocating the device, we test its latency to ensure that it can return requests in an efficient manner.
All new nodes are validated through our validator nodes, which by virtue of operation will 'ping' for key operational data on these nodes.
In other words, this means that in the event a GPU goes live on our network, the Cerebrum Node software ensures it dedicates all resources to the processing of network tasks exclusively. It is necessary because it maintains integrity and fairness within our rental agreements; such a guarantee means that for as long as a GPU is rented out, it is not utilized in the running of any other job that could undermine its performance on the contracted job.
**Security Measures**
The Cerebrum Node, for added reliability, will include a proof-of-work mechanism. The procedure will wring every node dry through some computational tasks in proving capability and preparedness for its effective participation in the network. This proof of work helps to ascertain that nodes are working besides preventing fraudulent acts of any form.
---
# 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.cerebrum.dev/cerebrum/product-overview/cerebrum-node.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.