Show HN: Ellipticc Drive – open-source cloud drive with E2E and PQ encryption

Posted by iliasabs 1 day ago

Show HN: Ellipticc Drive – open-source cloud drive with E2E and PQ encryption(ellipticc.com)

Hey HN, I’m Ilias, 19, from Paris.

I built Ellipticc Drive, an open-source cloud drive with true end-to-end encryption and post-quantum security, designed to be Dropbox-like in UX but with zero access to your data, even by the host.

What’s unique:

Free 10GB for every user, forever.

Open-source frontend (audit or self-host if you want)

Tech stack:

Frontend: Next.js

Crypto: WebCrypto (hashing) + Noble (core primitives)

Encryption: XChaCha20-Poly1305 (file chunks)

Key wrapping: Kyber (ML-KEM768)

Signing: Ed25519 + Dilithium2 (ML-DSA65)

Key derivation: Argon2id → Master Key → encrypts all keypairs & CEKs

Try it live: https://ellipticc.com

Frontend source: https://github.com/ellipticc/drive-frontend

Would love feedback from devs and security folks — particularly on encryption flow, architecture, or UX.

I’ll be around to answer every technical question in the comments!

19 points | 10 comments

pixel_popping 6 hours ago|

I don't understand the Github repo, it shows some sort of drafted/vibe-coded frontend, but the actual program isn't open-source?

iliasabs 1 hour ago|

[dead]

QuiCasseRien 12 hours ago||

Nice, but please stop with the words "forever" when it's about costs, ie: "free forever". It harms your message.

iliasabs 8 hours ago|

Thanks for your advice!

foxylad 20 hours ago||

Your "About" links seem not to work. In my case I was interested in where data is hosted, and the only information I see (from your HN post) is that you are from Paris. Does this mean EU hosting (which is good)?

iliasabs 8 hours ago|

Yes, sorry — I’ve focused more on the actual logic of the dashboard rather than the landing page, which still lacks polish. Regarding the data, all your files are stored on Backblaze B2 servers (EU-central), with their data centers located in Amsterdam, Netherlands. I hope I’ve answered your question correctly.

some_furry 22 hours ago||

Your post here says ML-KEM768 but the website says Kyber512.

Also, this SRP implementation seems a bit... sus.

https://github.com/ellipticc/drive-frontend/blob/main/lib/sr...

iliasabs 8 hours ago|

Thanks for pointing that out! Could you elaborate on what specifically looks off about the SRP implementation? I tried to follow RFC 5054 with some minor adjustments for the frontend (using hash-wasm and fixed-length encoding to match the server), but I’d really appreciate feedback if something looks wrong or insecure.

some_furry 7 hours ago||

Side-channels. Also, N and G matter a lot to security; not making those hard-coded and transparent is sus. You can't just use a normal DH group.

I would recommend OPAQUE instead.

iliasabs 6 hours ago||

[dead]

groby_b 22 hours ago|

"Open Source" is a pretty clear case of lying by omission.

You open sourced the frontend. Without a clear license.

That's not an "open-source cloud drive"

iliasabs 7 hours ago|

Thanks for the feedback — to clarify, only the frontend is open-sourced at the moment, sorry for any confusion. I’ve also just added an MIT License to make that explicit. The backend isn’t public yet, but we may open parts of it later.