This document calls a system that stores and manages training data separately the DataOps server. The platform connects to that server, downloads a dataset and makes it a platform dataset.

SideRoleOwner
DataOps serverHTTP REST server — three APIs: list · manifest · fileThe side that has the data
MLOps Central PlatformHTTP client — connects, compares and downloads when a user presses a buttonThe platform

The DataOps server only needs to provide three query/download endpoints for the data it holds. The direction is Pull only; there is no feature that sends data from the platform up to DataOps.

Direction of the DataOps link: when the AI developer presses sync, the platform calls the DataOps server's list, manifest and file APIs with a Bearer token, compares the manifest and applies only the changed files to the dataset. Uploaded files stay as they are, and nothing is pushed back to DataOps

What a sync does

When you press sync, the platform compares the remote manifest with the dataset's files line by line. For example:

Remote manifestFile in the datasetOrigin of that fileResult
f-0001 a.png, sha256 9f8a…a.png, sha256 9f8a… (same)synckeep
f-0002 b.png, sha256 77c1…b.png, sha256 12de… (differs)syncfetch again, replacing the same row
f-0003 c.pngnonenonefetch new
noned.pngsyncdelete
f-0005 e.pnge.png (same name only)uploadskip with a warning
nonex.pnguploadleave alone
  1. It reads the remote manifest (file list + SHA-256).
  2. It compares it by file_id · sha256 with the files received through sync already in this dataset.
  3. It downloads only new and changed files, and deletes files that have disappeared from the remote.
  4. Received files take exactly the same path as directly uploaded files — the same validators, the same aggregation, the same rewrite of manifest.json. Training does not depend on how a file came in.

Order of this section

  1. The three APIs the DataOps server implements — for developers on the data provider side
  2. Reference implementation — a minimal server that uses only the standard library
  3. Connect to the platform — register a source → test the connection → create a dataset → see the result
  4. Sync rules and limits

Written for the platform as of 2026-10-02.

© MLOps Central Platform