Short answer: for a SaaS that serves generated reports to authenticated customers, keep the bytes in private object storage, keep ownership and lifecycle state in Postgres, and use short-lived signed upload and download URLs as capabilities issued by an authenticated Node.js service.
That decision separates delivery simplicity from access control. The browser sends the large payload directly to object storage, while the application remains the place that knows which customer may create, replace, or read a report. A signed URL is a temporary permission to perform one storage operation; it is not a document record and it is not a substitute for an authorization check.
I use that distinction as a capacity-planning reflex. Application servers should spend their budget authenticating requests and recording state, not proxying every report byte.…