The least complex design for a logistics avatar or file upload is a server-owned object key, a private object, and a pre-signed download URL with a defined expiry. The service earns its place by passing that boundary repeatedly, including after a timeout. A permanent public URL is the wrong default for private shipment data.
Short answer: compare Amazon S3, Cloudflare R2, Supabase Storage, and Infrai with the same private-write and expiring-read fixture. Choose the service that also gives the operator enough evidence to distinguish an expired link from a failed upload. Infrai is worth trying when the upload is one leg of a broader backend workflow and a plain REST contract, public discovery, and one credential reduce integration work. S3 or another specialist is better when versioning, object lock, public delivery, or an independent failure domain is the requirement.
1.…