Hi Product Hunt, I'm Cho. I built ShieldFive solo. I made it because the encrypted-storage tools I was using kept bolting on AI features that need to read your files. I wanted the opposite: store an encrypted blob, hand me the key, leave me alone. What it is: your files are encrypted in your browser before they upload. The server only ever holds ciphertext. No admin override, no key escrow, no support agent who can be talked into your files. What's actually different: the default at-rest cipher is post-quantum. ML-KEM-1024 combined with XChaCha20-Poly1305, on every upload, not a toggle you have to go find. It's aimed at "harvest now, decrypt later." The crypto is a separate Apache-2.0 library on npm, the same code that runs in your browser, so you can diff the published package against what gets served to you. The honest part, up front: - No external audit yet. Bootstrap-funded, it happens when revenue funds it. - Anonymous share links are classical-only. - Browser-only client for now. - If you lose your password and recovery key, your data is gone. The product says so loudly. EU-hosted, 20 GB free, no card to start. And if you ever want out, /export pulls your encrypted files and decrypts them offline with the open-source library, no ShieldFive servers needed. I ran that end to end before launching. I wrote up the crypto design here if you want the deep version: https://dev.to/chogarcia/making-... I'd love feedback, especially the skeptical kind. Tear into it.

ShieldFive

Zero-knowledge cloud storage, post-quantum by default

Zero-knowledge cloud storage, post-quantum by default