Put a name
to that localhost.
When port 3000 is already taken, see which project is listening. Pip puts its name, branch and address together, with controls to open it or stop it.
macOS + Windows. Pay once. Future updates included.
Three terminals open. Find the right localhost.
Four processes called node don’t tell you which one belongs to the storefront. Pip uses the project folder name, then adds the port and Git branch. You can find the server you meant without retracing the terminals you opened this morning.
Start your projects with the same commands you already use. Pip checks running processes for development signals, filters out operating system services, and gives each detected server a place to inspect its stats, open its address or stop it.
- recognised development runtimes
- 80
- common development ports checked
- 28
- between automatic server scans
- 5s
Recognise the project at a glance.
Project names come from the folders your servers run in. Search by name, port or branch to find the one you have in mind.
Get straight to your local app.
Open a server at its actual address or copy the URL. Its Ports tab shows every bind address and flags when it’s reachable from your network.
Finish with a clear desktop.
Stop servers you no longer need to release their ports and resources. Pip marks elevated processes when it doesn’t have permission to stop them.
Keep track from launch to last request.
Read the Servers guideStart your project as usual.
Run your dev command in your terminal. Pip detects supported servers without setup in each project.
Find it in Pip.
Browse the server list or search for a project, port or branch. Open a row for its stats, Git details and addresses.
Open, copy or stop.
Jump into the browser, copy a URL for your next task, or stop a server when you’ve finished using it.
A few details behind the server list.
What appears in Pip depends on what’s listening and how it was started. These are the details that help when a project behaves differently from the others.
- Does Pip show every process on my machine?
- Pip starts with listening sockets and looks for development signals: a recognised runtime, a working directory inside a Git repository, or a common dev port. One signal is enough. Operating system services and ports below 1024 are filtered out, so the list focuses on development servers rather than every background process.
- Can Pip start a server or stop an elevated one?
- You start servers with your usual terminal commands; Pip finds them once they’re running. It can stop processes it has permission to manage. On Windows, servers started from elevated terminals are marked as elevated because Pip runs without administrator rights. Stop those servers from a terminal with the required permissions.
- How can I tell whether a server is reachable on my network?
- Open the server’s Ports tab to see every address it is bound to. Pip flags an address bound to all interfaces, which can make the server reachable from other devices on your network. Each listed address can be opened or copied, so you can use the address the server actually exposes.
Keep your running projects within easy reach.
Every Pip tool. $29 USD, once. One machine at a time.