Filedot

The file storage market is crowded. You have Google Drive, Dropbox, WeTransfer, and IPFS. Where does Filedot fit?

| Feature | Google Drive | Dropbox | IPFS | Filedot | | :--- | :--- | :--- | :--- | :--- | | Encryption | At-rest (server side) | At-rest (server side) | Optional | Zero-knowledge (Client side) | | Speed | Fast (CDN) | Fast | Slow (DHT lookups) | Very Fast (Multipath) | | Censorship Risk | High (Govt/Corp can delete) | High | Low (Persistent hashes) | Zero (No single owner) | | Recovery | Centralized backup | Centralized backup | Manual pinning | Automatic (Erasure coding) | | Cost | Monthly subscription | Monthly subscription | Free (But slow) | Pay-as-you-store (Microtransactions) | filedot

Journalists working with the Verge or ProPublica use Filedot to share sensitive documents. Because the network doesn't know which fragments belong to which file, metadata is hidden. Even if a government subpoenas a single Filedot node operator, that operator only has random noise, not the full document. The file storage market is crowded

Navigate to the official Filedot web portal. Warning: Always double-check the URL (should be app.filedot[.]network or similar) to avoid phishing scams. | Feature | Google Drive | Dropbox |

Developed in response to major data breaches at centralized hosts (the iCloud leaks of 2014, the Facebook breach of 2019), Filedot started as an open-source GitHub project. The goal was simple: make data breaches mathematically impossible. If a hacker steals 3 of your 10 Filedot fragments, they have nothing—just unreadable gibberish.