How YourKeep Protects Your Files Without Running Any Servers

When people first discover YourKeep, the most common question is: “Where are your servers located, and how do you store my backups?”

Our answer is always the same: We run zero servers. We have no centralized databases, no user authentication backends, and no cloud storage clusters.

While this sounds counterintuitive in an era dominated by cloud SaaS platforms, eliminating the central server is the deliberate, core architectural choice that makes YourKeep’s data resilience unbreakable.

---

The Client-Side Execution Pipeline

Every operation in YourKeep takes place exclusively within your device’s local CPU and RAM using compiled native binaries:

[ Local Master File ]
          │
          ▼  (1. Key Derivation: Argon2id Memory-Hard Hash)
[ 256-Bit Cryptographic Key ]
          │
          ▼  (2. Authenticated Symmetric Encryption: AES-256-GCM)
[ High-Entropy Ciphertext Container ]
          │
          ▼  (3. Erasure Coding: Reed-Solomon 6-of-10 Cauchy Matrix)
[ 10 Self-Describing Fragment Files (.keep) ]
          │
          ▼  (4. User-Directed Passive Placement)
  ┌───────┴───────┬───────────────┬───────────────┐
  ▼               ▼               ▼               ▼
[Local SSD]   [Home NAS]   [Google Drive]   [Proton Drive]

---

3 Core Architectural Pillars

1. Zero-Knowledge Cryptography by Default

YourKeep never transmits your master password, keys, or plaintext data across any network. Files are encrypted with AES-256-GCM before any fragment touches a disk or storage bucket. Even if a storage provider’s database is breached, the attacker gains access only to high-entropy, authenticated ciphertext fragments.

2. Mathematics Over Company Promises

Traditional backup software relies on the company remaining solvent and maintaining active license servers. YourKeep relies on pure, open mathematics. The V1 container format is fully documented, using standard Galois Field matrix multiplication. Even if the YourKeep team ceases operations, your files can be restored using any open-source tool built to the V1 specification.

3. Passive Storage Interoperability

YourKeep treats storage endpoints as dumb byte buckets. You do not need to configure complex OAuth integrations or grant third-party apps read/write access to your entire cloud drive. You simply drop the generated fragment files into any standard directory.

---

Conclusion

By eliminating intermediate servers, YourKeep removes the single point of failure that compromises traditional cloud backups. You retain total cryptographic ownership of your data—forever.