Fleet — Open-Source Device Management and Security Platform

What it is

Fleet is an open-source platform for managing and securing servers, laptops, and cloud workloads at scale. It uses osquery under the hood, providing real-time visibility into your entire device fleet through SQL queries. Fleet adds a management layer with GitOps-driven policies, vulnerability detection, software inventory, and automated remediation.

IT administrators, security teams, and DevOps engineers managing hundreds or thousands of devices benefit from Fleet. It replaces fragmented endpoint management tools with a single platform that covers macOS, Windows, Linux, and cloud workloads.

How it saves time or tokens

Fleet centralizes device information that otherwise lives in separate tools. Instead of SSH-ing into machines or checking multiple dashboards, you write SQL queries against live device data. GitOps-driven policies automate compliance checks that would otherwise require manual audits. Vulnerability detection runs continuously, flagging issues before they become incidents.

How to use

1. Deploy Fleet server via Docker or the official installer
2. Install the Fleet agent (fleetd) on your devices
3. Query devices with SQL and set up policies through the web UI

Example

# Docker quickstart
git clone https://github.com/fleetdm/fleet.git
cd fleet
docker compose up -d
# Open https://localhost:8080

# Query all devices for installed Python versions
# In Fleet UI, run live query:
# SELECT name, version FROM programs WHERE name LIKE '%python%';

# Install agent on endpoints
curl -LO https://download.fleetdm.com/fleetctl
chmod +x fleetctl
./fleetctl package --type=deb --fleet-url=https://fleet.example.com --enroll-secret=YOUR_SECRET

Related on TokRepo

• AI tools for security — Browse security monitoring and management tools
• DevOps tools — Explore infrastructure management solutions

Common pitfalls

• osquery queries run on endpoints and consume CPU; avoid expensive queries (large table scans) on production servers
• Fleet server requires MySQL and Redis; plan for database sizing based on fleet size and query frequency
• Agent enrollment secrets must be rotated periodically; exposed secrets allow unauthorized devices to join