One package workflow
Prepare recipients, files, metadata, notes, and supported delivery controls without stitching together separate upload and tracking screens.
Browser workspace
The browser workspace is RIPTON CLOUD's control plane. It gives senders and operators a clear place to assemble a package, choose recipients, apply supported lifecycle controls, and understand what happened without moving local file paths through the page.
entry
Files + recipients
control
Package policy
transfer
Desktop or Web Edge
evidence
Status + activity
Why it matters
Prepare recipients, files, metadata, notes, and supported delivery controls without stitching together separate upload and tracking screens.
Authorization and package policy remain in the browser control plane while Desktop, Web Edge, nodes, and relays handle package bytes.
Follow package, recipient, transfer, and completion state from the same workspace used to begin the handoff.
How it works
The workflow stays understandable at every stage, with the control plane coordinating policy and the data plane moving supported workloads.
Select files through RIPTON Desktop or an eligible Web Edge path while keeping local paths out of the browser page.
Add recipients, a title, metadata, notes, and supported release, expiration, passcode, and download controls.
RIPTON applies package and recipient policy before issuing the transfer setup for an eligible endpoint.
Review progress, recipient access, completion, forwarding where allowed, and package activity.
Capability detail
Organize file movement around a named package and the people or destinations that should receive it.
Apply supported metadata, release timing, expiration, passcodes, download limits, archiving, and retention settings.
Keep user, operator, and administrator responsibilities separated through the product's current role model.
Carry the workflow through notification, secure access, download, forwarding where permitted, and completed delivery state.
Operational evidence
Separating control from data movement keeps package policy, authorization, and status understandable while the eligible transfer path handles the workload.
Continue exploring
Use the native transfer path for demanding local workloads.
Explore →Offer scoped upload or download access outside the signed-in workspace.
Explore →Apply the workspace to an external handoff.
Explore →The sender's view: recipients who need no account, folders as one package.
Explore →Step-by-step guide to a Web Edge upload, with the checks that it worked.
Explore →The practical guide, tool by tool, with current size limits.
Explore →Frequently asked questions
For the Desktop path, local selection and movement are handled by RIPTON Desktop; the browser coordinates the package and receives status without needing the local paths.
The receiver experience can include forwarding when the package and delivery policy allow it.
Yes. Current product surfaces expose package status, selected path, transfer state, activity history, and operational diagnostics according to role.
Evaluate the workflow
Bring one sender, recipient pattern, package policy, and transfer route. We will show how the browser workspace coordinates the handoff from preparation through completion.