Atlas · building
Deploys
Putting a new version where people can use it. A good deploy is one command and easy to undo.
See it working: Plate II
In plain words
A deploy takes what you built and puts it where everyone can reach it. Until then, changes live only on your machines.
How it works
This site runs on Cloudflare Workers. Every change to a Worker’s code or configuration creates a version, and wrangler deploy creates one and sends all traffic to it. A static site like this one ships as assets: Wrangler uploads the folder named in its configuration, and Cloudflare caches and serves the files.
Going deeper
Deploys are where an agent’s mistakes reach real people. On this site only a person may deploy. Plate II shows a hook refusing an agent’s deploy that a written rule could not stop.
Sources
- Versions & deployments Cloudflare
Every time you change your Worker's code or configuration, Workers creates a version.
When you run wrangler deploy, Workers creates a version and sets its deployment to 100% of traffic.
- Static Assets Cloudflare
You can upload static assets (HTML, CSS, images and other files) as part of your Worker, and Cloudflare will handle caching and serving them to web browsers.
The assets directory specified in your Wrangler configuration file is central to this design. During deployment, Wrangler automatically uploads the files from this directory to Cloudflare's infrastructure.
Quotes were checked against the live pages on 2026-11-12.