“Yes — Cloudflare Pages is a good fit for the static frontend, but your containerized API would normally live somewhere else.”
“Pages is excellent at serving static assets globally, with automatic Git deployments and preview deployments.”
“Pages is excellent at serving static assets globally, with automatic Git deployments and preview deployments.”
“It can also run backend code through Pages Functions, but those are Cloudflare Workers functions—not arbitrary Docker containers.”
“For a new Cloudflare project, I'd actually consider using Cloudflare Workers with static assets instead of Pages.”
“Cloudflare now explicitly describes Workers as its primary application platform and recommends it for new projects; Workers can serve static assets and backend logic from the same deployment.”
“Cloudflare now explicitly describes Workers as its primary application platform and recommends it for new projects; Workers can serve static assets and backend logic from the same deployment.”
“Cloudflare's own migration documentation now positions Workers as the broader successor to Pages.”
“But that doesn't eliminate the container requirement. A Dockerized API still needs a container runtime elsewhere.”
