~180 min read · updated 2026-05-10

Build a project

Tie several Cloudflare products together into one working system.

The point of this track isn’t reading 13 modules — it’s building something that uses several Cloudflare products together so the platform stops being a list of SKUs and starts being a single coherent toolbox.

This module is being expanded with project templates.

Coming in the next revision — pick one of:

  • Private homelab portal. Tunnel + Access in front of a Pi-hosted service (Plex, Home Assistant, Proxmox dashboard). Replaces “open ports + dynamic DNS + maybe-VPN” with a single hostname behind SSO.
  • Edge-served AI chat app. Pages (static frontend) + Workers (backend) + Workers AI (Llama) + Vectorize (RAG index) + R2 (documents) — a complete RAG application that runs entirely on Cloudflare’s edge.
  • Internal SaaS gateway. Tunnel to an internal service + Access for SSO + Workers for request transformation + Logpush for audit logs. The pattern most enterprises eventually want.
  • Edge API with global Postgres reads. Workers + Hyperdrive in front of a managed Postgres. D1 for low-write metadata. R2 for blob storage. Pages for the docs.
  • Personal whitelabel CDN. Workers + Cache rules + R2 for origin storage. Free-tier-friendly, useful for small communities.

Each project will be walked through end-to-end: setup, code, deploy, what to watch for, what the bill looks like.

This is where the track ends. If you completed the capstone you have a working Cloudflare stack you can grow — Tunnel, Access, Workers, Pages, plus whatever data and AI primitives the project needed.

Where to go from here: