Cloudflare Deployment Modes for a CRUD App

Cloudflare gives you three real ways to ship a full-stack CRUD app: Pages with Functions, Pages with a standalone Worker, and Workers with static assets. They look similar but differ in routing and auth, in where your code lives and when it runs. I was building Class of One when I faced this confusion. After resolving the confusion with the help of Claude, I wanted to document it for future reference. TL;DR: for a new full-stack app in 2026, go for Workers with static assets. It is Cloudflare’s own recommended default, unifies the frontend and backend into one deployment, and is the cleanest answer to “how do I put my static file behind auth.” Pages remains fully supported. If you already have a happy Pages project, there is no deadline forcing you off it. Mode 1: Pages with Functions A Pages project with a functions/ directory next to your built site. Each file becomes a route by its path: functions/api/todos.js handles /api/todos functions/api/todos/[id].js handles /api/todos/123 A…