Delivery
Deploy acceleration
Configuration changes never go live the moment you save them. Each edit is written to a draft table and the domain is marked as having a draft waiting; only the Deploy button copies that draft into the configuration the proxy actually reads. That single decision point is what makes it safe to experiment with routing, cache, and acceleration settings on a live domain.
How it works
- Edits are written to a draft config and the domain is marked deploymentStatus: DRAFT
- Deploying copies draft to deployed inside a single transaction, so the proxy never sees a half-applied config
- A tokenized /accelerate/:token URL lets you preview the deployed behavior, including HTML/CSS rewriting, ahead of a full production cutover
Good to know
- The tokenized preview is a demo path, not the production CDN flow — DNS, CNAME, and managed TLS onboarding are a separate step
- Because deploy is transactional, a failed deploy leaves the previous live config untouched
- Draft state is visible in the hero summary as Routing: Draft and Deploy: DRAFT
- Deploying increments the domain configuration version, which live responses report