# Fleet Types

Microservices fleets are full-featured, allowing you to run [multiple containers](/learn/develop/multicontainer.md) and set up a [public URL](/learn/manage/actions.md#public-device-url).

{% hint style="warning" %}
As of March 2023, balena has removed the concept of fleet types, effectively enforcing that all future fleets are of type Microservices. There are still customers with essentials, classic, and legacy fleet types so we'll keep the following docs for posterity. While it is possible to provision new devices to existing essentials, legacy, and classic fleets, it is not possible to create new fleets of these types.
{% endhint %}

## Essentials, Classic, and Legacy (sunset)

Essentials, classic, and legacy fleets allow you to run a single container and do not permit public device URLs. The classic and legacy fleet types allow for fleets that don't meet the requirements for new fleet types. Classic fleets support devices with balenaOS v2.0.3 and above, and legacy fleets support all earlier balenaOS versions. Classic fleets use Docker Registry V2, whereas legacy fleets use the slower and less reliable Registry V1. New classic fleets can only be created for device types that do not yet have balenaOS v2.12.0 or higher available. However, for supported device types, you can convert an essentials, classic, and legacy fleet to a microservices fleet, as described below.

{% hint style="warning" %}
All devices microservice and essentials fleets must run balenaOS v2.12.0 or higher. If you do not have the option to choose one of these fleet types, the selected device type does not yet have a high enough balenaOS version available. A classic fleet type will be assigned by default.
{% endhint %}

## Converting to Microservices

Existing fleets can be converted to Microservices, as long as all devices belonging to that fleet meet the OS version requirements, and the account has appropriate privileges.

To convert your fleet, first be sure all devices meet the balenaOS version requirements for the desired fleet type, [updating](/reference/os/updates/self-service.md) if necessary. Then, from the fleet summary page, click *Settings*, and scroll down to the *Fleet type* section. Select the fleet type you would like to convert to from the dropdown. If your fleet cannot be converted to the selected type, you will see it marked as unavailable.


---

# Agent Instructions: 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://docs.balena.io/learn/accounts/fleet-types.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.