How it works

EdgeShift is built around one constraint: every customer-visible change is delivered as a PR with a preview URL. Nothing auto-merges.

Launch workflow

1. Inventory + Migration Score
2. First Preview PR (early templates + preview URL)
3. Build templates + migrate content/media
4. QA checks (links, redirects, sitemap/robots, metadata parity, sanitization, performance budgets)
5. Cutover with rollback plan
6. Start Change Lane (monthly request credits)

Change Lane workflow (ongoing)

1. You submit a request (Slack/email/issue)
2. EdgeShift opens a PR with a Cloudflare Pages preview URL
3. You review and request edits (up to 2 review rounds per credit)
4. You approve
5. Human merges → Cloudflare deploys to production