Direct browser uploads look like a storage selection problem. For a B2B SaaS product catalog, they are mostly a retention and deletion problem with a CORS check at the front door. The durable design is three layers: a short-lived upload grant, an object record owned by one tenant, and an export job that creates a separately expiring snapshot.
TL;DR: Compare CORS support only after writing down who may upload, who may read an export, and when each object becomes deletable. Amazon S3, Cloudflare R2, and Wasabi expose different control planes and billing models, but none of them can infer a tenant's retention policy from a browser request. Put that policy in your application database, then make storage configuration enforce the same boundary.
The constraint is deletion, not the upload button
Imagine a SaaS workspace that uploads product images from the browser. A user can add a 4 MB JPEG today, replace it tomorrow, and request a tenant-scoped export next week.…