Cloudflare workers vs cloudflare pages

[vocal trail]

I am confused what to use for deployment of Next.js storefront+ payloadcms app: workers or pages??
Next.js storefront which I would be deploying is:https://github.com/medusajs/nextjs-starter-medusa.git

Also, I have a multi-tenant usecase where a single storefront would be serving thousands of tenants requiring ISR from Next.js.

1 click Payloadcms is for coudflare workers, so I am confused.

[lone shard]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Storage Adapters - R2 Storage
• Storage Adapters - R2 Storage - Usage
• Swap in your own React components - Performance - Follow React and Next.js best practices
• Production Deployment - File storage - Persistent vs Ephemeral Filesystems
• Vercel Content Link - Edit Mode

[shadow prairie]

use cloudflare worker

[vocal trail]

Thanks.
But would you please elaborate reason??

[shadow prairie]

1: Best-in-class ISR for multi-tenant e-commerce
2: Edge-delivered CMS API
3: Scalability for thousands of tenants
4: Developer-friendly deployment
5: Cost-effective at scale

[vocal trail]

Thanks.
I was struggling with this.

Chatgpt was suggesting me wrong, recommending me to use pages instead of workers for this usecase.

Also, recently (4/8/2025) cloudflare recommended "starting with workers" and announced "going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers".
https://blog.cloudflare.com/full-stack-development-on-cloudflare-workers/#start-with-workers

[sour cargo]

Yeah, Pages is all but deprecated