Install Snipe-IT in 5 Minutes 🔥 Complete Asset Management Setup Guide

What You Need Before You Start

Snipe-IT is web software — there is no .exe file to double-click. It needs a machine to live on: an office server, a small VM, or even a spare desktop PC that stays on during office hours. Under the hood it is a Laravel application, and the documented requirements are a web server (Apache or Nginx), PHP 8.2 or newer with the standard Laravel extensions, and a MySQL or MariaDB database. Two gigabytes of RAM is a comfortable floor for a small office install.

Decide also where staff will reach it. A name like assets.office on your local network is enough — Snipe-IT does not need to face the internet.

Take the Official Docker Route

Installing PHP, a database and a web server one by one is an hour of careful typing — which is why the video takes the container route. The Snipe-IT project publishes an official Docker image, snipe/snipe-it, and the project's docker-compose.yml setup packs everything into one tested bundle: one container for Snipe-IT, one container for its MySQL database, and a data volume so your uploads survive container restarts.

So the order is simple: install Docker on your Linux server or VM first, then take the project's compose setup as your starting point.

Set the .env Values

Before starting the containers, copy the example environment file to .env and set the values Snipe-IT cannot guess: your site address (APP_URL — the exact address staff will open, such as the local name from Step 1), your timezone, and the database passwords. These few lines decide how every link the system generates will look, so get the address right the first time.

Generate the App Key and Start the Containers

With the .env values in place, generate the application encryption key inside the running Snipe-IT container:

docker exec -i -t snipeit php artisan key:generate --env=production

Then start the containers with Docker Compose and open the site address from Step 1 in your browser — Snipe-IT answers with its first-run wizard.

Run the First-Run Wizard

The first page Snipe-IT shows is a pre-flight check — PHP version, extensions, folder permissions and the database connection. Fix anything it flags before continuing; the wizard will not let a broken base through, which is a kindness. Then you create the first admin account and the company settings: company name, site name, default currency and timezone.

Spend two extra minutes in Admin > Settings right now, while it is fresh: turn on auto-incrementing asset tags if you want the system to number assets for you, set your date format, and configure the mail settings (SMTP).

The Four Building Blocks — Models, Categories, Statuses, Suppliers

Before the first asset, Snipe-IT asks for four small vocabularies, and five minutes here saves months of mess later. Asset models describe what a thing is (for example, one specific laptop model), so fifty identical laptops share one description. Categories group them — Laptops, Desktops, Phones, Printers. Status labels say what state an asset is in — Ready to Deploy, Deployed, In Repair, Archived are the heartbeat of the whole system. Suppliers record who sold it to you, which the warranty and repair pages lean on later.

Your First Asset and First Checkout

Now the register goes live. Create an asset: pick its model, give it a unique asset tag (the system generates one if auto-increment is on), and type the serial number, purchase date, purchase cost and warranty period. Add the person first if they are not in the system yet — the People section takes a name, username, email and department.

Then the act the entire system exists for — checkout. Choose the person, set an expected return date if there is one, and save. That laptop is now recorded as being in that person's custody, with a timestamp, in an audit history nobody can quietly rewrite.