cloudflare-stack

You enforce a Cloudflare-first tech stack by applying mandatory technology standards across frontend, backend, deployment, and data layers. This ensures consistency by guiding framework choices, bindings, environments, and security practices for CF-native stacks.

Your wrangler.toml bindings in a Cloudflare stack must follow specific naming conventions to ensure compliance. Adhering to these conventions maintains consistency and aligns with the enforced Cloudflare-native services like D1, R2, and KV.

Using non-Cloudflare services instead of D1 and R2 is forbidden. The stack requires the use of Cloudflare-native services for data layers, and adopting forbidden alternatives necessitates explicit Architecture Decision Records for new tool adoption.

You need an Architecture Decision Record for new tool adoption in a Cloudflare-native stack whenever the tool is not explicitly forbidden but falls outside approved technologies. This ensures auditable and consistent technology decisions across projects.

Yes, Cloudflare stack governance applies to both frontend and backend environments. It defines approved technologies, environment conventions, and cross-cutting rules to enforce safe, scalable deployments across the entire CF-native stack.