Elapsed time
Wall-clock time from start to verified completion, per run, for both tools.
Proof of concept
Two weeks. Your route. Your current tool as the baseline. Numbers you keep.
A proof of concept is a defined test, not a demo. We put a transfer node next to your storage, run the same files over the same route with what you use today and with RIPTON CLOUD, and write down what happened. It costs nothing and ends with a document your technical team can use whatever you decide.
No generic speed promise. The result is whatever your route produces, written down with the conditions.
Duration
14 days
first call to written result
Cost
$0
no card, no commitment
Scope
1 to 2 routes
your files, your baseline tool
Who it is for
Teams with a route that already hurts.
A facility that waits overnight for deliverables, a research group moving datasets to compute, a partner exchange that fails at 90 percent, an FTP server everyone wants gone. If you can name the route and the file set, you are ready. If you are still exploring, start with the calculator or the Free plan.
How it runs
Four steps, fourteen days.
- 01
Day 1: define the route
A 30-minute call to pick one or two real routes, the file set, the tool you use today, and the numbers that would make the decision: elapsed time, retries, operator effort, delivered file count.
- 02
Days 2 to 3: set up
A RIPTON node next to your storage on each end, in your cloud or on your hardware, and RIPTON Desktop on the operator workstation. We do it with you; typical setup is under an hour per site.
- 03
Days 4 to 10: run both
The same file set on the same route with your current tool and with RIPTON CLOUD, at the times of day that matter to you. Interrupt one run on purpose to see resume behaviour.
- 04
Days 11 to 14: write it down
A short results document: conditions, commands, versions, timestamps and numbers for both tools, plus what did not work. Yours to keep and share internally whatever you decide.
What we measure
The same six things, for both tools.
Delivered files
File count and bytes on the far side, checked against the source, including for file-heavy directories.
Interruptions
What happened when a run was stopped: resumed, restarted, or failed, and how much was repeated.
Operator effort
Who had to do what on each end, and how many steps a recipient needed.
Link conditions
Measured latency, loss and available bandwidth on the route during the runs, so the result can be reproduced.
Security behaviour
Which credentials were issued, how long they lived, and what the audit log recorded.
What you provide
- A representative file set, or a copy with the same shape: same file count, sizes and structure.
- One or two routes with a person at each end who can run the current tool.
- A place for a transfer node at each site: a VM or instance in your cloud, or a machine on your network, with access to the storage.
- Your current transfer's timings, if you have them, so the baseline is yours rather than ours.
What you get
- A results document with the conditions, commands, versions and numbers, written for your technical team.
- The RIPTON CLOUD workspace and nodes left running on the Free plan, so the route keeps working after the test.
- A plan recommendation based on the volume you actually moved, with the published prices, or a clear statement that RIPTON CLOUD is not the right fit.
FAQ
Questions before you commit two weeks.
What does the proof of concept cost?
Nothing. No card, no commitment. If RIPTON CLOUD is not meaningfully better on your route, you keep the results document and we part on good terms.
How long does it take?
Two weeks from the first call to the written result, assuming a node can be placed at each site in the first days. Simple single-route tests often finish sooner.
Do we have to expose our storage or data to RIPTON?
No. Transfer nodes run on infrastructure you control, next to your storage, and the files move between your nodes. The hosted control plane authorises and records transfers; it does not hold the files.
Can we test a browser-only workflow?
Yes. Web Edge transfers from a browser through your node are part of the test if that is how your senders work. The accelerated RIPT path needs RIPTON Desktop or a node on both ends.
Can we publish or share the results?
The results document is yours. We will ask, at the end, whether you are willing to be a reference or a case study; that is separate and entirely your choice.
What if our partner is the other end?
Partners can receive with a browser link and no software. For an accelerated partner route, the partner runs a node or RIPTON Desktop for the test; we will help them set it up.
Request
Tell us the route.
Where the files start, where they need to go, roughly how big and how many, and what you use today. A rough answer is enough; the first call fills in the rest.