> For the complete documentation index, see [llms.txt](https://docs.clore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clore.ai/for-hosts/advanced.md).

# Advanced

Advanced configuration and features for experienced Clore.ai hosts and enterprise users.

## What's in This Section

### [Bare Metal Servers](/for-hosts/advanced/bare-metal.md)

Dedicated physical servers with full root access, no virtualization, and no power limits. Ideal for AI/ML training, HPC, 3D rendering, and high-performance workloads.

* Tier 3+ data center requirements
* Hardware specifications (64+ threads, 128GB+ RAM, NVMe)
* InfiniBand/NVLink support
* SLA 99.99% with 24/7 NOC

Want to rent bare metal instead of providing it? See [Bare Metal Rental](/for-renters/bare-metal-rental.md) for the self-serve configurator; the requirements above are for providers listing capacity.

### [HiveOS Integration](/for-hosts/advanced/hiveos-integration.md)

Connect your HiveOS-managed rigs to the Clore.ai marketplace. Run mining workloads alongside GPU rentals.

### [Clore Fleet — Mass Onboarding](/for-hosts/advanced/clore-fleet-mass-onboarding.md)

Onboard multiple servers at once using Clore Fleet. Designed for hosts with 10+ machines who need automated provisioning and management.

### [Clore Partners](/for-hosts/advanced/clore-partners-high-volume-rental-system-for-major-clients.md)

High-volume rental system for data centers and major infrastructure providers. Custom pricing, dedicated support, and enterprise SLAs.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.clore.ai/for-hosts/advanced.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.