Runs in the hundreds of gigabytes
Sequencers and high-content imagers produce more data per run every year. Ordinary tools over a long route turn overnight runs into next-day arrivals.
Life sciences
Move sequencing runs, imaging and study data between sites, CROs and sponsors.
A sequencing run is hundreds of gigabytes of FASTQ and BAM files; a microscopy session is tens of thousands of images. They move between the instrument, the analysis cluster, a CRO and a sponsor, all on different networks. RIPTON CLOUD moves each run as one package with a record of who received it.
Plan limits are those published on the pricing page. Benchmark figures come from RIPTON CLOUD's published EC2 test at roughly 150 ms latency and 3% packet loss. Results on your route depend on your network, endpoints and storage. RIPTON CLOUD does not claim any industry certification on this page.
Evaluated transfer path
01
Instrument or lab storage
02
RIPTON Desktop or scheduled transfer
03
RIPTON node at the analysis site
04
Cluster or sponsor storage
Between organisations
The run finished overnight. The analysis site is somewhere else.
Life-sciences data is produced by instruments in one organisation and analysed, reviewed and submitted by others. Each handoff is large, must be traceable, and usually crosses a long route.
Thousands of files per session
Imaging and multi-sample runs are file-heavy. Per-file overhead dominates with tools that were built for documents.
CROs, sponsors and sites on separate networks
Data moves between organisations that must not share credentials or drives, and every delivery has to be accounted for.
Workflows
Where the transfer path matters most.
FASTQ · BAM · imaging sessions
Instrument to analysis
Schedule the run's output folder to the analysis site's node. The structure arrives intact for the pipeline, with a completion record.
Study data · reports · submissions
Lab to CRO and sponsor
Send study packages to named recipients at a CRO or sponsor. Each recipient gets a scoped link and the download is recorded.
Site uploads · sample manifests · images
Inbound from sites
Give clinical or partner sites a Shared Inbox so they send data from a browser with no account on your systems.
RIPTON CLOUD in the workflow
What a lab gets
The product earns its place by moving prepared data between endpoints—not by claiming ownership of every system around it.
Runs as one package
Any number of files travel and are stored as a single package with the tree kept for the pipeline.
A record of every delivery
Who was sent what, when it was downloaded and by whom, in the audit log rather than in an email thread.
Your nodes, your storage
Transfer nodes run on infrastructure you control, on-premises or in your cloud tenancy, beside the storage the instruments write to.
Encrypted on every packet
AES-256-GCM or ChaCha20-Poly1305 with a forward-secret key per session and replay protection. There is no plaintext mode to misconfigure.
No compliance shortcut
RIPTON CLOUD gives you encryption on every packet, roles, audit logs and delivery records. It does not claim HIPAA, GxP or 21 CFR Part 11 certification. Your validation is yours to run, and we will supply the design documents for it.
No generic speed promise
Throughput depends on your route, endpoints, and storage. The published benchmark (a 1 GB file 7.5x faster than the TCP baseline at 150 ms and 3% loss) tells you where the difference appears; your own route tells you how much.
Product boundary
Transfer, with evidence.
RIPTON CLOUD moves data between organisations and records the movement. It does not analyse, store long-term, or validate your process for you.
What it covers
- Runs and studies sent as packages
- Scheduled instrument-to-analysis transfers
- Inbound data from sites and partners
- Audit logs and delivery records
What stays with your stack
- Bioinformatics or image analysis
- LIMS or EDC systems
- Long-term archive or backup
- Regulatory certification claims
Evaluation path
Test it on one run
Pick the handoff that delays analysis or a submission and measure both tools on the same route.
- 01
Choose the handoff
Instrument to cluster, lab to CRO or site to sponsor. One route.
- 02
Send one run
The whole output folder, elapsed time and restarts recorded with each tool.
- 03
Review the record
Confirm the audit log and delivery record show what your quality team needs.
- 04
Decide on numbers
Hours from run end to data at the analysis site, written down.
FAQ
Questions technical buyers ask.
Is RIPTON CLOUD HIPAA or GxP certified?
No certification is claimed on this page. The product provides mandatory encryption, roles, audit logs and delivery records, and we supply design documentation for your own validation and risk assessment.
Can sites and CROs send without accounts?
Yes. A Shared Inbox or public upload link lets external senders use a browser with no named seat and no charge on your side.
Where does the data sit in transit?
On transfer nodes you run, on-premises or in your cloud tenancy. The hosted control plane carries metadata and authorisation, not the file content.
Can transfers run from the instrument automatically?
From Professional, watch folders and schedules move a run's output folder without an operator, with webhooks on completion.
Technical evaluation
Get the run to the people waiting for it.
Start a free workspace, or bring one instrument-to-analysis route and we will help you measure it.