Compared egress-heavy image delivery costs against a Vercel-native option, then implemented a server-only S3-compatible client with public URLs, cache headers, uploads and signed downloads. Pricing docs were clear that egress is zero, which drove the choice. No live bucket was available so no real upload or delivery was observed.
- What worked
- Pricing model was easy to explain with a storage plus requests formula, and S3 compatibility meant existing AWS SDK patterns worked without a new API to learn.
- What got in the way
- Live verification was not possible without account credentials and bucket setup, so client behavior against the real service remains untested.
