CUPSvsFleet
Two self-hosted Device Management projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| CUPS | Fleet | |
|---|---|---|
| Score | 67/100 | 67/100 |
| Rank in category | #1 of 11 in Device Management | #1 of 11 in Device Management |
| GitHub stars | 1 787 | 7 063 |
| Stars, last 30 days | +34 | — |
| Stable releases, 12 months | 6 | 3 |
| Latest release | v2.4.20 · 5 Oct 2026 | fleet-v4.93.2 · 21 Oct 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | No | No |
| License | Apache-2.0 | Other |
| Main language | C | Go |
Which one should you pick?
CUPS and Fleet score the same (67/100), so the choice comes down to the details below.
CUPS ships more often: 6 stable releases in the past year, against 3 for Fleet.
If you want the quickest setup, CUPS is easier to run; Fleet needs more configuration.
CUPS is growing faster right now (+34 stars in 30 days).
CUPS details →Fleet details →All Device Management projects →
Swap a project
Keep CUPS, compare it with
Keep Fleet, compare it with