Operations · Deployment

Place the migration runtime close to the data path.

Omni Loader publishes self-contained artifacts for Windows x64, Linux x64, Linux ARM64, and macOS ARM64. Its normal desktop-like mode binds to an ephemeral loopback port and opens the local browser.

Plan my migration Explore automation

Why this path matters

Use the browser interface without exposing a shared service.

When no URL is supplied, Omni Loader listens on an ephemeral loopback port and opens a browser on the same machine.

What changes for you

Network exposure is an operator decision.

The runtime can bind another HTTP or HTTPS address, but the current product does not provide individual user login, RBAC, or tenant isolation. Keep access inside a controlled administrative boundary.

The payoff

See what the capability changes.

4 builds

Common server platforms

Windows, Linux x64, Linux ARM64, and macOS ARM64.

Loopback

Safe local default

Keep the operator interface local unless binding is explicit.

Self-contained

Packaged runtime

Deploy without assembling a separate application server.

Where the work happens

The details that make the result usable.

At a glance

A visual summary of the work.

Illustration of Omni Loader deployment across operating environments

Place by data gravity

Reduce avoidable network distance.

Install the runtime where it can reach the source, target, object storage, drivers, and temporary disk with the throughput and credentials required for the migration.

Take the next step

Put Omni Loader where the migration can run efficiently.

Map source and target reachability, driver requirements, temporary storage, credentials, and the administrative access boundary.

Plan my migration