Path Finder alternative: provisioning it across several Macs

Picking a file manager for one Mac is a matter of taste and a weekend of trying things. Picking one that has to be supplied to four machines, or to a colleague whose Mac nobody sits at, is a different exercise with different failure modes. The features stop being the deciding factor somewhere around the second install, and the questions that decide it become how the licence is counted, how long updates last, whether the installer can be scripted, and what happens to the arrangement when the vendor changes something. This is what separates a purchase from a provisioning decision.

What provisioning adds to the question

A single seat has one owner who is also the buyer, the installer, and the person who clicks through the permission prompts. Provisioning splits those roles, and every split introduces something that can go wrong later.

The buyer is often not the user, which makes the licence key a shared secret that has to be stored somewhere retrievable. Vendors that tie a licence to an email address rather than to a key raise a related question: whose address, and what happens when that person leaves.

The installer is often not sitting at the machine, which rules out any tool whose only distribution route is a download page with a manual drag into the Applications folder. The user is the one who has to grant the operating system permissions, which cannot be done from a script on a machine without device management.

The practical result is that a tool which is slightly worse to use, but trivial to install and clearly licensed for several machines, wins the comparison it would lose on features alone. That is not a compromise so much as a different scoring system, and it is worth adopting deliberately rather than discovering after the third machine.

The licence shapes on offer

Four shapes cover almost everything in this category, and each behaves differently under multiplication.

Tool	Licence shape	Price as published	Minimum macOS
Finder	Included with macOS	None	Whatever the Mac runs
Path Finder	Subscription or licence key, 30 day trial	Listed in the store on the vendor site	13 per the Homebrew cask
ForkLift 4	Perpetual licence with a fixed update window	19.95, 29.95 family, 69.95 for up to 5 office Macs, in US dollars	14.6 per the vendor site
Commander One	Free version plus a paid PRO Pack, 15 day PRO trial	Listed in the vendor store	10.13 per the vendor site
Marta	Free download, currently in beta, supported through Patreon	None	11.0 per the vendor site

The middle rows are where the multiplication happens. ForkLift publishes a family licence covering every Mac in a household and a small business licence covering up to five office Macs, which is a straightforward answer to a four machine question. A per seat subscription answers the same question by multiplying, which is fine but produces a recurring line item rather than a one time one.

Path Finder describes its own offer directly on the front page:

Path Finder has all the tools you need to take control of your files. It comes with a 30 day free trial. Source: cocoatech.io

Thirty days is unusually generous for a trial, and it matters more for provisioning than for a single user, because a trial has to survive being run on several machines by people with different habits before anyone commits money.

What the update window actually buys

The perpetual licence with a limited update window is the shape most likely to be misread, so it is worth reading the vendor's own wording rather than the marketing summary:

With the ForkLift lifetime license, you get free software updates for one or two years, depending on your choice. Once that period ends, you can keep using the latest version of ForkLift covered by your license indefinitely. Source: binarynights.com

Two things follow. The app does not stop working when the window closes, so the downside is not a dead tool. What does stop is compatibility with whatever macOS ships next, because a file manager sits close enough to the system that a major macOS release regularly requires work on the vendor's side.

That makes the update window a bet on the macOS upgrade cycle rather than on the software. A machine that stays on one macOS version for three years gets full value from a one year window. A fleet that takes each September release as it arrives will hit the wall in the second or third year and need new licences anyway, which changes the arithmetic against a subscription considerably.

The version numbers are the cheapest evidence of whether that bet is safe. ForkLift's site lists 4.7.5, dated 1 September 2026, with a stated requirement of macOS 14.6. Commander One's page lists 3.17.1, dated 13 October 2025, and states compatibility with macOS 10.13 and later. Both figures are published by the vendors and both are worth rechecking at the moment of purchase rather than trusted from an article.

Putting it on machines you do not sit at

Every tool in this category is a standard macOS application, which means the download and drag route works and is also the route that does not scale. The scriptable alternative is Homebrew, and all four of the paid or free third party options have casks:

brew install --cask forklift
brew install --cask path-finder
brew install --cask commander-one
brew install --cask marta

Two details in the cask metadata matter for provisioning. All four are marked as self updating, which means Homebrew installs them and then steps back: subsequent updates come from the application's own updater, not from brew upgrade. Any expectation of controlling versions centrally through Homebrew is therefore mistaken, and version pinning has to happen inside each app's preferences instead.

The casks also carry install counts, which are a rough but honest signal of how many people deploy each tool by script rather than by hand. Over the most recent 365 days, Homebrew records 7,539 installs for Marta, 4,831 for ForkLift, 4,150 for Commander One and 1,111 for Path Finder. Those figures say nothing about quality and quite a lot about which tools reach machines through automation.

The step that cannot be automated without device management is permissions. A file manager needs access to the folders macOS protects, which means Full Disk Access, or at minimum the Files and Folders entries, granted per application in System Settings under Privacy and Security. Those approvals are granted by a person sitting at the machine, and they have to be granted again for every tool adopted. Budgeting five minutes per machine for this avoids the common outcome, which is a colleague reporting that the new app cannot see the Desktop.

Four checks before standardising on one tool

Feature comparisons age badly. Four facts about the vendor age worse, and each one can invalidate a decision made on features alone.

The first is whether the product is still sold. A tool still listed on review sites can have quietly stopped taking new customers, and the review does not update itself.

The second is whether new signups are open on the same terms. A product can remain available while the licence type someone chose for a fleet has been withdrawn, which turns the fifth machine into a different purchase from the first four.

The third is ownership. Cocoatech states on its own blog that its parent company is Distant Future, which is the sort of arrangement worth knowing before a finance team queries an unfamiliar name on a card statement. Ownership changes also tend to precede changes in licence terms.

The fourth is pricing. Every figure in this article was published by a vendor on a specific day, and none of them are promises. Rechecking the store page at the moment of purchase costs a minute and prevents an approved budget from being wrong by the time it is spent.

None of these four checks require contacting anybody. The product page shows whether the buy button still works, the store page shows which licence types are offered today, the vendor's own blog or about page shows who owns the company, and the store page shows the current figure. Ten minutes covers all four for three candidates, and doing it in that order stops a shortlist being built around a product that has already changed shape.

What does not come across when the tool changes

Migration cost is the line item nobody puts in the comparison, and it lands after the decision rather than before it.

Favourites, bookmarks, tab presets and keyboard bindings live inside each application's own preferences and do not transfer. Anyone who has spent two years shaping a sidebar rebuilds it by hand, and rebuilding it on four machines is four times the work unless the new tool has a settings file that can be copied.

What does survive is anything macOS stores rather than the app. Finder tags live in file metadata, so they remain readable by any tool that goes through the standard file APIs, and a tagging scheme is not lost by switching. The same is true of file dates, permissions and extended attributes.

There is one exception worth planning around. A tool that keeps its configuration in a plain text file, rather than in an opaque preferences store, can be set up once and copied to every other machine. Marta documents a configuration file for exactly this reason, and the difference it makes on four machines is the difference between one setup and four. Checking for that file before committing is a five minute exercise that pays back on the second install.

The habit cost is the one that is systematically underestimated. Two weeks of reduced speed per person, multiplied across a small team, is a real number, and it argues for changing tools once rather than trying three. It also argues for being clear about what problem the change is meant to solve. If the complaint is that a folder view, a terminal and an assistant occupy three separate windows, a second file manager does not address it, and a file manager that keeps them in one window is a different category from the dual pane tools above. The side by side comparison and the pricing page are the places to check that before a trial rather than after.

What to change first

Decide the machine count and the update horizon before opening any download page, because those two numbers eliminate most of the list without a trial. Then run one tool on every machine that will use it, not just on the fastest one, and grant the permissions on day one so the trial measures the tool rather than the setup. If the count of windows is the actual complaint, Atriens belongs in that trial alongside the dual pane options.