Yorigu separates recovery and migration into explicit phases so readiness and progress remain visible.
The orchestrator runs inside the customer's controlled infrastructure; workload data and workflow state remain in the customer environment. For product-specific behavior, supported platforms, and packaging options, see the Products section.
Physical Servers, Virtual Machines, and DB Systems running in the customer's existing environment. When additional evidence is useful, source assessment can include VMware inventory visibility, OS/source access readiness, and DB footprint discovery without persistent Yorigu software installed on source workloads.
Coordinates Provision, Sync, Validate, Failover, Failback / Cutover, and Application Recovery Plans from a customer-controlled deployment. There is no Yorigu cloud in the workload data path.
OCI and Proxmox VE follow separate delivery models with platform-specific validation and rollout requirements.
Assessment, target preparation, sync and validation, failover, target operation, and failback remain visible as separate phases.
Yorigu does not impose fixed recovery numbers. Recovery point and recovery time objectives are defined against the environment during scope, and workflow validation produces evidence against those targets.
A one-time transition. The system moves from source to target and the lifecycle ends after validation.
