Terabytes per capture
Orthomosaics, LiDAR tiles and raw frames add up quickly. Cellular and satellite backhaul is high-latency and lossy, which is exactly where TCP transfers lose most of their bandwidth.
Geospatial & survey
Get imagery, LiDAR and survey data from the field to the office in one move.
A day of drone capture or a mobile-mapping run produces terabytes of tiles, point clouds and logs, usually at a site with a poor connection and a client waiting elsewhere. RIPTON CLOUD moves the whole capture as one package and resumes if the link drops.
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
Field capture drive
02
RIPTON Desktop at the site or office
03
RIPTON node at the processing centre
04
Processing storage
Field to office
The data is collected. Getting it home is the slow part.
Geospatial teams produce large, file-heavy datasets far from good networks and deliver them to clients who are further still. Shipping drives is the usual fallback, and it costs days.
Thousands of tiles
Tiled rasters and point-cloud chunks are many files. Each one handled separately by a transfer tool becomes overhead.
Clients and agencies on their own systems
Deliverables go to municipalities, utilities and engineering firms who will not install a client or create an account.
Workflows
Where the transfer path matters most.
Drone · mobile mapping · terrestrial scans
Field capture to processing
Package the capture folder on the field laptop and send it to the processing centre's node. Interruptions resume from where they stopped.
Surveys · as-builts · inspection reports
Deliverables to clients
Send finished orthomosaics, DEMs and point clouds as a package to named recipients. They download from a browser with a scoped link and no account.
Project close-out · retention copies
Archive to a second site
Schedule project archives to a node at another office or region so the raw capture exists in two places.
RIPTON CLOUD in the workflow
What a survey team gets
The product earns its place by moving prepared data between endpoints—not by claiming ownership of every system around it.
Built for lossy links
The RIPT protocol is UDP-based with rate control and block retransmission, designed for exactly the high-latency, lossy backhaul field sites have.
Tiles as one package
Any number of tiles or chunks travel as a single package with the folder structure kept, so processing pipelines find files where they expect them.
Resume, not restart
A dropped connection resumes the package from where it stopped rather than starting the day's capture again.
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 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, not processing.
RIPTON CLOUD moves the data. Photogrammetry, classification and GIS publishing stay in the tools you already use.
What it covers
- Field captures sent as packages
- Client deliverables with scoped links
- Scheduled archive copies between sites
- Delivery and download records
What stays with your stack
- Photogrammetry or point-cloud processing
- GIS hosting or map tile serving
- Continuous folder sync
- Backup software
Evaluation path
Test it from a real site
The evaluation that matters is from the connection you actually have in the field. Bring one capture and the route it takes home.
- 01
Choose the capture
A real day's output, tiles and all, from the drive it lands on.
- 02
Send from the site link
Cellular, satellite or the hotel Wi-Fi. Measure elapsed time and how many times it needed a restart with each tool.
- 03
Deliver to a client
Send the processed output to a client contact and confirm they could download without help.
- 04
Decide on numbers
Hours saved per capture and operator time, written down.
FAQ
Questions technical buyers ask.
Does it work over cellular or satellite backhaul?
That is the environment the protocol is designed for: high latency and packet loss. How much faster it is than your current tool depends on the link; the evaluation measures it.
Do clients need to install anything?
No. Recipients download from a browser with a scoped link. They do not need an account or a paid seat.
Is there a file-size limit?
10 GB per file on Free, 100 GB on Starter, and no file-size limit from Professional up. Folder packages can contain any number of files within the plan's monthly transfer allowance.
Can transfers run unattended?
From Professional, watch folders and schedules move packages without an operator, with webhooks on completion.
Technical evaluation
Stop shipping drives.
Start a free workspace, or bring one field capture and the route it takes and we will help you measure it.