Updates why-fleet.md to better reflect how Fleet is used today. Resolves https://docs.google.com/document/d/1rroNFfb8j8zGJdkZX1wUKuzXv3Kh-VNlFeN7P8kTtT8/edit?usp=sharing Changes: - Removed "Managing computers today is getting harder," the middleman framing, and the universal remote analogy from "What's it for?" - Added diagnostics and audit use cases to "Get what you need." - Called out IaC/GitOps directly in "Out of the box," with a link to the YAML files configuration docs. - Added a mention of the Fleet MCP server and AI-powered chat workflows in "Out of the box." - Added a link to GitOps workshops in "Out of the box," where IaC is introduced. - Trimmed "Good neighbors" to its core point: Fleet is independent, open by design, and committed to osquery. - Removed the extra dashes from "Scope transparency." - De-emphasized Chromebooks in "Scope transparency" in favor of iOS and Android. - Simplified the "Ready to get started?" section; removed the push toward "Get a demo." <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated internal code review configuration for documentation files. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Fleet documentation
Welcome to the documentation for Fleet, the lightweight management platform for laptops and servers.
You can also read the Fleet docs over at https://fleetdm.com/docs.
Using Fleet
Resources for using the Fleet UI, fleetctl CLI, and Fleet REST API.
Deploying
Resources for installing Fleet's infrastructure dependencies, configuring Fleet, deploying osquery to hosts, and viewing example deployment scenarios.
Contributing
If you're interested in interacting with the Fleet source code, you'll find information on modifying and building the code here.
If you have any questions, please don't hesitate to File a GitHub issue or join us on Slack. You can find us in the #fleet channel.