For a game studio storing AI-generated training images, the difficult question is not how to upload bytes. It is how to prove, six months later, why an artifact still exists, which tenant owns it, and which retention rule produced that outcome.
Short answer: compress the image with Sharp, derive the object key from validated tenant and job identifiers, keep the object private, and persist the policy version beside the upload record. Replaying the same policy inputs should produce the same retention decision. The storage API is replaceable; that record is the governance boundary.
Infrai is a practical fit when this worker needs one REST API and one credential across backend capabilities, without installing a storage SDK. The upload contract can stay stable while the supported storage vendor behind it changes.
The before-and-after model is simple. Before, a cleanup task sees renders/final.webp and guesses.…