- Can I install Snipe-IT with Composer like a normal Laravel package?
- No. Snipe-IT is a complete Laravel application, not a library, so there is no composer require path and no service provider you drop into an existing app. The Composer file exists to pull in the framework and dependencies for the application itself. If you want asset management inside your own Laravel codebase, you would have to fork it, extract the domain logic, or integrate over its REST API instead.
- What are the server requirements and how do I install Snipe-IT?
- You need PHP 8.x, MySQL or MariaDB, Composer, and a standard LAMP/LEMP or container host; Redis is optional for cache and queues. After deploying the code and running Composer and the database migrations, you also need a queue worker for mail and notifications plus the Laravel scheduler wired to cron. Those two background processes are the most commonly forgotten step and the usual cause of notifications silently not working. Uploaded files such as asset images and audit attachments must be backed up alongside the database, since database-only backups lose them.
- Is Snipe-IT free, and what does the AGPL-3.0 license mean for commercial use?
- It is free and open source under AGPL-3.0, and unmodified internal self-hosting is straightforward. The obligations trigger if you modify the code and expose it as a network service, or embed it in a commercial offering, because that can require source disclosure. Treat legal review as a hard prerequisite before any fork-and-extend or product-embedding plan, and decide up front whether this is strictly internal use.
- Does Snipe-IT have a REST API, and how does API authentication work?
- Yes, there is a REST API v1 with token authentication, where each user or service account gets an API token. CRUD coverage is solid for assets, users, licenses, and checkouts but uneven across less common entities, so verify your specific resources before designing around it. Rate limiting is global configuration rather than per-client throttling, which matters if multiple integrations share one instance. Where the API falls short, teams often resort to polling or direct database reads, both of which couple you to the schema.
- Does Snipe-IT support LDAP and SAML single sign-on?
- Both LDAP and SAML are first-class features, and enterprise SSO support is one of the main reasons organizations choose Snipe-IT over lighter asset trackers. SCIM provisioning is not native, so automated user lifecycle sync from an IdP or HRIS usually needs API glue or a scheduled job. Before rollout, agree on which system is the source of truth for user accounts to keep that sync scope small.
- Which PHP and Laravel versions does Snipe-IT require?
- Current releases target PHP 8.x and track Laravel major versions, so check the upgrade notes for the exact minimum on the release you deploy. Because it is an application rather than a package, you cannot pin an older Laravel independently of Snipe-IT itself. Releases are frequent, and Laravel major-version churn is the main upgrade friction, especially if you carry customizations.
- Can Snipe-IT be used as a multi-tenant asset management system?
- Multi-tenancy in Snipe-IT is soft, handled through the Companies scoping feature rather than hard tenant isolation. That is adequate for departmental separation inside one organization but is not a substitute for real tenant boundaries if you are building a commercial multi-tenant product on top of it. If strict isolation is a requirement, plan for separate instances rather than relying on scoping alone.
- How do I extend or customize Snipe-IT without forking it?
- There is no plugin or extension architecture, so behavioral changes mean editing the source, and every version upgrade becomes a merge project. The lower-risk paths are configuration, custom fields, and integrations that run outside the application against the REST API or webhooks. If customization is unavoidable, assign clear ownership of the fork and budget maintenance time for each upstream release. Some capability gaps can also be closed with Grokability commercial support or hosted options contracted separately.
- Are Snipe-IT webhooks reliable enough for production event handling?
- Webhooks cover the meaningful events such as checkout, check-in, audit, and license seat changes, with Slack, Teams, Google Chat, and custom targets. Delivery is fire-and-forget, however, with no guaranteed retries or dead-letter queue, so treat it as best-effort notification rather than a reliable event bus. For anything that must not be dropped, poll the API or reconcile on a schedule instead of depending on webhook delivery.
- Is Snipe-IT actively maintained, and what are the alternatives?
- Snipe-IT is actively maintained with frequent releases, and commercial support or hosting is available from Grokability under a separate contract since the community edition has no vendor SLA. Alternatives depend on your reason for looking: lighter self-hosted inventory tools if you do not need LDAP or SAML, or a SaaS CMDB if you do not want to own hosting and upgrades. If API depth, guaranteed event delivery, or true multi-tenancy are hard requirements, evaluate dedicated ITSM or CMDB platforms before committing to the fork-and-maintain route.