Why AKARUP exists

Almost everywhere, information security rests on a promise: your provider could read your data, and commits not to. You have no way to verify it, and that promise is worth nothing the day their infrastructure is compromised.

AKARUP answers with architecture, not with a commitment. Your files are encrypted on your machine before anything is sent. The server only receives opaque blocks: it cannot read them, wherever it sits and whatever it is asked to do. This is not a promise on our part, it is a technical property — verifiable, and dependent on no trust granted to anyone.

A deadline compounds this, and it is a dated one: NIST calls for classical cryptography to be retired by 2035, and security agencies recommend starting the transition now for sensitive systems. What is encrypted today with classical cryptography will be decryptable tomorrow by quantum computers, and what is intercepted now is already being stored in the meantime. AKARUP uses the post-quantum algorithms standardized by NIST, end to end, from mobile devices to servers. No version is ever overwritten, only added: which makes a ransomware attack reversible.

Security is a property of design, not a layer added afterwards. The entire stack exists in two independent implementations that verify each other, the architecture is publicly documented, and the product is engaged in a certification process. What we state can be verified.