01Map
LinkedHost, guest, and dependency
Virtualization
See the host behind the guest—and the impact of a change.
Explore virtual infrastructure in client context, from inventory and health to lifecycle tasks. Check your exact hypervisor version, connector and recovery requirements.
A change you can inspect
Move from current state to a controlled next step.
Virtualization management
Host, guest, provider action, and outcome in one recordHost and guest operationProvider support varies
02Observe
CurrentHealth and capacity context
03Change
HeldSupported action reviewed
04Recover
DefinedSnapshot and backup distinguished
Illustrative workflow · explore the steps · no action is executed
01
Connect the platform
Add a supported hypervisor or management plane with a scoped Digital Vault credential and verified TLS identity.
Confirm this step for your release, permissions and environment.02
Map hosts and guests
Normalize provider inventory, metrics, storage, networks, and placement into the correct customer and site context.
Confirm this step for your release, permissions and environment.03
Review and operate
Choose a supported action, validate provider and policy constraints, obtain approval when required, and read back state.
Confirm this step for your release, permissions and environment.Keep host, guest, snapshot, workload, and recovery context connected.
Map supported hosts, guests, workloads, snapshots, and health into the client record.
Move approved power, snapshot, backup, and recovery work through policy and evidence.
Inside the workflow
The work this connects.
- Broad platform inventory
- Cover supported VMware vSphere and ESXi, Hyper-V, Proxmox, KVM and libvirt, and Nutanix AHV environments.
- Host and guest relationships
- See cluster, host, VM, storage, network, and customer dependencies together.
- Capacity and health
- Track supported CPU, memory, storage, network, availability, and placement signals.
- Lifecycle actions
- Perform provider-supported power, snapshot, migration, clone, and guest-script workflows.
- Backup context
- Connect virtual-machine identity and restore points to endpoint backup, incidents, and runbooks.
- Recovery controls
- Govern break-glass access and supported disk-encryption recovery with explicit authorization and audit.
Try one useful scenario
A stale plan must stop before apply
Fictional example: a power-change plan targets a host with two dependent services. Inventory changes after approval. The evaluator expects a stale-plan stop and a new impact review.
Illustrative evaluation scenario, not a recorded product result.What a useful result must show
Capture provider resource ID, dependency snapshot, plan version, authority, stale-state result and recovery prerequisites. Verify actual provider state after any permitted apply.
Get the evaluation worksheet →Check the support boundaries
- Provider/resource inventory versus create/update/delete/import
- Console, snapshot, clone and migration prerequisites
- Guest actions and host/service dependencies
- Rollback, compensation and unavailable recovery
Inventory visibility does not prove mutation support. Rollback restores prior state only where supported; compensation is a different action. Missing required recovery should block the evaluated action.
Check public evidence and availability →Scope, availability and evaluation details
Provider, version, resource, snapshot, console, and mutation coverage must be verified against current release evidence.
A snapshot is not presented as a verified application-consistent backup unless the recovery workflow proves it.
The proposed $99 monthly model includes the target product scope for evaluation, unlimited technicians, unlimited customers, and the first 50 managed devices. Final terms require confirmation. See transparent pricing →
Review full environment and integration scope
Inventory across major hypervisors
Provider connectors and host agents normalize supported VMware vSphere and ESXi, Hyper-V, Proxmox, KVM/libvirt, and Nutanix AHV hosts and guests into customer and site context.
Operations follow a capability matrix
Typed infrastructure adapters govern supported Proxmox, vSphere, and Nutanix mutations; other platforms expose only the inventory and actions their connector can verify, with Digital Vault credentials and provider read-back.
Virtualization connects provider inventory to infrastructure operations, endpoint operations, backup, alerts, service work, and reporting.
Questions, answered
Before you choose your next step.
Which virtualization platforms are covered?
The target scope includes VMware vSphere and ESXi, Hyper-V, Proxmox, KVM/libvirt and Nutanix AHV. Inventory support is not the same as permission to run lifecycle actions. Confirm your connector, host version, available operations and current deployed evidence during evaluation.
Can technicians manage VM snapshots?
Yes where the connected provider and resource type support it. Snapshot operations remain policy-controlled and auditable.
Does every provider support migration and cloning?
No. Dayrook follows a finite provider capability matrix and does not present unsupported actions as available.
How are hypervisor credentials handled?
Connections use scoped Digital Vault references with tenant binding and strict provider identity checks.