Deploys & rollback
Every approved ticket ends in a deployment: your product, updated and live on your Cloudflare account. And because the source lives in your GitHub repository, every deployment is reversible.
What a deploy is
Section titled “What a deploy is”When builder agents finish a ticket they:
- commit the code to your GitHub repository,
- deploy the result to your Cloudflare account, and
- publish it at a live URL.
The deployment is real production infrastructure in your own account — not a preview hosted by Typillar. See What you own.
Rollback
Section titled “Rollback”Every deployment is recorded, and you can roll back to any prior state with one click. Rollback is reliable because it’s anchored to two things you own:
- the commit history in your GitHub repo, and
- the deployment history Typillar records for the project.
If a change isn’t what you wanted, reverting it is a single action — not a salvage operation.
Why reversibility matters
Section titled “Why reversibility matters”Reversibility is what makes shipping fast safe. When any change can be undone in one step, you can approve work quickly and react to what’s live, rather than deliberating over every deploy. The loop is built to be fast precisely because it’s built to be reversible.
Production-ready from the first deploy
Section titled “Production-ready from the first deploy”There’s no separate “go to production” ceremony. The first time a project ships, it ships to production — live, on your domain or a Workers subdomain, with rollback available immediately.
Related
Section titled “Related”- Project history — the full record behind rollback.
- The build loop — where deploy fits in the loop.