Migration Engine

The migration-engine changes your infrastructure layout without a maintenance window, using a green-blue cutover with health gates at every step.

The flow

provision green ──▶ replicate state ──▶ health gate ──▶ cutover traffic ──▶ drain blue

1. Provision green — the new layout is stood up alongside the live blue one.
2. Replicate — state is copied to green.
3. Health gate — nothing proceeds until green is healthy.
4. Cutover — traffic shifts to green.
5. Drain blue — the old layout is drained; you can roll back until the final commit.

API

Endpoint	Purpose
POST /v1/plan	Return the migration action list
POST /v1/apply	Execute the migration
POST /v1/cancel	Abort an in-flight migration

State is tracked by the engine; with TEMPORAL_HOST set it runs on a Temporal backend for durability, otherwise in-process.

From the CLI

pdctl topology migrate            # start
pdctl topology migration list               # in-flight + history
pdctl topology migration show <id>
pdctl topology migration logs <id>
pdctl topology migration pause <id>
pdctl topology migration resume <id>
pdctl topology migration rollback <id>

Because every step is health-gated, a bad migration stops itself rather than taking the live system with it.

→ Marketing overview: Migration Engine