Self-Host 40+ Dev Tools Locally with One Docker Command

// Before you start

What you need

Docker installed and running on your machine (Mac, Windows, or Linux)
A terminal or command prompt you can open
Port 8080 free on your machine (nothing else using it)

Step 1 of 5

Confirm Docker is running

1 min

Before pulling anything, make sure Docker is actually running. If Docker Desktop is installed but not open, the next steps will fail with a confusing error. This command prints the Docker version — if it responds, you are good to go.

Terminal · mac

$ docker --version

What you should see

Docker version 24.x.x, build xxxxxxx (any version number is fine)

This might happen

Command not found or 'Cannot connect to the Docker daemon'

Open Docker Desktop first, wait for it to finish starting (the whale icon in your taskbar stops animating), then try again.

Step 2 of 5

Pull and start the it-tools container

3 min

This single command downloads the pre-built it-tools image from Docker Hub and starts it as a background service. The flags mean: run in the background (-d), name it 'it-tools', restart it automatically if your machine reboots (--restart unless-stopped), and make it reachable on port 8080 of your machine (-p 8080:80).

Terminal · mac

$ docker run -d --name it-tools --restart unless-stopped -p 8080:80 corentinth/it-tools:latest

What you should see

A long string of letters and numbers (the container ID), e.g.: a3f8c2d1e9b7...

This might happen

'Bind for 0.0.0.0:8080 failed: port is already allocated'

Something else is using port 8080. Change the left side of the port flag to a free port, e.g. -p 9090:80, then open http://localhost:9090 instead.

Step 3 of 5

Verify the container is running

1 min

This command lists all running containers. You should see 'it-tools' in the list with a status of 'Up'. If it shows 'Exited', something went wrong during startup and you can check the logs in the next step.

Terminal · mac

$ docker ps --filter name=it-tools

What you should see

A table row showing: it-tools ... Up X seconds ... 0.0.0.0:8080->80/tcp

This might happen

Status shows 'Exited' instead of 'Up'

Run: docker logs it-tools — to see the error message. Most often it is a port conflict; see the fix in Step 2.

Step 4 of 5

Open it-tools in your browser

1 min

The app is now running locally. Open your browser and go to the address below. You will see the full it-tools interface with all utilities listed — no login, no account needed.

Terminal · mac

$ open http://localhost:8080

What you should see

The it-tools homepage loads in your browser showing a grid of developer tools like 'Token generator', 'Hash text', 'JWT parser', and many more.

This might happen

'open' is not a recognized command on Windows

Just type http://localhost:8080 directly into your browser's address bar. The 'open' command only works on Mac/Linux.

Step 5 of 5

Stop or remove the container when done

1 min

Because you used --restart unless-stopped, this container will start automatically every time Docker starts. If you want to stop it temporarily, use the stop command. If you want to remove it entirely, use the remove command. You can always re-run Step 2 to bring it back.

Terminal · mac

$ docker stop it-tools

$ # To remove it completely:

$ docker rm it-tools

What you should see

it-tools

// Status

cooked. baked. worked.

A fully working private copy of it-tools running at http://localhost:8080, with 40+ utilities available instantly in your browser, no internet connection required after the initial download.

// the honest bit

The honest part

This guide runs the official pre-built image — you get all tools that shipped in the latest release. You cannot add or remove individual tools without rebuilding from source, which requires Node.js and developer setup. The app has no authentication layer, so do not expose port 8080 to the public internet without putting a password-protected reverse proxy in front of it.