FleetDM-Automation
CptOfEvilMinions/FleetDM-AutomationReviewed by AI
Checked by RepoPicks Radar on
What is FleetDM-Automation?
This is not a program but a set of recipes written by one person: Docker Compose files and Ansible playbooks that install Fleet, the web console for osquery, together with MySQL, Redis and an NGINX front end. With it an administrator gets a server that asks every enrolled Windows or Linux machine questions about its software, settings and running processes, and there are extra playbooks to install the osquery agent on those machines. The README points to the author's blog post for the full guide. Built for Ubuntu Server 20.04.
FleetDM-Automation is free and open source (MIT) and can replace Kolide.
How easy is it to install FleetDM-Automation?
E · developers only · Linux
Administrators only, and Linux is the single target, so there is one grade: you install Docker (or Ansible 2.11 and an Ubuntu 20.04 server), generate your own TLS certificate with openssl, invent a JWT key and database passwords, edit hosts.ini and the group variables, then run docker-compose, a Docker Swarm stack or "ansible-playbook -i hosts.ini deploy_fleetdm.yml". There is no interface and no installer.
Coming soon: install in 1 click with the RepoPicks app.
FleetDM-Automation on GitHub
- Stars
- 60on Nov 10, 2026
- Downloads
- —all releases
- Growth
- —no gain in the last reading
Stars over time
Facts
- Runs on
- Linux
- You need to install
- Docker, Other tools
- To build from source
- Docker
- Disk space
- not determined
- Accounts or keys
- None
- Cost
- Free · These recipes are MIT licensed and free. Fleet, the software they install, is open source but its maker also sells a paid tier, so the newer paid features are not part of what you get here.
- License
- MIT (Permissive)
- Can replace
- Kolide
- Last change on GitHub
- Mar 20, 2022
FleetDM-Automation risk signals (6)
- Attentionstale releases
Last release on 2022-03-20 (1690 days ago)
automatic check
- Attentiontest keys and certificate are in the repository
The README says "This project has a pre-defined JWT key of `super_secret_key_here` which should ONLY BE used for testing" and "This project contains with a self-signed OpenSSL ceretificate which should ONLY BE used for testing", with conf/tls/fleet.crt and conf/tls/fleet.key read straight out of the repository by the compose files. A .env file is also committed at the top level. Deployed as it comes, the login keys and the private key are public knowledge.
AI review
- Attentionpinned to 2022 versions and untouched since
The compose files pin fleetdm/fleet:v4.11.0, mysql:8.0.27, redis:6.2.6-alpine and nginx:1.21.6-alpine, and "Versions supported" lists "Fleet FleetDM v4.11.0+", "Ansible v2.11+" and "Ubuntu server 20.04". The last commit is from 2022-03-20, so everything here is four years behind the software it installs, including its security fixes.
AI review
- Infothe server sees everything on every machine
The repository also carries deploy_osquery_linux.yml and deploy_osquery_windows.yml, which put the osquery agent on the machines to be watched. Whoever reaches the Fleet console can then ask those computers questions about installed software, users and running processes, so the console needs the same care as any administrator tool.
AI review
- Infosettings look like a home lab
The Traefik file routes "Host(`fleet.hackinglab.local`)", the plain compose file publishes 8000:80 and 8443:443, and the Fleet container is capped at "memory: 100M". These are the author's lab values, not sizing for a real fleet of computers.
AI review
- Infoinstructions live on a blog
The README says "For a complete setup guide see my blog post here", pointing at a 2021 article about FleetDM v3.6.0 — an older version than the one pinned here. The reference list at the end also finishes with several empty entries ("* []()"), so the written documentation inside the repository is thin.
AI review
Evidence is shown in its original language.
What Radar could not check about FleetDM-Automation
- Whether any of it still works with a current Fleet release, a current MySQL or a newer Ubuntu
- Whether the Ansible roles leave a working server, since there is nothing here to test them against
- What the committed .env and config files contain besides the test keys named in the README
- How much memory and disk a real fleet of machines needs, which the lab limits do not answer
- Whether the osquery agent playbooks still match today's osquery packages