Mountit brings SFTP, WebDAV, S3 and your cloud drives up in Finder — and in the Files app on iPad and Vision Pro. A Rust core does the work. No kernel extension is installed, and nothing is copied to a folder you have to keep an eye on.
you@build.example.net · sftp://
Connection
SFTP
✓ Encrypted connection
Activity
18.4 MB/s
3 files queued · write-back
Cache
2.1 GB
94% metadata hits
Learning
On
Prefetching /src at 09:00
The Mountit window on macOS — a rendering of the shipping interface, drawn from the app’s own SwiftUI source. Not a photograph of a running build, and we would rather say so.
reachable from one app
exercised against a real server or an emulator
nothing installed below user space
macOS, iPadOS, visionOS
Why it feels different
Anyone can open a socket and list a directory. The reason most remote-mount tools are unpleasant is the 100 ms sitting between Finder and the server. That gap is the entire engineering problem, and it is where the work went.
Finder is a hostile client. It stats everything, fetches an icon for every file, writes .DS_Store into directories you only looked at, and expects an answer in under 100 ms. Raw passthrough over a 100 ms link is unusable. Mountit caches metadata, reads ahead, writes back and pins for offline — which is what you actually feel.
The mount is served by a File Provider extension, so your storage appears in Finder under Locations. Nothing is installed into the kernel, nothing asks you to reduce your security settings, and nothing breaks on the next OS update because a kext stopped loading. An FSKit volume in /Volumes is built and shipping in the Mountit Pro binary, and does not mount yet — see the ledger.
Passwords and keys live in the Keychain and the Secure Enclave. OAuth runs through the system browser, so your provider password is never typed into our app. The Rust core receives short-lived tokens and stores none of them.
The Mac App Store edition will be a Universal Purchase: buy it on the Mac and it is there on your iPad and in Vision Pro too. Mountit Pro tiers cover two to ten Macs, and you move a seat yourself without writing to support — including when the old machine is already sold, wiped or broken.
A real path, not a sync folder
A File Provider mount is a real directory on disk, not a synced copy —
so rsync, git, Xcode, Logic and your editor's
file watcher all work against it unchanged. macOS puts it under ~/Library/CloudStorage, which nobody wants to type, so
Mountit keeps a folder of short symlinks beside it: you pick where it
lives once, and then ~/Mountit/work-nas tab-completes like
any other path. There is no second app to open and no sync status to
interpret.
$ ls -l ~/Mountit
work-nas -> ~/Library/CloudStorage/Mountit-Work NAS
$ ls -la ~/Mountit/work-nas/archive | head -3
total 48
drwxr-xr-x 12 you staff 384 4 Aug 09:12 .
-rw-r--r-- 1 you staff 2.1G 3 Aug 22:40 2026-08-03.tar.zst
$ rsync -a ~/Documents/ ~/Mountit/work-nas/documents/
$ git -C ~/Mountit/work-nas/repo status
On branch main
nothing to commit, working tree cleanTwo editions
Sandboxed, as Apple requires. Every file, object and cloud protocol. A Universal Purchase covering macOS, iPadOS and visionOS at once.
Developer-ID signed and notarized by Apple, distributed by us, and not sandboxed — which is the only way the block protocols can exist.
What we promise
“We support 38 services” is a number that hides the only question worth asking — has anyone ever mounted one? Our protocol page answers it per service, and it is generated from the same ledger the engineering team works against.
No, and Mountit has never shipped one. Today the mount is served by a File Provider extension, which needs nothing switched on at all.
The Mountit Pro build also carries an FSKit module, for a volume in /Volumes on macOS 26. That path is not working yet: it needs the File System Extensions consent in System Settings › General › Login Items & Extensions, which only you can grant, and on macOS 26.6 the network-URL load path FSKit uses fails for Apple’s own modules as well as ours. We will say here when it mounts.
The App Store edition (Standard) is sandboxed, as Apple requires, and covers every file, object and cloud protocol across macOS, iPadOS and visionOS with a single Universal Purchase.
Mountit Pro is Developer-ID signed and notarized, distributed by us, and is not sandboxed. It adds the block protocols — iSCSI and NVMe-oF — which cannot exist in a sandboxed app, and it carries the FSKit module. It is the edition sold on this site.
Yes — 14 days, the full app, no card and no account. The clock starts at your first successful mount rather than at first launch, so time spent downloading, reading the docs or waiting on IT for credentials does not come out of it. It is recorded in your Keychain, so it survives a reinstall.
No. Personal and Advanced can be bought outright, and a perpetual licence entitles you to every release in that major version — 1.x today — for as long as you like, not for twelve months. When the next major version ships, your copy keeps working unchanged; upgrading is optional and discounted.
Past the trial and with nothing bought, the app settles into a free mode rather than a paywall: every connection you already configured keeps mounting, read and write, at full speed, with no time limit. What it will not do is add a new connection of any protocol — that is the whole of the limit.
No. Mountit connects your Mac directly to your server. Your files, credentials and tokens never touch our infrastructure — there is nothing in the middle to intercept. When the shop opens, our servers will see an email address, a licence key and which devices it is activated on — and nothing else. La politique de confidentialité spells out the whole list.
The core, the app and the mount in Finder work today. What is missing is the shop around them, and an FSKit volume that mounts — so rather than collect your email for a launch list, here is the engineering ledger and a way to tell us what you need.