The Fundamental Difference: Control Plane vs. Data Plane
Most cloud backup and synchronization applications act as a heavy middleman. When you send a 2 GB video through a traditional aggregator, the aggregator’s server buffers the full 2 GB in memory and re-uploads it to the cloud. This results in slow transfer speeds, expensive bandwidth bills for the provider, and major privacy risks for you.
Fuze Drive completely separates the Control Plane from the Data Plane:
Handles user authentication, encrypted OAuth token storage, Virtual File System (VFS) folder structures, and high-speed metadata queries. Only JSON payloads are exchanged.
Raw file binaries stream directly between your web browser and official cloud endpoints (Google Drive, Microsoft Graph, Box API, Dropbox, pCloud).
The 5-Step Direct Upload Lifecycle
Client Initiates Upload
When you drop a file into Fuze Drive, the browser calculates its size, MIME type, and asks the Fuze backend for an upload strategy.
Smart Allocation Engine
Fuze checks your connected accounts. If Google Drive (15 GB) or pCloud (10 GB) has enough free space, it selects Whole-File Priority. If a file is massive, it allocates chunks across multiple clouds.
Presigned Session Generation
The backend queries the target cloud provider's API to initiate an authorized resumable session URL and hands it directly to your browser.
Direct Browser-to-Cloud Binary Stream
Your browser uploads raw bytes directly to Google, Microsoft, Box, Dropbox, or pCloud endpoints via HTTPS PUT requests. 0 KB of file payload touches Fuze servers.
Metadata & Tree Finalization
Once the provider acknowledges the completed upload, Fuze records the file ID, size, and path in your encrypted Virtual File System (VFS) tree.
Intelligent Allocation: Whole-File Priority & Merkle Trees
Many experimental multi-cloud tools make the mistake of slicing every single file into tiny pieces across multiple providers. While interesting in theory, this destroys performance and breaks native cloud previews.
Fuze Drive uses a pragmatic Two-Rule Allocation Engine:
If any connected provider with sufficient space can store the file intact, it is assigned to that provider based on transfer speed (Google Drive > pCloud > OneDrive > Box > Dropbox). This guarantees instant cloud-native previews and maximum single-stream throughput.
Only when a large file exceeds the free capacity of every individual provider does Fuze activate chunking. The file is partitioned into discrete SHA-256 validated segments, uploaded in parallel across your remaining quotas, and linked via a cryptographic Merkle root.
How Your Credentials and Data Stay Secure
- Official OAuth2 Authorization: You never enter your Google, Microsoft, Box, or Dropbox passwords on Fuze. Authorization happens on each provider’s official login domain.
- AES-256-GCM Token Encryption: OAuth refresh and access tokens are encrypted before being saved to the database.
- Distributed Redis Token Locking: Concurrent upload streams share a centralized Redlock mechanism, preventing race conditions or rate-limit lockouts during token refresh cycles.
- Account Collision Protection: Fuze enforces unique email ownership across providers, preventing another user from linking your cloud drive.
Ready to Experience Zero-Proxy Cloud Storage?
Aggregate your free Google Drive, OneDrive, Dropbox, Box, and pCloud into one 42 GB personal drive today.