Yorigu separates recovery and migration into explicit phases so infrastructure teams can review readiness and progress.
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. Source workloads enter recovery and migration workflows without persistent Yorigu software installed on them.
Coordinates Provision, Sync, Validate, Failover, and Failback / Cutover phases 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.
A continuous lifecycle. The system stays in a recovery-ready state and can return after a failover.
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.
