Models and scans in the tens of gigabytes
Federated BIM models, laser-scan point clouds and photogrammetry are large and updated often. Emailing links to a drive is how versions get mixed up.
Architecture, engineering & construction
Move BIM models, point clouds and drawing sets between firms and sites without the courier.
A federated model, a scan of the existing building and the current drawing set are gigabytes to terabytes, held by different firms on different networks and needed on site with a poor connection. RIPTON CLOUD moves those project folders between the organisations on a job as single packages.
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
Project server or site laptop
02
RIPTON Desktop or browser
03
RIPTON node at the other firm
04
Their project folder
Between firms and sites
Every firm on the job has the model. Nobody has the latest one.
Project data is exchanged between separate companies at every stage, from design coordination to handover, and site connectivity is often the worst link in the chain.
Drawing sets are thousands of files
Issue sets, specifications and photo logs are many files. Tools that handle each one separately spend the day on overhead.
Sites with poor connectivity
Site offices and field laptops are on cellular or shared links where ordinary transfers stall.
Workflows
Where the transfer path matters most.
BIM · CAD · point clouds
Model exchange between firms
Send a model or scan package to named contacts at the other firm. Each gets a scoped link; the download is recorded so the issue is traceable.
Issue sets · specifications · handover
Issue sets to contractors and clients
Send drawing and specification sets as packages with expiry you set. Recipients download from a browser with no account.
Scans · progress photos · reports
Site capture back to the office
Give site teams and surveyors a Shared Inbox so scans, photos and reports come back as folders, not attachments.
RIPTON CLOUD in the workflow
What a project team gets
The product earns its place by moving prepared data between endpoints—not by claiming ownership of every system around it.
Project folders as one package
Any number of files travel and are stored as a single package with the folder structure kept.
Delivery you can point to
A record of who received which issue and when they downloaded it, for the project record.
Works from the site link
The RIPT protocol is built for high-latency, lossy connections, and interrupted packages resume rather than restart.
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
Exchange, not the common data environment.
RIPTON CLOUD moves project files between organisations and records the movement. It does not replace your CDE, model-checking or document control.
What it covers
- Models, scans and issue sets sent as packages
- Recipient links without accounts or seats
- Inbound site data through Shared Inboxes
- Delivery records for the project file
What stays with your stack
- Common data environment or document control
- Model coordination or clash detection
- Continuous folder sync
- Viewer or markup tools
Evaluation path
Test it on the current issue
Bring one real handoff, usually to the firm or site that always waits longest, and measure both tools.
- 01
Choose the handoff
Office to office, office to site or site to office. One route.
- 02
Send the model
The real federated model or scan with each tool, elapsed time and restarts recorded.
- 03
Send the issue set
The full drawing set, so file-count overhead is measured.
- 04
Decide on numbers
Hours from issue to receipt, and courier costs avoided, written down.
FAQ
Questions technical buyers ask.
Does it replace our CDE?
No. It moves files between organisations and sites. Publish to the CDE as you do now; use RIPTON CLOUD where the CDE's own transfer is the bottleneck or where the other party is not on it.
Can contractors and clients receive without accounts?
Yes. Recipients download from a browser with a scoped link. They do not use a named seat and are not charged.
What is the file-size limit?
10 GB per file on Free, 100 GB on Starter, and no file-size limit from Professional up.
Does it work from a site office?
The protocol is designed for high-latency, lossy links and resumes interrupted packages. How much faster it is than your current tool depends on the site connection; the evaluation measures it.
Technical evaluation
Get the model to the people building from it.
Start a free workspace, or bring one handoff between firms and we will help you measure it.