> 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/gpu-infrastructure/gpu-deployment.md).

# GPU Deployment

Examine the planned first GPU deployment, verification approach, hosting information, operational reporting, and transition toward GPU-backed infrastructure.

Phase 1 has no GPUs. The first hardware deployment is planned for Phase 2, which the roadmap targets for one month after launch.

### Planned deployment

| Roadmap target           | Detail                                 |
| ------------------------ | -------------------------------------- |
| Hardware                 | 2 × NVIDIA RTX 4090 units              |
| Approximate target price | $2,000 per GPU                         |
| Purpose                  | Establish the first physical GPU layer |

These are roadmap targets. The hardware is not presented as purchased or deployed, and the target price is not a guaranteed future purchase price.

### Planned visibility and reporting

The project plans to publish deployment information and recurring operational reports.

| Item                   | Intended purpose                                              |
| ---------------------- | ------------------------------------------------------------- |
| GPU serial numbers     | Identify the specific hardware associated with the deployment |
| GPU photographs        | Provide visible evidence of the physical hardware             |
| Hosting location       | Identify where the hardware is hosted                         |
| Monthly uptime reports | Provide an operational view of availability over time         |
| Utilization reports    | Provide an operational view of how the hardware is used       |

These items describe the planned reporting approach. They do not establish cryptographic hardware attestation or third-party verification.

### GPU-powered to GPU-backed

During Phase 1, USE-GPU is described as **GPU-powered**. GPU infrastructure is the intended direction, but no physical GPUs are present.

Once the Phase 2 hardware is live and generating rental revenue, the project intends to use **GPU-backed**. This change reflects live physical infrastructure and rental activity. It is not a formal certification.

### Planned admin renounce

An admin exists in Phase 1. Phase 2 includes a planned permanent admin renounce. The program is intended to operate without the project's administrative control after renunciation.

The roadmap does not define the technical implementation of the renounce.

### Hardware reference

The NVIDIA RTX 4090 is the roadmap's hardware target only. USE-GPU is not affiliated with NVIDIA, and no partnership, endorsement, sponsorship, or procurement relationship is implied.


---

# 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/gpu-infrastructure/gpu-deployment.md?ask=<question>&goal=<endgoal>
```

`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.
