MACOS · DEVELOPMENT WORKSPACES

Deckhand

Knows what is running on your machine, what owns it, and what is safe to stop.

Launch price · −50%Final price €130

€65+ VAT at checkoutLicence agreement

428 licences left at the launch price

Four surfaces in one product: busy ports, processes left hanging, containers and build folders. The value is in the link between them.

The problem

You have ten projects you haven't touched in weeks, and no quick way to tell which ones still hold something open. A busy port, a Node process left running in the background, a Docker container still up, a node_modules folder several gigabytes deep — each one is checked separately, with a different tool.

The alternative is lsof, ps, docker ps and a du -sh through every folder, one after another, project by project, every time you just want to know what is still occupying the machine.

The mechanism

One scan, four surfaces

Deckhand reads all four independently, then links what belongs together.

PortsThe TCP ports something on your Mac is currently listening on.
ProcessesThe development processes behind those ports — what they are, and how long they have been running.
Build foldersThe regenerable output each project has left behind — node_modules, .next, .build, DerivedData, target, build, dist.
ContainersDocker containers, images, volumes and build cache, correlated by their Compose working directory — shown only when Docker is installed and running.
// screens

The app's screens

Pick a project and its first line says what holds its port and for how long, with tabs for its processes, build folders and containers.
Deckhand reads ports, processes, containers and build folders in one scan, and links what belongs together into projects.
Evidence shows how each link was made, and a port matched only by its number is flagged as a weaker link.
Close Project shows the whole plan before it runs: live processes stop, build folders go to the Trash, the project's containers and the images only it built are removed, and shared images and volumes stay.
// screen tour

What each screen shows

  1. 01 / 04

    A project's page

    • Under the project's name and path, one sentence says which process holds its port and how long it has been running.
    • The overview counts the processes, ports, build folders, containers, images and volumes that belong to the project.
    • The Processes, Build, Docker and Evidence tabs open each surface on its own.
    • Close Project, top right, starts closing the project with the whole plan in view.
  2. 02 / 04

    The scan and the project list

    • On the left, each project found is listed with its path and its count of processes, containers and build folders.
    • The scanned folders sit under the list; the toolbar adds a new folder or runs the scan again.
    • Here the port is linked to a container by its number, and the sentence says so outright: “matched by port number, not by process identity”.
    • The bottom bar shows the version, how recent the scan is and the licence state.
  3. 03 / 04

    The evidence behind each link

    • The Evidence tab lists every link between a resource and the project, with its source: the build-folder adapter, the process's working directory or the Docker Compose label.
    • A build folder is tied to its project by what sits beside it, here a package.json next to node_modules.
    • A solid green icon marks high-confidence evidence; a weaker one, such as a port matched only by its number, shows in orange.
    • A port on its own can never merge two projects.
  4. 04 / 04

    The Close Project plan

    • Before anything runs, the sheet splits the plan into “Will run”, what will happen, and “Kept”, what stays.
    • Processes stop, the project's containers are removed, build folders go to the Trash and the image only this project built is deleted.
    • Every kept resource carries its reason: the postgres:16 base image stays because ownership is not proven, and the volume stays because volumes have their own separate workflow.
    • Nothing starts until you press Execute, and right before it does, Deckhand rechecks the identity and ownership of each resource.

What it does

Correlates processes, ports, projects and containers into a single view. From that correlation comes "close the project": pick a project, see everything of its on the machine, then close it all in one operation — with an exact list of what is removed and what stays because it is shared.

Why correlate at all

The point of linking them

Each surface alone tells you a fact. Linked, they tell you a story your terminal cannot — that a port, a process and a container all trace back to the same project, one you may have already moved on from.

“Port 3000 is held by container acme-api, started 3 days ago, from ~/work/acme — which you closed on Friday.”

This is the promise CorrelationEngine.correlate() is built to keep — an illustration written for this page, not a screenshot of a real scan.

The workflow

Close Project

Pick a project. See everything of it still on the machine. Close it in one operation — with the exact list of what gets removed and what stays because it is shared.

What gets removed
  • Live processes
    Stopped, if their PID and working directory are confirmed in the current scan.
  • Project containers
    Removed, when a container's Compose working directory matches the selected project.
  • Build folders
    Moved to the Trash — never deleted outright, and never Docker volumes.
  • Exclusive images
    Removed only if the image is built by this project and not shared with another one.
What stays, and why
  • Base and registry images
    Kept — project ownership of a pulled image is never assumed.
  • Shared images
    Kept, when the same image belongs to more than one correlated project.
  • Docker volumes
    Always kept. Volume deletion is a separate, higher-risk workflow, never part of Close Project.

Docker volumes are always shown, never removed by this workflow — deleting one is a separate, higher-risk operation with its own confirmation.

The licence

See it all for free, close it with a licence

Without a licence, Deckhand scans, correlates and shows you exactly what Close Project would do. The licence unlocks the actions that change your system.

Free, no licence

  • Scanning ports, processes, containers and build folders
  • Correlating them into projects, with the evidence behind every link
  • Previewing exactly what Close Project would remove and what it would keep
  • The analysis of the space Docker takes up

With an activated licence

  • Running Close Project: stopping the processes, removing the project's containers and its exclusive images, moving the build folders to the Trash
  • The same operations one at a time, plus pruning the Docker build cache
  • Deleting a Docker volume, kept separate because it is the only operation that destroys data you cannot regenerate

How the licence works

  • One payment, no subscription. One licence activates one Mac.
  • Activation happens online: me-digital.ro receives the key, a machine identifier and the Mac's name.
  • At launch, when you are online, the app checks that the licence is still active on your Mac. With no internet, it keeps working.
  • Changing Macs? Release the licence from the app on the old Mac and activate it on the new one.

What you can rely on today

Four things the app does exactly as described here.

What it scans stays on your Mac

Nothing Deckhand correlates leaves your Mac, and its entitlements file is empty. It contacts me-digital.ro only for the licence (the key, a machine identifier and the Mac's name) and to check for updates, which it does on its own and from the menu.

Tested without touching your machine

The suite covers the probes, the correlation engine, the safety verdicts and the Close Project planner — and none of it touches a real Docker installation or a real process to do so.

A universal binary

The release build is signed for both Apple Silicon and Intel Macs — one binary, not a per-architecture download.

Docker absence is a normal state

Deckhand does not require Docker. When it is not installed or not running, the app shows the other three surfaces and says so, instead of erroring.

Where this stands

How the port link is made

v1.0.0

The link between a port held on the host and the container that publishes it is made by port number, not by process identity: on macOS the host side of a published port is held by Docker's own networking process, which belongs to no project. The app says so in the sentence it shows — "matched by port number, not by process identity" — and marks the evidence as medium confidence, not certain.

Shipped in 0.1.1. Verified by tests, on a premise measured on a real machine — a process whose working directory cannot be resolved, not one that is absent. Not verified at runtime against live containers.

Requirements

System
macOS 14.0 or later
Architecture
Universal — Apple Silicon and Intel
Built with
Swift 6, SwiftUI

Questions

No. Docker is one of four surfaces Deckhand reads, shown only when Docker is installed and running. The other three — ports, processes, build folders — work on a Mac with no Docker at all.

Yes — the download is on this page. It is signed with a Developer ID and notarised by Apple, so macOS does not warn: an ordinary double-click opens it the first time.

No. Close Project never touches volumes. They are shown so you know they exist, and removing one is a separate, deliberately higher-risk workflow.

No account. Everything it scans stays on your Mac and its entitlements file is empty. The only connections are the licence (the key, a machine identifier and the Mac's name) and update checks.

It is kept. Deckhand only offers to remove an image it can prove is built by this project alone and used by no other correlated project.

Deckhand for Mac

SwiftSwiftUImacOSDocker CLI
Launch price · −50%Final price €130
€65

+ VAT, calculated at checkout for your country

428 licences left at the launch price

Licence agreement

Activation

How to activate your licence

Download the app

Download version 1.0.0

2.7 MB

Open the app, open the Deckhand menu → Licence…, paste the key from the email and press Activate.