Welcome to the documentation for Fleet, the lightweight management platform for laptops and servers.
Can't find what you're looking for? Support
{{thisPage.title}}
On this page:
Fleet offers managed cloud hosting for Fleet Premium customers with large deployments.
While organizations of all kinds use Fleet, from Fortune 500 companies to school districts to hobbyists, today we are only currently able to provide fully-managed hosting for deployments larger than 300 hosts. (Instead, you can buy a license and self-host Fleet Premium with support.)
Fleet is simple enough to spin up for yourself. Premium features are available either way.
Take a look at Deploying Fleet for guides on Render or deploy for scale with AWS Terraform. You can also deploy Fleet anywhere you want.
You can enroll servers and laptops using a simple installer or automatically deliver Fleet's agent (fleetd) using your existing tools, such as Chef, Terraform, Munki/autopkg, Ansible, Puppet, Jamf, Intune, etc. As of Fleet v4.53.0, when Fleet's MDM is enabled for MacOS, fleetd is installed as part of the bootstrap.
By default, Fleet keeps fleetd up to date automatically. For self-managed instances, Fleet provides a Simple upgrade process.
Fleet lets you define role-based access controls, the ability to assign different admins for different groups of hosts, and rolling deployments. Fleet has built-in audit logging (accessed through API or streamed to a data lake.)
In addition, you can do GitOps because you can control your Fleet instance through a git repo, allowing you to use your standard CI/CD and approval process. This also tracks the history of changes as commits.
Fleet comes with a built-in query library for reporting device health and also includes over 400 optional built-in CIS policies for Mac and Windows.
You can easily write queries yourself with query auto-complete, as well as import query packs for HID to detect IOCs using Yara or other intrusion detection mechanisms from the community or other vendors. Or, you can import policies to monitor for high-impact vulnerabilities such as a particular TPM chip; for example, a large vehicle manufacturer uses Fleet to do this.
Customers can build on these built-in policies to monitor ongoing compliance with regulatory standards like NIST, PCI, ISO, SOC, and HIPAA.
Fleet is used in production deployments with hundreds of thousands of hosts and has been stress-tested to 150,000 online and 400,000 total enrolled hosts.
It’s standard deployment practice to have multiple Fleet servers behind a load balancer. However, the MySQL database is typically the performance bottleneck and a single Fleet server can handle tens of thousands of hosts.
Unlike legacy systems, Fleet gives you complete control over how frequent and labor-intensive the scanning is.
When you collect data with Fleet, the performance impact is automatically reported. You can analyze CPU, memory, and network usage or just compare whether a query's performance impact is “minimal,” “considerable,” or “excessive.” You can easily compare the average performance of a scan across all systems or troubleshoot performance on an individual host. If one of your queries gets too rowdy on a particular host, Fleet will temporarily disable it.
You can test changes on a small subset of hosts first, then roll them out to the rest of your organization.
Fleet supports the latest, stable releases of all major browsers and platforms.
We test each browser on Windows whenever possible, because our engineering team primarily uses macOS.
Note: This information also applies to fleetdm.com.
- Mobile web is not yet supported in the Fleet product.
- The Fleet user interface may not be fully supported in Google Chrome when the browser is running on ChromeOS.
Fleet supports the following operating system versions on hosts.
OS | Supported version(s) |
---|---|
macOS | 13+ (Ventura) |
iOS/iPadOS | 17+ |
Windows | Pro and Enterprise 10+, Server 2012+ |
Linux | CentOS 7.1+, Ubuntu 20.04+, Fedora 38+, Debian 11+ |
ChromeOS | 112.0.5615.134+ |
While Fleet may still function partially or fully with OS versions older than those above, Fleet does not actively test against unsupported versions and does not pursue bugs on them.
Not all osquery tables are available for every OS. Please check out the osquery schema for detailed information.
If a table is not available for your host, Fleet will generally handle things behind the scenes for you.
Fleet Desktop is supported on Ubuntu and Fedora.
Fedora and some flavors of Ubuntu (e.g. Kubuntu) require a gnome extension and Google Chrome for Fleet Desktop.
Fleet's default (un)install scripts use apt-get
for Debian-based distributions, and dnf
for Red Hat-based distributions. To install packages on CentOS versions prior to 8, either add dnf
or edit install and uninstall scripts to use the yum
or rpm
command.
On Ubuntu, Fleet Desktop currently supports Xorg as X11 server, Wayland is currently not supported. Ubuntu 24.04 comes with Wayland enabled by default. To use X11 instead of Wayland you can set WaylandEnable=false
in /etc/gdm3/custom.conf
and reboot.
The fleetctl package
command is not supported on DISA-STIG distribution.
Different portions of the Fleet software are licensed differently, as noted in the LICENSE file. The majority of Fleet is MIT licensed. Paid features require a license key.
When a feature is free and open source we won't move that feature to a paid tier. Features might be removed from the open source codebase in other cases, for example when combining features from multiple tiers into one new feature.
The majority of new capabilities added to Fleet will benefit all users, not just customers.
We won't introduce features into the open source codebase with a fixed delay; if a feature is planned to land in both it will be released simultaneously in both.
We will always release and open source all tests that we have for any open source feature.
The free version of Fleet is enterprise ready.
The open source codebase will not contain any artificial limits on the number of hosts, users, size, or performance.
The majority of new features contributed by Fleet Device Management Inc will be open source.
The product will be available for download without leaving an email address or logging in.
We will always allow you to benchmark the performance of Fleet. (Fleet also load tests the platform before every release, with increasingly ambitious targets. The scale of real time reporting supported by Fleet has increased 5,000% since 2019. Today, Fleet deployments support 500,000 devices, and counting. The company is committed to driving this number to 1M+, and beyond.)
A lot of questions can be answered in the documentation or guides.
To get help from the community, visit https://fleetdm.com/support.
If your organization has Fleet Premium, you can access professional support with a guaranteed response time.
If you opt not to renew Fleet Premium, you can continue using only the free capabilities of Fleet (same code base, just unconfigure the license key.)
We aren’t able to sell licenses and support separately.
For now, the number of hosts is the maximum cap of hosts enrolled at any given time. Umanaged hosts ("Pending" MDM status in Fleet) are not included in the enrolled hosts count.
Like any modern application, Fleet scales horizontally. The biggest potential bottleneck for Fleet is the number of hosts being monitored, so that's where we've devoted the most attention when testing. The largest number of hosts we've had a customer ask about was 350,000, for all of the production servers and employee laptops of a publicly traded company.
Since Fleet is self-managed, some metadata is stored wherever it is deployed (e.g. Amazon, Azure, Google, your own data center, hybrid cloud, anywhere). That's done using a MySQL database, but the bulk of the data flows directly into a tool like Splunk or ElasticSearch. You can send that information to any of Fleet's supported log destinations.
Potentially! Fleet is open core with a source code license similar to GitLab's.
Anyone is free to contribute to the free or paid features of the project. We are always interested to hear feedback, and we are happy to take pull requests and ideas upstream any time we can.
The only way we are able to partner as a business to provide support and build new open source and paid features is through customers purchasing Fleet Premium.
To uninstall Fleet's agent (fleetd), follow the instructions here.
Back to top