DATACLONE / MANAGED FILE TRANSFER
Move large datasets across difficult high-capacity WAN paths
Dataclone moves large files and datasets directly between the systems you control. It is built for difficult high-capacity WAN paths affected by latency and packet loss. Create and monitor transfer jobs in the Dataclone UI. An API-assisted workflow is also available.

IBC2026 / Amsterdam
Meet Dataclone at IBC2026
Discuss your large media and archive transfers with us and Anhalt University of Applied Sciences.
Product workflow
Configure, start and monitor transfers from one operator view.
Choose the participating systems and paths, select the files or directories, review the transfer options, then start and monitor the job.

One operator sequence
- Choose the participating systems and paths.
- Select the data and review the transfer options.
- Start and monitor the transfer in the UI.
Transport underneath
We built Dataclone around RMDT so fast transport comes with the controls operators need.
RMDT handles the direct payload path. Dataclone adds endpoint selection, job status and retry around it.
Deployment model
Files move directly between agents. You control each transfer.
Run the same Dataclone agent at each endpoint. Your files move directly between the agents over the connectivity you choose. Our separate on-premises control plane starts the job and reports status without relaying the payload.
Operator UI · API-assisted workflow
Control plane: orchestration + observation · Control/status, not payload relay
Control/status paths to both agents
Site A
Customer-controlled system
Dataclone agent
Agent A
Direct agent-to-agent payload path
Site B
Customer-controlled system
Dataclone agent
Agent B
Your connectivity. RMDT runs over existing IP infrastructure without proprietary network hardware. You choose the interface for the payload path.
Control-plane hosting. The diagram shows the customer-hosted option. Dataclone can also use a control plane hosted by Dexor by arrangement. In that model, the agents connect to the hosted controller while file payload still moves directly between the participating agents.
Read the architecture description
RMDT transport. We built it for high-capacity WAN paths affected by latency, jitter and packet loss. Route, hosts, storage, workload and configuration still shape the result.
How we test it
We agree the endpoints, route, workload and useful criteria before the run. When your current method gives us a meaningful baseline, we compare against it on the same path.
Your two sites run the same Dataclone agent software. Both agents connect to our separate on-premises control plane for job orchestration and status. The file payload moves directly between the agents over your connectivity; the control plane does not relay it. You operate the transfer through the Dataclone UI or an API workflow. Deployment and path prerequisites are reviewed during the technical discussion.
Why it moves faster
From hours to seconds across the WAN.
Dataclone is built to outperform conventional TCP-based file transfer on difficult high-capacity WAN paths.
Actual results depend on the route, hosts, storage, workload and configuration.
Documented 2024 lab test
Measured across latency and packet loss
Our documented 2024 lab tests used one 50 GB file on 1 Gbps and 10 Gbps paths across 0–400 ms RTT and 0–2% packet loss.
Review the hosts, MTU, storage and complete test matrix before comparing it with your path.
Where it fits
Bring us the transfer with a deadline.
Media, archive and research data are common starting points for Dataclone.
Media / production
Media masters and production packages
Move UHD masters, camera originals, audio stems and delivery manifests between production, post-production and archive sites inside the delivery window.
Backup / archive
Backup sets and archive migrations
Move backup sets, archive exports and large directory trees within a planned maintenance window.
Research / engineering
Research and engineering datasets
Send instrument output, simulation results and engineering data between laboratory, compute and long-term storage sites before the next compute or analysis stage.
Your next transfer
Bring us the route that slows you down.
Tell us what has to move, where it has to arrive and what the current transfer delivers. We will review the path and propose a useful next step.