Interactive demo — synthetic data, read-only. Nothing here is a real person or organisation.
Request access →
Offload victim dump files to your own cloud storage to keep the Hostinger shared disk light — the platform serves each file by its direct link. Add several instances per provider for more capacity; the offloader spreads across active ones by priority and auto-skips a full or erroring account.
0Files offloaded0.0 KB off Hostinger
0Awaiting offload0.0 KB on Hostinger disk
3Active instancesof 3 connected
3.7 MBDatabase sizefull backup below
Offload progress
0 of 0 dumped files moved off HostingerGreen = offloaded to cloud · orange = still local. The offloader also runs automatically every 10 minutes on the main node.
🗄️ Total storage availability
across active cloud instances — the offloader & backups fill lower-priority numbers first186.26 GBTotal capacity2 sized · 0 unmetered
44.89 GBUsed24% of known capacity
141.37 GBFreeheadroom for offload + backups
Green = used · grey = free. Instances with unmetered capacity (e.g. S3) aren't counted in the totals.
Connect a storage instance
credentials are encrypted at restConnected instances
Google Drive · demo Google Drive
active
Mega · demo Mega.nz
active
S3 · demo-archive S3-compatible (AWS / Backblaze B2 / Wasabi / MinIO)
active
💾 Database backup
full gzipped SQL dump of every table (queries, credentials, victims, parsed data, users, config)Weekly automatic backup runs Sundays 03:00 and is replicated to 2 cloud copies for redundancy — Google Drive first (if a service-account instance is connected), then the highest-priority active instances (e.g. dosya.dev / Zippyshare).