38 services, two block protocols, an honest answer for each.

Native Rust implementation on russh — not a shell-out to ssh, so it runs inside the App Store sandbox. Mounted against a live NAS and driven through Finder by a person.

A self-contained pure-Rust client, written because libsmbclient cannot cross-compile to iOS. Live-tested against a real Samba server with mandatory packet signing; no C dependency anywhere in it.

Live-tested against a real server and driven through Finder. WebDAVS is the same protocol over TLS, not a separate backend.

Live-tested against a static server. Read-only, and labelled read-only in the volume properties — the protocol cannot write, and pretending otherwise is how data gets lost.

Native implementation, written because OpenDAL hardcodes passive mode: transfer mode, port and TLS are all controllable. Verified against a live server with 12 integration tests. FTPS is FTP over TLS, not a separate backend.

Compile-verified and confirmed to cross-compile to iOS. The native libhdfs client needs a JVM, which a sandboxed app cannot load; WebHDFS reaches the same clusters over HTTP.

Not usable as a mount today, and listed rather than hidden. The vendored backend declares `read: false` behind an upstream FIXME, so it has no read path: a connection can be configured and every file on it opens empty. Compile-verified, and no live server would change that — there is nothing on our side to call.

Compile-verified; no live server reached yet.

Compile-verified; no live server reached yet. Self-hostable, so it is on the same live-test path Azure Blob took.

Read-only, because the backend has no write path at all — a gateway serves content addressed by its hash, and a hash is not a name you can write to. The volume properties say so and writes are refused rather than accepted and lost. Compile-verified; the writable sibling is IPFS MFS, listed separately.

Compile-verified; no live server reached yet.

It is what the encryption and union layers wrap, and what they are tested against.

Live-tested against MinIO. The same code path reaches Cloudflare R2, Wasabi, Storj, Scaleway, DigitalOcean Spaces, Garage, Ceph and every other S3-compatible endpoint — same API, same credentials, different host. The presets below pre-fill the endpoint for the well-known ones.

Verified against Azurite, Microsoft’s own emulator. Strong evidence, not the real endpoint.

Verified against fake-gcs-server. Strong evidence, not the real endpoint.

Same S3 code path as the live-tested S3 service; the per-provider endpoint is unverified.

Same S3 code path as the live-tested S3 service; the per-provider endpoint is unverified.

Same S3 code path as the live-tested S3 service; the per-provider endpoint is unverified.

Speaks B2’s native API. The S3 endpoint B2 also offers is covered by a preset under S3, which skips nothing but the gateway.

Compile-verified; no live server reached yet. Self-hostable, so it is on the same live-test path Azure Blob took.

Compile-verified and confirmed to cross-compile to iOS; no live server reached yet.

Not usable as a mount today, and listed rather than hidden. The vendored backend declares no read capability at all, so it has no read path: a connection can be configured and every file on it opens empty. Compile-verified, and no live workspace would change that — there is nothing on our side to call.

Compile-verified; no live server reached yet. Self-hostable, so it is on the same live-test path Azure Blob took.

Compile-verified; no live server reached yet.

Compile-verified; no live server reached yet.

Compile-verified; no live server reached yet.

Read-only: the backend has no write path, so a repository mounts for reading and writes are refused rather than accepted and lost. That suits what people mount it for — pulling weights and datasets without a download step. Compile-verified; no live server reached yet.

Native client, verified against a live account: digest sign-in, two-factor by SMS, push or recovery, and the full backend trait. The EU region refuses passwords in query parameters; this client does not use them.

Implemented and compiled; waiting on the provider registration that lets anyone sign in. Sign-in happens in the system browser, so your Google password never touches the app. Mountit asks Google for the narrow drive.file scope, so you choose the folders it may see through Google’s own picker — it is never handed your whole Drive.

Implemented and compiled; waiting on the provider registration that lets anyone sign in.

Implemented and compiled; waiting on the provider registration that lets anyone sign in.

A native REST client, tested against an in-process mock Box API. One live account is still needed to confirm a response spelling; everything else about it is covered by the mock suite.

Read-only today: the upload path is not written, and the volume says so rather than accepting a write it cannot honour. Key derivation is verified byte-for-byte against the library rclone uses, and the wire protocol is driven end to end against an in-process MEGA.

Compile-verified; no live server reached yet.

Compile-verified; no live server reached yet.

Speaks Koofr’s own API, and its WebDAV endpoint too — the preset under WebDAV needs an app password. Compile-verified; no live server reached yet.

A native client (`mountit-putio`), added to the picker on 2026-09-03 alongside Premiumize.me — both crates were complete and compiled for weeks before either could be selected. Unit-tested against put.io’s own published JSON shapes; no live account has mounted it yet, and put.io’s paid-only, no-free-tier, no-emulator account is why: a conformance lane needs someone to buy a subscription first.

A native client (`mountit-premiumize`), added to the picker on 2026-09-03 alongside put.io. Unit-tested against the exact JSON shapes rclone’s own premiumize client handles — including the API’s habit of answering a refusal with HTTP 200 and an error body, which a generic client would read as success. No live account has mounted it yet: premiumize is a paid-only service with no free tier and no self-hostable server, so a conformance lane needs someone to buy a subscription first.

Live-tested against a real tgt target, including the R2T multi-burst path.

Tested end to end against a target built alongside the initiator; cross-validation against Linux nvmet is pending.