> For the complete documentation index, see [llms.txt](https://help.runonrufus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.runonrufus.com/rufus-cloudbox/interface/cloud-interface.md).

# Cloud Interface

The **Cloud Interface** allows you to link (bind) your CloudBox to your Cloud account, enabling seamless cloud-based timing, storage, and remote management. When bound, the CloudBox automatically sends timing passings to the **Passing Ingestion Service** and can be monitored through the Race Manager Software and you Cloud dashboard.

This interface is divided into two sections: **RUFUS Cloud** and **Cloud Binding**.

<figure><img src="/files/0g2olabNqCYfXs5TvkXo" alt=""><figcaption><p>Cloud interface</p></figcaption></figure>

## RUFUS Cloud

This section shows the current binding status and IoT connectivity of the device.

**Fields**

* **Binding Status**: Indicates whether the CloudBox is bound to a Cloud account.
  * **Not bound** (red) → Device is not linked to a Cloud account.
  * **Bound** (green) → Device is linked and will actively send passings.
* **Device Token**: The token generated in your Cloud account for the device.
* **IoT Connection**: Displays the status of the IoT service (Connected / Disconnected). IoT transmits system health and configuration data to the Cloud every 60 seconds.
* **Passings Sent to Cloud (last session)**: Number of passings successfully uploaded to the Passing Ingestion Service during the last timing session.
* **Binding Token Field**: Paste the token obtained from cloud.runonrufus.com to bind your device.
* **Bind Device Button**: Completes the binding process.

Additional actions:

* **Open RUFUS Cloud**: Opens your Cloud account in a new window.
* **Refresh**: Updates the current binding and IoT status.

## Cloud Binding

This section explains what binding does and provides important notes.

**What binding does**

* Links this CloudBox to your Cloud account.
* Sends passings to the Cloud Timing Service whenever internet connectivity is available (Ethernet, WiFi AP-shared, or 4G).
* Allows remote monitoring and status checks from your Cloud account via IoT.

**Good to know**

* Binding/unbinding is disabled while in **Start Mode** or **Test Mode** to avoid data loss.
* Passings collected offline are forwarded to the Cloud as soon as connectivity returns (within the same session).
* Unbinding only prevents future uploads — previously sent data remains stored in your Cloud account.

## Binding Your CloudBox

1. Log into your Cloud account at cloud.runonrufus.com.
2. Generate a **binding token** from the **Devices** section.
3. Paste the token into the **Binding Token** field in the Cloud interface.
4. Click **Bind Device**.

Once bound, the CloudBox will automatically send passings to the Cloud whenever an internet connection is available.

## Unbinding Your CloudBox

1. Access the Cloud Interface in the CloudBox dashboard.
2. Click **Unbind Device**.

The device will be disconnected from your Cloud account, disabling cloud-based race management.

## Summary

The **Cloud Interface** links the CloudBox to the Cloud ecosystem, unlocking powerful remote management and secure data storage features. By binding your device, you ensure:

* **Automatic upload** of all passings to the Passing Ingestion Service.
* **Remote monitoring** through IoT integration.
* **Centralized race management** in the Race Manager Software.

Binding and unbinding is straightforward, but should be managed carefully to guarantee uninterrupted synchronization and reliable event timing.


---

# 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:

```
GET https://help.runonrufus.com/rufus-cloudbox/interface/cloud-interface.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.