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.

Two customer-controlled Dataclone endpoints connected directly across a world map.

IBC2026 / Amsterdam

Meet Dataclone at IBC2026

Discuss your large media and archive transfers with us and Anhalt University of Applied Sciences.

11-14 September 2026 · Hall 7 / Stand 7.A48 · Available by appointment

Managed file transfer for large datasets

Move fast. Keep control. Operate every transfer.

Dataclone combines direct transport with the operational controls required for recurring file movement.

Developed in Germany

Direct payload path
File payload moves directly between participating Dataclone agents over customer-provided connectivity. You select the interface used for the payload path.
Managed workflow
Use reusable templates, scheduling, queueing, history, retry and notifications to operate recurring transfers.
Access and audit
Roles and workspace permissions control access. Audit records can be reviewed and exported.

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.

Dataclone Browse view with six media files selected at STUDIO and an empty ARCHIVE destination, ready to start transfer.
Select the image to view a larger version.

One operator sequence

  1. Choose the participating systems and paths.
  2. Select the data and review the transfer options.
  3. 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.

Explore RMDT transport

Review deployment requirements

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.

Dataclone direct-path model

On-prem deployment

Dataclone direct-path architecture Two customer-controlled systems each contain one Dataclone software agent. A direct payload path joins the agents through customer-provided WAN connectivity. A separate on-premises control plane reaches the two agents through two independent control and status routes and does not relay payload. OPERATOR UI + API ON-PREM CONTROL PLANE Orchestration + observation control/status · not payload relay CONTROL / STATUS SITE A SITE B AGENT A AGENT B DIRECT AGENT-TO-AGENT PAYLOADRMDT / CUSTOMER-PROVIDED WAN Customer-controlled system Dataclone agent A inside Customer-controlled system Dataclone agent B inside Dataclone direct-path model Site A and Site B are arranged horizontally. Each customer-controlled system contains a Dataclone agent facing the direct payload path. Separate foreground control and status routes connect both agents to an on-prem control plane above. The opaque WAN cloud hides the payload while it crosses existing connectivity. SITE ACustomer-controlled system DatacloneAgent SITE BCustomer-controlled system DatacloneAgent DIRECT AGENT-TO-AGENT PATH ON-PREM CONTROL PLANEOperator / UI + APIInitiate · observe · retryOrchestrationControl and status onlyCONTROL / STATUS WAN Vertical mobile Dataclone direct-path modelSite A and Site B are arranged vertically. The direct payload path crosses an opaque WAN cloud beside the on-prem control plane. Separate control and status routes connect the control plane to both agents. SITE ACustomer-controlled systemDatacloneAgent DatacloneAgentSITE BCustomer-controlled system DIRECT PATHAgent-to-agent ON-PREM CONTROLOperator / UI + APIStart · monitor · retryOrchestrationControl / status onlyCONTROL / STATUS WAN

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.

Explore Dataclone managed file transfer

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.