Discover
Normalize mixed estates into one inventory model.
Hypervisor-agnostic workload migration
Discover, validate, and move mixed virtualization estates through a shared control plane.
Viaduct gives operators one system for discovery, dependency-aware planning, migration orchestration, rollback and resume awareness, and post-cutover lifecycle visibility across mixed hypervisor estates.
Map
Model workload, storage, network, and backup dependencies.
Migrate
Use checkpoints, approvals, rollback, and resume-aware execution.
Operate
Track lifecycle posture, drift, policy, and cost after cutover.
Workflow
A controlled transit model from discovery through post-cutover operations.
Viaduct keeps the migration path legible: normalize the estate, model dependencies, validate cutover, execute with checkpoints, and keep lifecycle signals visible after the move.
01
Discover
Normalize mixed estates
02
Map
Model dependencies
03
Plan
Validate cutover
04
Migrate
Checkpoint and resume
05
Operate
Track drift and cost
Architecture
One control plane that keeps discovery, execution, and lifecycle state aligned.
Connectors feed a shared system of record, the core engines add dependency and execution logic, and the CLI, API, and dashboard all reflect the same persisted truth.
Connectors
Hypervisor and backup adapters with a restrained plugin model.
VMware
Proxmox
Hyper-V
KVM
Nutanix
Veeam
Community plugins
Core engines
A staged pipeline with shared context instead of siloed utilities.
Discovery engine
Concurrent, read-only collection normalizes inventory and infrastructure metadata into the universal model.
Dependency mapper
Cross-platform node and edge modeling exposes workload, storage, network, and backup relationships before execution.
Migration orchestrator
Declarative plans drive validation, wave execution, checkpoints, cutover, rollback, and resume behavior.
Lifecycle manager
Post-migration analysis keeps drift, cost, policy, portability, and remediation visible in the same control plane.
CLI / API / Dashboard
Operator surfaces that stay in parity because they read and write the same state.
CLI
Declarative specs, discovery, planning, status, and rollback.
API
Tenant-scoped routes for inventory, graphs, migration state, policy, reporting, and metrics.
Dashboard
Inventory, dependency, migration, lifecycle, and reporting views on one backend model.
Shared state / persistence
Execution context stays durable so retries, approvals, and rollback do not lose the thread.
Discovery snapshots
Baseline inventory, infrastructure, and historical diffs.
Migration state
Execution plans, approvals, checkpoints, and resume metadata.
Recovery points
Rollback artifacts and portability cleanup context.
Tenant metadata
Quotas, service accounts, permissions, and request-scoped context.
Execution model
Change remains explicit and operator-controlled.
Read-only discovery across mixed source platforms
Pre-flight validation, wave planning, approvals, and checkpoints before cutover
Lifecycle, policy, cost, and remediation remain visible after migration completes
Platform coverage
Connector coverage for real mixed estates, with a restrained extension path.
The platform row stays technical and quiet on purpose. Connector availability matters, but the real story is the shared migration and lifecycle control plane behind it.
VMware
vSphere inventory and migration planning
Proxmox
REST-backed discovery and target planning
Hyper-V
WinRM and PowerShell-driven collection
KVM
Libvirt-ready with portable fallback support
Nutanix
Prism-backed mixed-estate visibility
Veeam
Backup correlation and portability context
Community plugins
gRPC extension path with compatibility checks
Start in a lab
Evaluate Viaduct without needing a live hypervisor estate on day one.
The first-run path starts with the local KVM lab under `examples/lab/`, then expands into live discovery, dependency analysis, migration pilots, and dashboard-backed operations.