Bringing clouds together.
The Opportunity
The average user in 2025+ has storage fragmented across 3–7 cloud services. Each with different capacity limits, different interfaces, different security models — and no interoperability between them.
Result: wasted storage, fragmented files, cognitive overhead, and security gaps.
Core Promises
Megh doesn't just list your clouds side by side. It fuses them into a single, encrypted, OS-native storage pool.
All connected cloud accounts appear as one contiguous storage pool. A file you save doesn't go to “Google Drive” or “pCloud” — it goes to Megh. Capacity is summed, transparently, across every provider you've linked.
A 3 GB file uploads across 1 GB left on Drive + 2 GB left on Backblaze — invisibly. Megh splits at the chunk level, encrypts each chunk independently, and reassembles on read. No provider sees the whole file. No provider knows it's incomplete.
The server, the cloud providers, and any interceptor see only encrypted noise. Keys never leave your device. Megh's backend can grant access, rotate tokens, or be fully compromised — your files remain unreadable to everyone except you.
Real folders on Windows, macOS, Linux — via FUSE and WinFSP. Not a browser tab. Not a sync app. A real filesystem that any app on your computer can read from and write to. Native iOS and Android apps are in active development.
Cryptographic Architecture
Every file is encrypted on your device before it ever touches the network. The keys live only in your device's memory, derived from your password through a memory-hard KDF.
Provider employee or breach accesses stored files.
Attacker gains access to Megh backend.
Network traffic interception.
Physical access to user's device.
Offline password guessing.
A single key is exposed.
Future quantum attacks on current encryption.
192-bit nonce eliminates reuse risk even with billions of chunks. Fast in pure software on all platforms. AEAD provides confidentiality + integrity.
Hardware-accelerated (AES-NI) on modern CPUs. Well-audited. Used for filenames, DEKs, and OAuth tokens.
Memory-hard. Resists GPU/ASIC brute-force. Winner of the Password Hashing Competition. The "id" variant protects against both side-channel and GPU attacks.
NIST-standard KDF for deriving multiple sub-keys from a single master key.
Fastest cryptographic hash. Tree-hashable for parallel computation. 256-bit output.
(k, n) threshold scheme: any k of n shares reconstruct the key. Information-theoretically secure.
Why Megh
Other tools list your clouds. Megh fuses them.
Megh · बादल · মেঘ · ☁ — Bringing clouds together.