Why this matters — Cloudflare Workers

What you just played

The game, this page, and the protected leaderboard are one Worker — a few hundred lines of JavaScript with no servers, containers, or regions to choose. It was deployed from a terminal with wrangler deploy, the same command an enterprise team wires into CI/CD.

0servers to manage

300+cities running this code

<1 mindeploy to global

What that buys a customer

Latency: code executes in the city closest to the user, not in one origin region.
Scale without capacity planning: the same deploy handles ten users or ten million.
Security in front of the app: WAF, rate limiting, and bot rules sit ahead of the Worker.
Identity without a VPN: Cloudflare Access protects /leaderboard — the app only ever sees a verified identity header, never a password.
State at the edge: Workers KV stores the high scores; no database to provision.

Architecture in one line

Request → Cloudflare edge (WAF + rate limit + bot rules) → Access policy on /leaderboard → Worker → Workers KV. Every hop is configuration or code, not hardware.