Hoodik

Hoodik provides self-hosted personal cloud storage where every file encrypts locally inside the client before transmission. Its storage architecture splits files into encrypted chunks and wraps access keys with post-quantum cryptography so the underlying server never inspects document contents.

Why Hoodik instead of Dropbox

Dropbox manages encryption keys on its own infrastructure, enabling server-side indexing, automated previews, and corporate metadata collection. That architecture requires complete trust in the provider's privacy compliance, employee access controls, and data retention policies. Hoodik moves cryptographic authority entirely to the user's browser or mobile device, running client-side ciphers like AEGIS-128L before bytes leave the host. Even if the hosting server, disk volume, or network traffic is compromised, an outside observer only sees opaque binary blocks and tokenized lookup hashes.

The trade-off centers on workflow convenience versus data sovereignty. Dropbox provides transparent desktop background filesystem synchronization, native operating system integration, and collaborative office document suites. Hoodik discards those background operating system daemons in favor of a focused web interface, Android client, and encrypted note editor. Non-technical users avoid recurring per-seat subscription tiers and commercial telemetry, but they must manage their own storage server and accept manual browser uploads rather than automated desktop folder sync.

What it does well

• Client-side encryption executes entirely in the browser before upload, ensuring family photos and sensitive documents remain unreadable to the server operator.
• Public file sharing generates secure web links containing the decryption key in the URL hash, allowing recipients to download files in their browser without registering an account.
• Built-in encrypted note editor saves formatted markdown text with automatic saving, keeping private journals and lists inside the same protected environment.
• Blind metadata search tokenizes query terms locally so users can search through stored file names without revealing plaintext terms to the database.
• Straightforward single-container deployment runs on modest hardware or virtual private servers with minimal memory consumption.
• Flexible storage backend supports either local drive storage or external S3-compatible object buckets without altering the end-user encryption workflow.