Backends
Every storage service Mountit can mount has a page of its own here — what it is, what Mountit does with it, and the same evidence level our engineering ledger carries. 9 are verified against a live server or a vendor emulator; the rest say exactly that on their page, because a logo wall never lost a file but a lying one has.
Servers that speak files.
The workhorse of self-hosted storage: a file server over SSH, on every NAS and every Linux box.
Live-tested Verified against a live serverWindows file sharing — and the protocol most NAS boxes and office file servers speak.
Live-tested Verified against a live serverThe HTTP extension that turns a web server into a file server — and the door to Nextcloud, ownCloud, Synology and HiDrive.
Live-tested Verified against a live serverRead-only access to any static file tree a web server publishes.
Live-tested Verified against a live serverThe old faithful of file transfer, still running on a remarkable number of hosts.
Live-tested Verified against a live serverHDFS over its HTTP gateway — the only shape of Hadoop a sandboxed app can use.
Not yet tested live Compile-verified; no live server reached yetThe caching layer that sits in front of a data lake.
Not yet tested live Compile-verified; no live server reached yetMicrosoft’s managed file shares in the cloud, reachable over SMB and REST.
Not yet tested live Compile-verified; no live server reached yetSelf-hosted file sync with library-level organisation.
Not yet tested live Compile-verified; no live server reached yetContent-addressed storage read through a gateway.
Not yet tested live Compile-verified; no live server reached yetThe mutable file system of an IPFS node — writable, unlike the gateway.
Not yet tested live Compile-verified; no live server reached yetNot a remote — a folder on your own disk, mounted through the same volume stack.
Not yet tested live Compile-verified; no live server reached yetS3 and the stores that imitate it, plus the data-lake filesystems.
One API, an entire industry: Amazon S3 and every store that speaks its protocol — R2, Wasabi, B2, Scaleway, MinIO and more.
Live-tested Verified against a live serverMicrosoft’s object store, from individual backups to data-lake foundations.
Emulator-tested Tested against an emulatorGoogle Cloud’s object store, and the backend of many a data pipeline.
Emulator-tested Tested against an emulatorBackblaze’s object storage, popular for backups at commodity prices.
Not yet tested live Compile-verified; no live server reached yetThe object store of OpenStack clouds — and of a fair few Rackspace-era installs still running.
Not yet tested live Compile-verified; no live server reached yetTencent Cloud’s object storage.
Shared code path Same code path as a verified service; endpoint unverifiedAlibaba Cloud’s object storage service.
Shared code path Same code path as a verified service; endpoint unverifiedHuawei Cloud’s object storage service.
Shared code path Same code path as a verified service; endpoint unverifiedBlob storage with a real hierarchical namespace — directories that are directories.
Not yet tested live Compile-verified; no live server reached yetThe storage layer of a Databricks workspace, including Unity Catalog volumes.
Not yet tested live Compile-verified; no live server reached yetGit-like versioning and branching over object storage.
Not yet tested live Compile-verified; no live server reached yetVercel’s blob store for application assets and uploads.
Not yet tested live Compile-verified; no live server reached yetThe Chinese CDN-backed cloud storage service.
Not yet tested live Compile-verified; no live server reached yetRepositories over the REST API — content, releases and the like as a file tree.
Not yet tested live Compile-verified; no live server reached yetModel weights and datasets from the HF Hub.
Not yet tested live Compile-verified; no live server reached yetSign-in with the provider, storage billed by them.
Google’s cloud drive, from Docs to whatever you dropped in it.
Not yet tested live Compile-verified; no live server reached yetMicrosoft’s cloud drive, personal and business.
Not yet tested live Compile-verified; no live server reached yetThe cloud drive that started the category.
Not yet tested live Compile-verified; no live server reached yetThe enterprise content cloud — the one ExpanDrive had that the field mostly skipped.
Not yet tested live Compile-verified; no live server reached yetThe Swiss-based cloud drive with a lifetime-plan following.
Live-tested Verified against a live serverThe encrypted cloud — client-side crypto and generous free tiers.
Not yet tested live Compile-verified; no live server reached yetYandex’s cloud drive.
Not yet tested live Compile-verified; no live server reached yetAlibaba’s personal cloud drive.
Not yet tested live Compile-verified; no live server reached yetThe cloud hub that aggregates other clouds behind one quota.
Not yet tested live Compile-verified; no live server reached yetThe id-addressed download and streaming locker — the destination for a library too large to keep a second copy of.
Not yet tested live Compile-verified; no live server reached yetA premium download and streaming locker, taken by an API key rather than a sign-in.
Not yet tested live Compile-verified; no live server reached yetSeveral entries cover a family, which is why a raw count understates the coverage. The S3 page reaches Cloudflare R2, Wasabi, Storj, Scaleway, DigitalOcean Spaces, MinIO, Garage, Ceph and every other S3-compatible endpoint — same API, same credentials, different host. WebDAV is how Nextcloud, ownCloud, Synology, Fastmail, pCloud and Yandex Disk are reached; SFTP and SMB are how a Synology, QNAP, TrueNAS, Unraid, OpenMediaVault, ASUSTOR or TerraMaster NAS is. FTP covers FTPS, WebDAV covers WebDAVS, HTTP covers HTTPS.
What a family entry costs is discoverability: nobody looking for “Cloudflare R2” thinks to pick “S3 or compatible” and go and find an endpoint. That is what the 47 presets close — a product name on a form, over a backend that already speaks the protocol. They are listed on the four pages they belong to, and they are generated from the table compiled into the app rather than retyped here, because a support page naming the wrong host is worse than one naming none.