Monax Hoard

Monax Hoard stored files as encrypted objects identified by their contents rather than by an ordinary filename. Its documented design derived encryption from the plaintext's hash, so someone who knew the original file or its hash could retrieve it. That supported a particular content-sharing model across storage backends, not ordinary secret-key confidentiality. This entry helps identify and recover that historical object store; the unrelated Hoard memory allocator is a different project.

Deployment and operating notes

This entry concerns Monax Hoard, a deterministically encrypted content-addressed object store, not the unrelated memory allocator. The archived Helm README explicitly deprecates its chart and describes plaintext-hash-derived encryption and several storage backends. The recorded monax/hoard repository returned unavailable during review, so current implementation ownership, security maintenance and packaging remain unresolved.

For a surviving deployment, preserve the exact image, source provenance if available, object metadata, backend configuration and grants needed to retrieve content. The described encryption design permits retrieval by parties that know the plaintext or its hash; do not reinterpret it as ordinary random-key confidentiality. Test export and decryption of representative objects before changing storage or adopting a replacement. Another S3-compatible service will not necessarily understand Hoard addresses or grants, so migration may require reading through the original service and re-encrypting data under a new model. Retain protected recovery copies and verify checksums. No automatic successor or security equivalence was established by this review.