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, we are only currently able to provide cost-effective hosting for deployments larger than 1000 hosts. (Instead, you can buy a license and self-host Fleet Premium with support.)
Fleet provides a standard Terraform module that deploys Fleet with best practices, along with cloud cost calculators and reference architectures used by some of Fleet’s largest customers with tens and hundreds of thousands of hosts. Fleet Premium customers can also opt for managed hosting provided by Fleet. You can also deploy Fleet anywhere you want.
You can enroll servers and laptops using a simple installer or automatically deliver the agent using your existing tools, such as Chef, Terraform, Munki/autopkg, Ansible, Puppet, Jamf, Intune, etc.
By default, Fleet keeps agents up to date automatically. For self-managed instances, Fleet provides a migration runner.
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.
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 regulator 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.
We have different licenses for portions of our software which are noted in the LICENSE file in our docs. 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 realtime reporting supported by Fleet has increased 5,000% since 2019. Today, Fleet deployments supports 500,000 devices, and counting. The company is committed to driving this number to 1M+, and beyond.)
For community support, 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 distinct agents enrolled at any given time.
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.
If you notice something we've missed or could be improved on, please follow this link and submit a pull request to the Fleet repo.
Back to top