> For the complete documentation index, see [llms.txt](https://docs.mobiusflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobiusflow.com/help/user-guides/deploying-mobiusflow-on-prem/deploying-mobiusflow-to-approved-hardware-using-balenacloud/creating-a-fleet.md).
# Creating a Fleet
Create a new balenaCloud fleet
After signing up to [balenaCloud](https://www.balena.io/cloud) follow their instructions to create a fleet and add your first device. We have simplified the process so you will only need to perform some of the actions they list. The steps below outline the process but for more information see the balena.io [documentation](https://docs.balena.io/learn/getting-started/raspberrypi3/nodejs/#create-a-fleet).
## What You Will Need?
{% hint style="info" %}
This guide assumes you will be using a Raspberry Pi 4. The instructions are the same for the UP and Intel NUC devices with the exception of loading the initial balenaOS onto your device.
{% endhint %}
1. A **balenaCloud account** with Microservices access (this requires a paid account)
## Creating a New Fleet
{% hint style="info" %}
A fleet is a collection of devices with the same device type (or architecture). Fleets allow simple management of a group of devices
{% endhint %}
Navigate to your [balenaCloud dashboard](https://dashboard.balena-cloud.com/?) and login in
Navigate to the **Fleets** page
Click on the **Create Fleet** button
Create your first Fleet
Enter a fleet **name**
Choose device type **Raspberry Pi 4 (using 64bit OS)**
Select fleet type **Microservices**
Click on the **Create new fleet** button
Create new fleet details
You have created your first balenaCloud fleet! Now go to [Adding Your First Device](/help/user-guides/deploying-mobiusflow-on-prem/deploying-mobiusflow-to-approved-hardware-using-balenacloud/adding-your-first-device.md) to add a device to this fleet
---
# 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.mobiusflow.com/help/user-guides/deploying-mobiusflow-on-prem/deploying-mobiusflow-to-approved-hardware-using-balenacloud/creating-a-fleet.md?ask=&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.
