Overview
What Pip is
One desktop app for dev servers, Git context, memory use, speed tests and file cleanup.
The short version#
Pip brings Servers, Network and Storage into one desktop app. See your running projects and Git details, find what is using CPU and memory, and stop servers you no longer need. Run speed tests, diagnose connection problems, explore your disks, and clean up build files and supported tool caches. On Windows, it lives in your system tray.
Server detection needs no per-project setup. Pip looks at what is running and connects each detected server to its project, ports and Git repository — three signals, no configuration.
The tools#
Switch between three tools from the dock at the bottom of the window.
- Servers
- Find running projects, check branches, commit IDs and remotes, and track CPU and memory across each server's process tree. Open a server, copy its URL, or stop it to release its resources. Read the Servers guide.
- Network
- Measure download and upload speeds, latency, jitter and packet loss. Check how your connection behaves under load, run diagnostics, and test a specific host. Read the Network guide.
- Storage
- Explore what is taking up disk space, review file cleanup, and run supported cache cleanup commands. Quarantined files have a seven-day restore window; cache commands take effect when they finish. Read the Storage guide.
What Pip does not do#
Half of knowing a tool is knowing where it stops. Pip is deliberately small:
- It does not start your dev servers. Pip finds servers that are already running. Starting them is still your terminal's job.
- It does not upload your scan results. Projects, ports, branches and metrics never leave the machine — see what leaves your machine.
- It does not need administrator rights. Detection uses unprivileged Windows APIs and the installer is per-user.
- It is not a task manager. OS services and privileged ports are filtered out on purpose, so the list stays short enough to read at a glance.
Getting started#
Note
New here? Install Pip — it is a two-minute setup, and you will be looking at your first scan about five seconds after that.
Did this page not answer it? Tell us what you were looking for — that is how Pip's documentation gets written.