// the find
grokability/snipe-it
A free open source IT asset/license management system
Snipe-IT is a mature, self-hosted IT asset management system for tracking hardware, software licenses, accessories, and consumables. Built on Laravel 11, it's aimed at IT ops teams who need to know what equipment exists, who has it, and when licenses expire. It's been around long enough to have a real ecosystem of third-party integrations.
- Full REST API with transformers for every resource type, making it straightforward to integrate with MDM tools, Jamf, Kandji, LDAP, etc. — the ecosystem of community sync scripts reflects real-world adoption.
- Actively maintained on a recent Laravel version (11) with CI running against MySQL, PostgreSQL, and SQLite, plus CodeQL scanning and accessibility checks (pa11y). This is more than most FOSS projects bother with.
- Solid auth story: LDAP sync with troubleshooter tooling, SAML support, 2FA, Google OAuth, and a dedicated security contact — appropriate for enterprise IT environments.
- The console commands list reveals years of real operational experience: key rotation, double-escape fixes, mismatched log repair, session kill-switch. These aren't features you add speculatively.
- The codebase shows signs of accumulated complexity — multiple overlapping 'Fix*' and 'Migrate*' console commands suggest data model decisions that weren't fully baked the first time and required corrective one-off scripts that now live permanently in the codebase.
- No native mobile app yet despite being a barcode/QR-scan-heavy workflow tool. You're depending on third-party apps of varying quality and maintenance status, which is a real gap for warehouse or field asset scanning.
- Livewire is used only in a handful of forms while the rest of the UI is server-rendered Blade — the frontend architecture is inconsistent, which makes contributing to the UI confusing and limits reactivity in bulk operations.
- The Docker setup ships multiple Dockerfiles (ubuntu, alpine, fpm-alpine) with no clear guidance on which is production-recommended, and the .env file zoo (.env.dev.docker, .env.docker, .env.dusk.example, .env.tests, .env.unit-tests) will confuse anyone setting this up for the first time.