Skip to content

Workers and Pages

Overview

Cloudflare provides an edge platform that combines DNS, TLS, routing, and compute in a single control plane. In this setup, Pages is used for build + deployment of frontend and full-stack apps, while Workers provides the runtime for backend logic and edge processing. Both are configured alongside DNS and security, so application delivery, routing, and execution live in one place and are managed declaratively.

Workers

Workers is the edge compute layer. It’s used for:

  • HTTP APIs and request routing
  • Middleware (auth, rewrites, headers, feature flags)
  • Background tasks and scheduled jobs
  • Integrations with KV, D1, R2, and external services
  • Lightweight backend logic close to the user

Code runs globally without server provisioning. Deployments are handled via CLI or CI, configuration is environment-scoped, and secrets/vars are managed per environment. In practice, Workers acts as the application runtime.

Pages

Pages handles the build and hosting lifecycle for web apps:

  • Git-connected builds (static or framework-based)
  • Automatic preview deployments per PR
  • Production deployments on merge
  • Native integration with Workers for server-side logic

Pages is responsible for compiling assets and publishing them to the edge. When paired with Workers, Pages serves the frontend while Workers handles dynamic behavior. Effectively: Pages owns delivery of built artifacts; Workers owns execution.

Currently deployed Pages

Below is the table containing currently deployed Pages

Name Purpose Status URL Repository
r-sky-documentation Internal documentation, developed using MkDocs and Material for MkDocs Active https://docs.r-sky.dev https://github.com/rowicsky/Documentation