R
Robin Cloud Vault
Vault:
Initializing Wasm...

Upload to Telegram Vault

Files are sliced into 10 MB chunks and encrypted with AES-256-GCM via WebAssembly before uploading directly to Telegram.
Destination Folder: 📁 Root

📁

Drag and drop files here, or browse files

Supports single or multi-file queue uploads.
Uploading Queue: File 1 of 1 0%
current-file.ext 0%
Chunks
0 / 0
Bytes Uploaded
0 MB
Transfer Speed
0.0 MB/s
Time Remaining
--:--

Vault File Explorer

Vault Management

Configure credentials, database names, and encryption keys for each vault profile.

A descriptive name for this vault profile.
The specific MongoDB database used by this vault (sent dynamically to Supabase).
Used by Wasm to upload chunks directly to Telegram.
Telegram channel or group where encrypted chunks are stored.
Points to your deployed Supabase robin-proxy function, which streams chunks to/from official Telegram with CORS headers.
Derives a 32-byte AES-256 key via PBKDF2 inside WebAssembly to encrypt chunks client-side.
Supabase Edge Function endpoint that persists metadata into the specified MongoDB database.