Migration

01 — Request access

Every request is read by an engineer and reviewed for fit — petabyte-scale, sequential-read workloads first. Approval returns an endpoint and keys, plus a migration plan sized to your dataset and scheduled against the 100 Gbps floor. No card. No commitment.

Request access on ramo.io

02 — Mirror the bucket

Standard tooling points at any S3 endpoint today — checksum-verified with rclone, or aws s3 sync with the same bucket layout.

# register ramo as an S3 remote (once)
$ rclone config create ramo s3 \
      provider=Other \
      endpoint=https://s3.ramo.io
# mirror the bucket, checksum-verified
$ rclone sync s3:training-corpus \
      ramo:training-corpus \
      --transfers 64 --checksum --progress

03 — Read from any cloud, at $0

Point training jobs at the endpoint and pull at line rate — into AWS, GCP, Azure, or your own racks. The read is free either way.

# read from any cloud — $0 either way
$ aws s3 cp \
      s3://training-corpus/00417.tar - \
      --endpoint-url https://s3.ramo.io \
      | tar -xf - -C /data