Two apps on the Luca Infra fleet do the heavy lifting no team wants to do by hand. Azure Local Deploy brings up a brand-new Azure Local & Hyper-V data center — agentically, from bare metal to booted cluster. VOSJ then moves and replicates your workloads into it — governed, born-whole, and fast. Personas on devstations run the whole motion. You hold the kill-switch.
A migration is only as good as the place you land, and a new cluster is worthless until the work is running on it. Luca Infra ships both halves as governed apps on the same fleet — so standing up capacity and filling it is one continuous motion, not two projects handed between two teams.
An agentic day-zero provisioner. Point it at bare metal and it validates the hardware, lays the network fabric, creates the cluster, builds the storage pool, wires Azure Arc, stands up the Hyper-V hosts — and hands you a booted, governed cluster ready for workloads. Every step is a ticket; every destructive act stops for a human.
See the deploy appThe workload mover. VOSJ assesses what you run today, plans it into waves, replicates each workload to the new cluster while the old one keeps serving, then cuts over on a gated confirm. Drag a card across the board and you launch one governed migration wave — across Azure, Azure Local and Hyper-V.
See the Voyage BoardStanding up Azure Local by hand is days of console work across a dozen disciplines — hardware, network, clustering, storage, Arc, virtualization. Azure Local Deploy turns the whole day-zero into one declared plan that a fleet of personas executes step by step, on your real nodes, inside the guardrails. New capacity for Azure Local and Hyper-V, without a war room.
Hardware validation, network fabric, cluster, storage, Arc and Hyper-V — one declared plan applied end-to-end, on real Azure Local nodes.
The same plan stands up the hyperconverged cluster and the Hyper-V compute fabric on top of it — ready to host VMs the moment it boots.
Real change is gated by a fleet flag and a human confirm on every destructive step. Run the whole plan in dry-run first; nothing touches hardware until you say so.
Every deploy is a blueprint, playbook and runbook — so the next data center is a repeat, not a rediscovery.
VOSJ is the migration platform — the Voyage Board. It reads what you run today, plans it into waves, and moves each workload to the new cluster by replicating it first and cutting over last. Across Azure, Azure Local and Hyper-V, a migration stops being a spreadsheet and a maintenance window, and becomes a card you drag.
| → Azure Local | → Hyper-V | → Azure | |
|---|---|---|---|
| Hyper-V | livemigrate + replicate | livehost to host | soonlift to cloud |
| Azure Local | livecluster to cluster | livede-converge | soonburst to cloud |
| Azure | liverepatriate | sooncloud to HV | soonregion move |
| VMware | soononboard | soononboard | — |
VOSJ streams a workload to the destination while the source keeps serving. The switch is a short, gated cutover — not a long dark maintenance window. Downtime shrinks to the cutover, not the copy.
Until cutover completes, the source is untouched and authoritative. If a check fails, the wave reverses on the path it came in on — no half-migrated limbo.
Each wave is created complete — assessment, path, tickets and rollback plan together — so a migration can never start half-defined or lose track of what it was moving.
Behind the card is a deterministic engine. A drag chooses a recipe; the recipe resolves a path; the path compiles a workflow; each stage of the workflow becomes a Luca Infra ticket; a specialized migration persona picks up each ticket and keeps the flow moving — cogs meshed, oil flowing — and steps in when a stage gets stuck. Fast because it is parallel and governed; easy because you only ever touch the board.
The source→target pair selects a proven recipe — the shape of this kind of move.
codex · recipeThe recipe resolves against the real workload into a concrete path with checkpoints.
codex · blueprintThe path compiles into ordered stages — assess, replicate, verify, cut over, reconcile.
codex · playbookEvery stage opens a governed ticket on the Luca Infra board — attributed, gated, logged.
luca infra · ticketThe migration persona works each ticket on its devstation, and unblocks the stuck ones.
devstation · migrationNeither app is a script with a login. Each stage of a deploy or a migration is a ticket, and each ticket is picked up by a persona on its own devstation — a human engineer and their AI twin sharing one declared flavor, one capability set, one set of rules. The board is the shop floor; the personas are the crew that keeps it moving.
Owns the voyage. Works each stage ticket — assess, replicate, verify, cut over — and when a stage stalls, it diagnoses and unblocks instead of leaving a card stuck. It keeps the cogs meshed and the oil flowing.
Runs the day-zero deploy: hardware, cluster, storage and the Hyper-V fabric — driving iDRAC, OpenManage and Azure Local as code. The same flavor that operates the fleet stands up new capacity for it.
Every persona lives on a Luca Express devstation — a governed, isolated seat with exactly the tools, access and credentials its flavor declares. Nothing hand-wired; nothing left on the desk after the work is done.
Reversible steps run unattended; every destructive step — a cutover, a cluster wipe, an Arc grant — stops for a distinct human, is attributed server-side, and answers to one master kill-switch held by the owner.
Azure Local Deploy and VOSJ run on the Luca Express fleet — the same platform that builds Luca and operates Luca's own data center. Book a demo to bring up a cluster and move a workload live, or head back to see the whole Luca Infra estate.
Demos, pricing and pilots on your own hardware — a live cluster bring-up and a real workload moved. Sales is handled by our partner Messina LLC.
+1 (888) 996-8530 · AI sales line, 24/7Azure Local Deploy and VOSJ are two apps on the Luca Infra fleet. See the Dell integration, the flavor crew and the governance model that run underneath them.
lucainfra.com → Watch it being built →