July 11, 2026
Cloud cage match: trust vs access
ZeroFS vs. Amazon S3 Files
One keeps files easy to grab, the other locks them up tight — and commenters are torn
TLDR: This showdown is about two ways to store files in the cloud: one keeps them visible like normal cloud files, while the other hides and secures them for efficiency. Commenters were split between excitement, fear about trusting valuable data, and outrage over Amazon’s pricing.
File storage drama has entered the chat, and the crowd is treating it like a custody battle for your photos, spreadsheets, and sanity. The big split is simple: Amazon’s S3 Files keeps your files looking like normal items sitting in cloud storage, while ZeroFS turns that storage bucket into a hidden vault where files are packed, compressed, and encrypted before they land. Translation: with Amazon’s option, other apps can still eventually see the file as a regular cloud object; with ZeroFS, outsiders see a mysterious blob pile unless they use ZeroFS itself and have the password.
That trade-off is exactly where the comment-section tension kicks in. One reader basically said, love the idea, terrified to trust it with my life’s files, and demanded a torture-test system that constantly tries to corrupt data just to see what breaks. Another immediately went into “cool, but can it scan fast for AI training?” mode, dreaming of slick analytics and DuckDB-style file access. And then came the money comment — the kind that always starts a cloud riot — with one user bluntly roasting Amazon prices by comparing S3 to a much cheaper giant VPS, complete with a “$377 vs $48” mic drop.
Even the visuals caught stray fire: one commenter opened with a dark-mode complaint from Safari on iPhone, which is honestly peak internet. The author jumped in with a cheerful “Author here” reply, but the real vibe was clear: people are curious, skeptical, and very ready to argue about convenience, trust, and whether cloud storage is genius or daylight robbery.
Key Points
- •Amazon S3 Files preserves a one-file, one-object mapping in S3, while ZeroFS stores files in an internal format using an LSM tree and immutable packed segments.
- •S3 Files writes become durable in AWS high-performance storage immediately and are exported to S3 asynchronously after inactivity; ZeroFS flushes segments and metadata to object storage on fsync.
- •Files written through S3 Files eventually become normal S3 objects accessible through the S3 API, but ZeroFS-mounted files are never directly readable through the S3 API.
- •S3 Files can import metadata and small files on first access, while ZeroFS relies on local RAM and disk cache plus cached sealed segments for read-after-write behavior.
- •ZeroFS supports Amazon S3, S3-compatible stores, Azure Blob, and Google Cloud Storage, whereas S3 Files is tied to Amazon S3.