A finite provider registry
Typed adapters cover Vultr, Cloudflare DNS, Kubernetes Deployments, Microsoft Entra policy, bounded REST APIs, Proxmox VM/LXC, vSphere VM, and Nutanix VM resources.
Infrastructure operations
Understand the change before you apply it.
Review desired state, provider scope and recovery before a controlled infrastructure operation.
A change you can inspect
Move from current state to a controlled next step.
Infrastructure operations
Desired state, approved plan, provider read-back, and rollback evidenceInfrastructure planIllustrative change
+ add managed firewall rule~ update server policy reference· retain regional network· retain storage attachment
Proposed changeNo action has run
Illustrative workflow · explore the steps · no action is executed
01
Define or import state
Create a tenant-scoped desired-state version or import a supported provider resource into managed ownership.
Confirm this step for your release, permissions and environment.02
Plan and approve
Lock the relevant state, preview exact provider operations, and obtain the policy-required approval.
Confirm this step for your release, permissions and environment.03
Apply and verify
Execute through the provider adapter, read back actual state, release the lock, and store recovery evidence.
Confirm this step for your release, permissions and environment.Separate the plan from the apply—and make rollback part of the decision.
Generate a bounded plan against current provider state before any mutation.
Bind apply to an approved plan, state version, lock, provider evidence, post-check, and rollback record.
Inside the workflow
The work this connects.
- Native desired-state engine
- Version resource intent, provider references, dependencies, ownership, and state without outsourcing the control plane.
- Plan, apply, and locks
- Prevent overlapping mutations and bind every accepted run to an exact state version and reviewed plan.
- Drift and import
- Compare managed intent with provider reality and safely bring supported existing resources under management.
- Rollback evidence
- Capture before-and-after state, provider responses, read-back, and the bounded recovery path for each run.
- Supported provider adapters
- Operate approved resource types across Vultr, Cloudflare DNS, Kubernetes, Microsoft Entra, generic REST, Proxmox, vSphere, and Nutanix.
- Reusable runbooks
- Connect approved infrastructure workflows to documentation, automation, incidents, and change evidence.
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. Recovery branch: refresh the dependency graph, replace the stale plan and obtain fresh approval. If safe recovery is required but neither rollback nor an approved compensating action exists, stop before applying. A later compensating change is not proof that the original state was restored.
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 and resource coverage is finite and must be verified against the current integration evidence for the intended environment.
No unreviewed apply is claimed; changed state, expired approval, missing lock, or unsupported rollback blocks execution.
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
Provider trust boundary
Credentials remain in the Digital Vault; TLS validation, optional custom CA or certificate pinning where supported, immutable plans, approval, locking, idempotency, provider read-back, drift, and rollback govern execution.
Infrastructure operations use purpose-bound provider credential references and link plans to automation, runbooks, incidents, reporting, and audit.
Questions, answered
Before you choose your next step.
Is infrastructure automation a wrapper around an external IaC runner?
No. Dayrook provides the first-party desired-state, plan, approval, lock, drift, and evidence control plane described here.
Which infrastructure resources can it manage?
Support is finite and provider-specific. The integration directory documents evaluation scope and evidence status; current resource and operation support must be verified before purchase.
Can it import existing resources?
Yes, for supported types. Import establishes explicit ownership and state before later plans can manage the resource.
What happens if an apply fails?
The run preserves provider and read-back evidence, releases or recovers its lock through policy, and presents the supported retry or rollback path.