Not yet released

Move your Azure VMs into availability zones.
Bring them up to Trusted launch.

Wormhole is a desktop application for the Azure virtual machines you already have. It moves machines that were deployed without a zone into availability zones, and raises existing machines to Generation 2 with Trusted launch, across as many at a time as you choose.

Windows, macOS and Linux · Sign-in to Azure happens inside the application · No Azure CLI or PowerShell to install

Choosing machines for a zone migration plan: each machine with its generation and Trusted launch state. Machines already in a zone are greyed out, and one with an ephemeral OS disk is named as unmovable.
Choosing machines for a plan. Machines already in a zone are greyed out; one that can't be moved is named. Invented estate; names and timings are illustrative.

Checked first

Machines that can't be changed are refused up front

Assessment is read-only and changes nothing. It reports blockers, quota and capacity limits, and whether a machine's generation can be raised, before a single machine is stopped.

Blockers include an availability set, a proximity placement group, an ephemeral disk, an unmanaged disk and a machine protected by Site Recovery. Structural changes, such as leaving an availability set, are listed and have to be accepted per machine before a plan will run.

Testing a plan in Wormhole: one machine blocked by a Basic SKU public IP, the other machines passing their checks, and an offer to remove the blocked machine and continue.
Testing a plan: one machine is blocked, and Wormhole offers to continue without it. Invented estate; names and timings are illustrative.

How a migration runs

Plan it once. Test it with nothing changed. Run it in the window.

  1. 1

    Assess

    Read-only checks across the estate: blockers, quota, capacity, generation.

  2. 2

    Plan

    Choose the operation and the machines, cut them into waves, and accept what changes.

  3. 3

    Test

    Every check the run makes, with the machines left running. Zone moves submit the exact request to Azure while the original still exists.

  4. 4

    Run

    Progress per machine. Every step is journalled, so an interrupted run resumes instead of starting again.

How it works in detail

A zone migration running in Wormhole: each machine's phases, the machines past the point of no return marked in red, and the run's journal below.
A run in progress. Machines past the point of no return are marked, and the journal records every step. Invented estate; names and timings are illustrative.

Honest about risk

You always know which side of the point of no return you're on

A zone move deletes the original machine at a defined step, and raising a generation rewrites its disk. Before that step, stopping the run leaves the machine as it was. After it, recovery rebuilds from the run's record. The watch window draws the boundary and says how many machines are past it.

Turning on Trusted launch has no point of no return: nothing is deleted, and Azure will remove the setting again on request.

Wormhole stops, rebuilds and deletes virtual machines, and some operations are irreversible. The licence requires you to keep verified backups.

Your data stays in your Azure

Wormhole runs on your machine and talks to Azure directly. Customer data stays in the customer's own Azure.

Built for change control

The operator manual ships inside the application, so it can be read on change-controlled and air-gapped estates. Reports are derived from the run's journal.

Made for MSPs too

The licence distinguishes your own subscriptions from a service-provider entitlement for your clients'. For MSPs →

Wormhole hasn't been released yet

It can't be downloaded, bought or subscribed to yet, and no price is published. When it is released it will be sold on kelomai.io as an annual subscription. Assessment and planning will be free; only migration will need a subscription.