A fleet encapsulates a set of regions, locations, providers, profiles, and scaling settings applied to compute availability (bare-metal and cloud instances). Fleets allow you to manage multiple environments with unique settings for each region while maintaining a core template. For example, you may have a separate fleet for each of your development environments (e.g., production, staging, development) or for each of the platforms your game supports (e.g., PC, Xbox, PlayStation).
Each fleet has one or more fleet regions by which you can manage machines more granularly. Fleet regions will inherit any unspecified settings from its parent fleet.
A note on compute availability
There is no delineation between bare-metal machines and cloud instances when interacting with our API. Instead, our orchestration platform determines which type of compute availability based on the fleet configuration, compute cost, instance types, locations, and network performance.