put.io
The 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 yet
What Mountit does with it
- Mount
- Read and write, in Finder
- Offline cache
- Metadata cache, read-ahead and write-back — the same volume stack as every other service
- Encryption layer
- Available on this connection: client-side, rclone-compatible crypt over the data before it leaves your Mac
- Editions
- Both. Either edition mounts it through File Provider, so it appears in Finder — and, on Standard, in the Files app on iPad and Vision Pro
The engineering ledger does not list put.io among the
services run against a real server, so this page does not claim it was. That is
read out of docs/BACKEND-COVERAGE.md in the app repository when
this site is built — the build fails rather than let this page claim more than
the ledger does.
The conformance record
No lane yet. No server has been stood up to run the corpus against this service, so there is no record to publish. That is the honest answer, not a pending one. Every service’s standing, side by side.
put.io questions
Can Mountit mount put.io?
Yes — put.io is one of the 38 services selectable in the app. It mounts read-write, with the same cache, read-ahead and write-back as every other service.
What we will not do is claim it works before it does: this page carries the ledger’s evidence level for put.io, and it changes the day the evidence does.
Which edition do I need?
Either — this service is in both editions. The difference is the surrounding app, not the protocol: Mountit Pro is the unsandboxed build with the block protocols; Standard is the Mac App Store build, and on iPad and Vision Pro every service appears in the Files app. Both mount this service through File Provider.
Does put.io have folders the way a normal drive does?
Yes — unlike the object stores on this site, put.io has a real path hierarchy, just addressed by id rather than by path underneath. Mountit resolves each path component through put.io’s API and caches the ids, so a listing does not re-walk the whole tree on every request.
What happens when I replace a file?
put.io’s upload endpoint only ever creates a new file — there is no overwrite and no versioning. Mountit renames the existing file aside, uploads the replacement, and only then deletes the old one, so a connection that drops mid-save leaves your original file exactly where it was rather than losing it.