Zero-downtime deploys
Weighted releases, instant rollback, and origin health gates.
A production deploy on GitFlare never drops in-flight requests. New isolates take new connections; old isolates drain. You can shift 5% of a hostname to a candidate Worker, watch error rate, then finish or roll back.
Weighted release
$ gitflare deploy --name web --tag 2026-09-19a --no-promote $ gitflare route weight shop.example.com --to web@2026-09-19a --percent 5 $ gitflare route weight shop.example.com --to web@2026-09-19a --percent 100
Instant rollback
$ gitflare route rollback shop.example.com
Rollback points the hostname at the previous Worker tag. It does not rebuild anything. Typical time to take effect in Tokyo is under two seconds.
Origin health gates
If you still have an origin, attach a health check. Deploys pause when the origin 5xx rate is above 2% so you do not ship a Worker that depends on a sick database.
$ gitflare health create origin.example.com --path /healthz --interval 10