Pier vs Mountain Duck
Pier vs Mountain Duck: Drive-letter service or desktop sync integration?
Pier and Mountain Duck offer two different ways to bring remote files into desktop applications. Pier fits a Windows setup built around persistent drive letters, while Mountain Duck’s Integrated connect mode fits a Finder or File Explorer experience built around on-demand synchronization. Both provide offline access, but their local-storage models and desktop integration differ.
How remote storage becomes part of your desktop
Pier uses the Dokany file-system driver to mount WebDAV, SFTP and NFSv3 storage as Windows drive letters. Explorer, Office, backup tools and scripts can open, save and rename files through those drives. Pier runs as a system service, mounts the drives for every user on the machine and preserves them across reboots.
This is a useful fit when a Windows application or script expects a stable drive path. For example, an SFTP folder could remain available under the same letter each time Windows starts, without making the mount dependent on manually opening a desktop application.
Mountain Duck supports macOS and Windows. Its version 5 Integrated connect mode uses Apple’s File Provider API on macOS and the Cloud Files API on Windows, with no device-driver installation or network mount required in that mode. Files are presented through the operating system’s desktop file interface, with synchronization controls in Finder or File Explorer.
The choice here is about how you want remote storage represented: a service-managed Windows disk with Pier, or an operating-system-integrated file collection with Mountain Duck’s Integrated mode.
Offline access: cached blocks versus selected files and folders
Pier fetches file data in blocks and stores those blocks in a local cache whose size you control. Repeated reads can use cached data, and only the touched portions of a file are transferred. Switching a drive to offline mode lets you work with content already in the cache; changes are journaled and sent to the server when you return online.
Pier also reconnects automatically after network interruptions and resumes interrupted transfers from the last completed block where the server supports the necessary mechanisms. Its protocol handling includes Nextcloud chunked uploads, HTTP Range requests and SFTP file offsets. These details are relevant when large files and interrupted connections are central to the workload.
Mountain Duck’s Smart Synchronization shows remote files whether or not they have been synchronized locally. Opening a file synchronizes it to disk for offline use, and you can explicitly select files or folders to always keep offline. Changes upload in the background once a connection is available.
That explicit offline selection is a meaningful reason to choose Mountain Duck for a laptop carrying a defined set of project folders. Pier’s offline model instead revolves around what is already present in its block cache. Neither approach eliminates local disk use; they give you different ways to manage it.
Storage connections and shared-document work
For a Windows machine accessing an NFS export, Pier offers a built-in NFSv3 client with per-drive UID/GID mapping, without requiring the Windows NFS feature. Its other connection paths are WebDAV—including Nextcloud and ownCloud—and SFTP over SSH.
Mountain Duck provides connections for WebDAV and SFTP alongside services and protocols such as Amazon S3, Azure, Google Drive, Dropbox, OneDrive, FTP and SMB. If your desktop access needs span a cloud account, object-storage bucket and server folder, those supported connections give Mountain Duck a clear role.
Mountain Duck also offers features specifically relevant to shared documents. It can lock files opened in Microsoft Office to prevent conflicting edits, using WebDAV server locking where supported or lock-owner files as an alternative. It supports opening and reverting versions in versioned Amazon S3 buckets, and version 5 adds custom versioning that stores changes in a versioned folder on the server. Cryptomator-compatible vaults provide transparent client-side encryption.
These are distinct reasons to prefer Mountain Duck when document coordination, version recovery or encrypted vault access matters—not simply another way to display remote files.
Which should you choose?
Choose Pier when your main requirement is to give WebDAV, SFTP or NFSv3 storage a persistent Windows drive letter, particularly for applications and scripts that work with disk paths. Its service model and block-level transfer handling are central to that choice. It supports 64-bit Windows 10 and 11 and Windows Server 2019 or newer, and requires Dokany.
Choose Mountain Duck when you want macOS and Windows desktop integration, explicit “always keep offline” folders, or its supported cloud connections and document-management features. Its Integrated connect mode is especially relevant if you want the operating system’s file-provider experience without installing a device driver.
Pier’s free edition includes up to five drives, all three protocols, caching, transfer resume and offline mode, with an advertising banner. Pro costs $19 per year per installation and removes the drive limit and ads; the upgrade changes capacity and advertising rather than the underlying file-access model.