Andrey Kizimenko
7d855287aa
**Related issue:** N/A — internal update to the release-QA issue template # Description Updates the **Release QA** issue template (`.github/ISSUE_TEMPLATE/release-qa.md`) to match current product group naming and to tighten the release-critical issue gate. Changes: - **Renamed product group sections** to match the working-group names in `handbook/company/product-groups.md`: **MDM → Apple at Work** and **Software → Auto Patching**. - **Moved OS updates and disk encryption checks** out of Security & Compliance to the platform-owning groups: - macOS OS updates + disk encryption → **Apple at Work** - Windows OS updates + disk encryption → **Power to PC** - Linux disk encryption stays in **Security & Compliance** - Per-section Fleet Free premium-gating lists updated to follow the moves. - **Consolidated the release-critical issue check** into a single "Ready for release" gate covering both `~unreleased bug` (regressions introduced during the cycle — the most critical to clear) and `~release blocker` labels. Every such issue must have a milestone, an owner, and be moved to "Ready for release" on its product group board before the release can proceed. - **Removed non-functional in-issue anchor links.** GitHub only generates heading anchors when rendering Markdown as a repo file/wiki/Discussion, not inside issue bodies, so the previous `#notes`-style links silently did nothing once the template became an issue. # Checklist for submitter - [ ] ~Changes file added for user-visible changes~ — N/A, internal QA issue template only (no user-visible product change). ## Testing This is a docs-only change to a GitHub issue template; no code paths are affected. - [x] QA'd all new/changed functionality manually (verified rendered Markdown, section structure, and label-filter links).
News · Report a bug · Docs · Why open source? · Art
Open-source platform for IT and security teams with thousands of computers. Designed for APIs, GitOps, webhooks, YAML, and humans.
What's it for?
Fleet gives you a single system to secure and maintain all your computing devices over the air. You can do MDM, patch stuff, deploy software, and verify anything, all from one place, across every OS your organization uses.
Fleet works directly with data and events from the native operating system, down to the bare metal. Strong diagnostics let you investigate errors on end-user devices and collect accurate audit evidence in minutes.
Get started
You can try Fleet out for yourself, or grab time with one of the maintainers to chat.
Is it any good?
Fleet is used in production by IT and security teams managing thousands of devices. Many deployments support tens of thousands of hosts, and a few large organizations manage 400,000 or more.
Supported platforms
- Linux (all distros)
- macOS
- Windows
- Chromebooks
- iOS and Android (BYOD or corporate-owned)
- Amazon Web Services (AWS)
- Google Cloud (GCP)
- Azure (Microsoft cloud)
- Data centers
- Containers (kube, etc)
- Linux-based IoT devices
Infrastructure as code
Manage your fleet with GitOps, or use the GUI, REST API, webhook events, and the fleetctl command-line tool.
Linux support
First-class support for all major distros. Linux gets the same attention and visibility as macOS and Windows.
Visibility and compliance
Fleet can report on hundreds of attributes across your devices and ships with CIS benchmarks for macOS and Windows and comprehensive operating system, hardware, and software data. Check out the table reference documentation to see what's available.
Open by design
Fleet is open source and transparent about what it can and can't see. End users can verify exactly how the agent works and what data their company collects. Fleet collects only the data needed to manage and secure devices, not private activity like keystrokes, emails, or webcams.
Good neighbors
Ready-to-use, enterprise-friendly integrations exist for Snowflake, Splunk, GitHub Actions, Vanta, Elastic Jira, Zendesk, and more. Fleet also works with tools such as Munki, Chef, Puppet, Ansible, CrowdStrike, and SentinelOne.
Lighter than air
Fleet is lightweight and modular. You can use it for MDM without using it for security, and vice versa. You can turn off features you are not using.
Free as in free
The free version of Fleet will always be free. Fleet is independently backed and actively maintained with the help of many amazing contributors.
Longevity
The company behind Fleet is founded (and majority-owned) by true believers in open source. The company's business model is influenced by GitLab (NYSE: GTLB), with great investors, happy customers, and the capacity to become profitable at any time.
Fleet Device Management's company handbook is public and open source. You can read about the history of Fleet and our commitment to improving the product.
Chat
The Fleet community is full of kind and helpful people. Whether or not you are a paying customer, if you need help, just reach out.
Contributing 
Contributions are welcome, whether you answer questions on Slack / GitHub / LinkedIn, improve the documentation or website, write a tutorial, give a talk at a conference or local meetup, give an interview on a podcast, troubleshoot reported issues, or submit a patch. The Fleet code of conduct is on GitHub.
License
The free version of Fleet is available under the MIT license. The commercial license is also designed to allow contributions to paid features for users whose employment agreements allow them to contribute to open source projects. (See LICENSE.md for details.)
Fleet is built on osquery, nanoMDM, Nudge, and swiftDialog.