> For the complete documentation index, see [llms.txt](https://whitepaper.usegpu.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.usegpu.app/roadmap/phase-3-gpu-operators.md). # Phase 3: GPU Operators Expand beyond project-owned hardware by allowing external GPU operators to contribute capacity and earn a share of rental revenue. Phase 3 is the planned expansion beyond the initial GPUs acquired by the treasury. Other people can contribute GPUs to the ecosystem as operators. ### Operator model ``` External GPU operator ↓ Contributes GPU capacity ↓ GPU is made available for rental ↓ Rental revenue generated ↓ Operator receives 70% of the rental fee ``` Operators are intended to receive 70% of the rental fee. The roadmap does not define the allocation of the remaining rental fee. ### Why this phase matters The intended model grows infrastructure beyond project-owned hardware. It moves the ecosystem from the first treasury-funded GPUs toward a broader operator network. Phase 3 depends on GPU infrastructure that can support operator expansion. It is a future expansion phase. Operator onboarding is not presented as current functionality, and the roadmap does not set operator counts or capacity targets. The next phase is designed to make available GPU capacity useful to developers through an inference API. --- # 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://whitepaper.usegpu.app/roadmap/phase-3-gpu-operators.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.