v0.5.2 Released|Tauri v2 + Rust Core

Turn Google Drive into an Unbreakable Data Bank

Slice and encrypt files locally with AES-256-GCM. Disperse redundant parity shards across pooled Google accounts using Reed-Solomon Erasure Coding and decentralized Magnet Swarms.

Zero-Knowledge Encryption
Multi-Account Quota Isolation
Reed-Solomon Fault Tolerance
Free Software (GPLv3)
magdrive-core // streaming-pipeline.rs
TOKIO POOL: 6 WORKERS
magdrive-cli$1. Client File Slicing
STREAM: Reading 'core_database_archive.tar.zst' (3.84 GB)
SLICER: Partitioned into 120 streaming stripes (constant RAM < 48 MB)
Zero-Knowledge: Google Drive hosts only AES blobs
Interactive Application Tour

Engineered for Precision & Absolute Privacy

Take a visual tour inside MagDrive. Built from the ground up with Tauri v2 and Rust for native performance and a tactile Nordic Minimalist interface.

Tauri v2 · 1440×900
Multi-Account OAuth Pool & Quota Isolation

Multi-Account OAuth Pool & Quota Isolation

Connect multiple personal Gmail accounts and Workspace Shared Drives into a unified, zero-knowledge vault. Automatically calculate adaptive 2+1 Reed-Solomon redundancy.

2.03 TB Pooled2+1 Reed-SolomonMulti-OAuthAuto-Provisioning
Quota Architecture

Bypassing Google Drive's Shared Folder Quota Trap

In 2021, Google updated its policy: files uploaded to someone else's shared folder count against the uploader's quota, preventing simple shared folder expansion. MagDrive solves this permanently.

Standard Google Drive Shared FoldersBottleneck Trap

Single-Account Quota Depletion

Even if your teammates share 100 GB of empty folders with you, every file you upload consumes your personal 15 GB account. Once your 15 GB is full, all uploads fail.

Uploader Account (You)15.0 / 15.0 GB (100% FULL)
Shared Target 010.0 / 15.0 GB (Unused)
Shared Target 020.0 / 15.0 GB (Unused)
✖ Result: Blocked uploads, wasted target capacity, recurring subscription pressure.
MagDrive Multi-Account OAuth PoolTrue Quota Isolation

Aggregated 45 GB Storage Pool

MagDrive holds separate OAuth sessions for each account. Shard 0 uploads using Account A's token, Shard 1 with Account B's, and Shard 2 with Account C's. Quota is consumed uniformly across all accounts.

Account A [alpha@gmail.com]5.0 / 15.0 GB (33%)
Account B [beta@gmail.com]5.0 / 15.0 GB (33%)
Account C [gamma@gmail.com]5.0 / 15.0 GB (33%)
✔ Total usable pool: 45 GB (or unlimited with Google Workspace Shared Drives).
Interactive Simulator

Dynamic Reed-Solomon Erasure Coding

MagDrive computes optimal Galois Field GF(2^8) matrices based on your connected Google accounts. Click any drive below to simulate account bans, deletions, or Google 403 quota exhaustion.

Connected Storage Targets:3 Google Accounts / Drives
1 Drive (1+0)3 Drives (2+1 Default)5 Drives (3+2)9 Drives (6+3 High Resilient)
Data 100% Lossless & Recoverable
3 of 3 drives active (Minimum required: 2)
Scheme (D + P)
2 + 1
2 Data / 1 Parity
Fault Tolerance
1 drive
Max simultaneous loss
Storage Overhead
+50%
Parity shard ratio
Early Decode Benefit
Save 50%
Stops when D shards arrive
Storage Target Distribution:(Click any drive card to toggle simulated failure)
Non-Colocation Invariant: MagDrive guarantees that each storage target hosts strictly no more than 1 shard per stripe. The rotation formula (stripe_index + shard_index) % N evenly distributes network bandwidth and storage usage across all connected accounts.
CORE ARCHITECTURE

Three Pillars of Resilient Privacy

Eliminating cloud surveillance, quota bottlenecks, and single points of failure with client-side mathematics.

Privacy

Client-Side Zero-Knowledge

All files are sliced and encrypted locally with AES-256-GCM before leaving memory. Cloud providers receive only anonymous binary blobs without file extensions, plain metadata, or readable headers.

  • Argon2id Master Key derivation (64 MB RAM, 3 iterations) strictly on your device.
  • AES-256-GCM authenticated chunk streaming with randomized nonces.
  • Google Drive never sees file names, folder structures, or content signatures.
Storage Pooling

Multi-Account Quota Isolation

Bypasses Google's post-2021 shared folder quota trap. Shard uploads are authenticated through each account's independent OAuth session, pooling multiple free 15 GB accounts into one large data bank.

  • Combines three free 15 GB Google accounts into an aggregate 45 GB pooled vault.
  • Rotates uploads evenly across accounts so no single drive is prematurely exhausted.
  • Supports personal Google accounts and Google Workspace Shared Drives with 1 click.
Fault Tolerance

Reed-Solomon Self-Healing

Mathematical redundancy ensures complete data survival even if storage drives are banned, suspended, or hit download quotas. Missing pieces are synthesized on the fly from remaining shards.

  • Dynamic (D + P) schema automatically calculates optimal redundancy for your drive count.
  • Survives full account deletions: 2+1 scheme recovers data from any 2 surviving shards.
  • Instant target migration engine with server-side fast-copy or math-based re-encoding.
BEHIND MAGDRIVE

Built by a vibe coder & problem solver

Crafted by uragenky — turning practical problems into working software with modern AI tools. I focus on system logic, privacy architecture, and pragmatic solutions rather than writing every line of code by hand.

MagDrive was born out of real annoyance with cloud storage limits, arbitrary policy shifts, and surveillance risks. Open for project collaborations, idea sparring, or building custom tools together.

FREQUENTLY ASKED QUESTIONS

Technical Questions & Answers

Everything you need to know about zero-knowledge encryption, quota isolation, and Reed-Solomon recovery.

No. Files are sliced and encrypted locally on your machine with AES-256-GCM before transmission. The file names and metadata stored on Google Drive are random cryptographic hashes (e.g., 'chk_a982df14...'). There are no recognizable file extensions, magic bytes, or plain MIME headers for automated scanners to inspect.