> 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/clore-fleet-mass-onboarding.md).

# Clore Fleet (Mass onboarding)

Onboard any number of machines with one identical command

Mass onboarding lets you bring an entire fleet onto Clore.ai without creating servers one by one. Every machine runs the **same** command (or receives the same flight sheet), installs the hosting agent, detects its own hardware, and self-registers to your account — Ubuntu boxes appear as `LINUX_<machine-id>`, HiveOS rigs as `<worker>_HIVE_<rig-id>`.

Open [My Servers](https://clore.ai/my-servers) → **Add Server** → **Mass** and pick your operating system. The dashboard generates everything below with your personal fleet token already filled in.

{% hint style="danger" %}
**Do NOT run the mass-onboarding command on machines that are already listed on Clore.ai.** The machine re-registers under a new auto-generated name, the original server entry goes dead, and any active customer order on it is cancelled. Use it only on fresh machines (the HiveOS flight-sheet path is safe on rigs that already carry a Clore token — it only onboards machines that don't have one yet).
{% endhint %}

{% hint style="warning" %}
The generated command contains your personal onboarding token. **Never share it** — it allows registering machines to your account.
{% endhint %}

## Defaults

Each self-registered machine starts with the same settings as the Quick add-server command: max rental length 300 hours, USD autopricing at $5 per server per day for on-demand and spot. Adjust any of it later in bulk from the dashboard: **My Servers → select servers → Change selected**.

## Ubuntu fleets

The core of every method is one identical command (run as root):

```bash
bash <(curl -s https://gitlab.com/cloreai-public/hosting-agent-installer/-/raw/main/install.sh) --onboarding-config <your-fleet-token>
```

The dashboard offers three ready-made ways to deliver it to many machines:

### Cloud (cloud-init)

For cloud instances or automated provisioning: copy the generated `user-data` snippet into your provider's cloud-init field, or build a NoCloud seed ISO from the downloaded `user-data` + `meta-data` files:

```bash
cloud-localds seed.iso user-data meta-data
```

(or `genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data`)

The `user-data` contains your onboarding token. After the machines register, detach/delete the seed ISO or clear the stored user-data (`cloud-init clean --logs`) so the token doesn't linger on disk or in instance metadata.

### SSH loop

Paste your machines' IPs into the form and it generates a loop you run from your workstation:

```bash
for ip in <ip-1> <ip-2>; do
  ssh -i ~/.ssh/id_rsa root@$ip '<onboarding command>'
done
```

### Ansible

The form generates an `onboard.yml` playbook and an example `hosts` inventory; run it with:

```bash
ansible-playbook -i hosts onboard.yml
```

## HiveOS fleets

No shell needed — onboarding rides on a flight sheet:

1. In the dashboard's Mass onboarding → HiveOS tab, copy the generated **Flightsheet** JSON and import it in HiveOS via **Import from Clipboard** when creating a new flight sheet.
2. Copy the generated **Wallet** value and set it as the wallet for that flight sheet — this is your onboarding token.
3. Apply the flight sheet to any number of rigs. Each rig installs the hosting agent, self-registers, and from then on is managed from the Clore.ai dashboard like any other server (the flight sheet is no longer needed for management).

For single-rig HiveOS onboarding through your HiveOS account link, see [HiveOS Integration](/for-hosts/advanced/hiveos-integration.md).


---

# 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.clore.ai/for-hosts/advanced/clore-fleet-mass-onboarding.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.