Defined responsibility
Manage current users, roles, workgroups, Shared Inbox relationships, and scoped service access.
Administration and nodes
Operate people, endpoints, transfer paths, and evidence with clarity.
RIPTON CLOUD administration connects identity, endpoint configuration, transfer-node state, policy, activity, and diagnostics. Technical teams can understand the selected path and investigate a transfer without treating the service as a black box.
RIPTON CLOUD / Administration and nodes
01
entry
Users + workgroups
02
control
Policy + configuration
03
transfer
Nodes + paths
04
evidence
History + diagnostics
Why it matters
A product capability tied to an operational outcome.
Inspectable endpoints
See node state, storage roles, Web Edge eligibility, preferred paths, and supported high-availability routing context.
Supportable operations
Follow transfer requests, history, diagnostics, activity, and relevant policy blockers when work needs attention.
How it works
From entry point to evidence.
The workflow stays understandable at every stage, with the control plane coordinating policy and the data plane moving supported workloads.
- STEP 01
Configure identity
Create or manage users, status, roles, workgroups, Shared Inbox membership, and supported API clients.
- STEP 02
Register the nodes
Configure transfer nodes, connectivity, storage context, Web Edge eligibility, and preferred roles.
- STEP 03
Apply service policy
Set the supported transfer, email, branding, retention, webhook, and lifecycle configuration for the deployment.
- STEP 04
Operate the transfer
Inspect selected paths, node and transfer state, activity history, diagnostics, and recovery context.
Capability detail
What your team can inspect and use.
Users and roles
Administer account state and current role relationships across the product's supported identity model.
Nodes and storage context
Configure endpoint roles, connectivity, storage locations, Web Edge eligibility, and preferred selection.
Transfer visibility
Review active and historical transfer requests, progress, path context, warnings, errors, and diagnostic events.
Administrative surfaces
Manage supported API clients, webhooks, activity retention, branding, transfer settings, and notification configuration.
Operational evidence
Customer-managed deployment with supported product updates.
Customers receive a versioned tar package and install RIPTON in infrastructure they manage. The customer controls deployment timing and policy; RIPTON CLOUD supplies maintained application updates.
- User and role state
- Node connectivity and role state
- Transfer and diagnostic timelines
- Administrative activity and retention context
Continue exploring
Related platform and solution pages.
Automation and integrations
Connect approved systems through supported automation surfaces.
Explore →Web Edge
Understand the browser transfer node role.
Explore →MFT Platforms
See the wider modernization use case for an operated transfer service.
Explore →Replace FTP and SFTP
Retire the FTP server without changing how partners work.
Explore →Proof of concept
Two weeks, one or two routes, your current tool as the baseline.
Explore →Changelog
What shipped on the node and control plane, by date.
Explore →Frequently asked questions
Technical questions, answered plainly.
Where does RIPTON CLOUD run?
Customers receive a versioned tar package and install RIPTON in infrastructure they manage. RIPTON CLOUD provides supported application updates.
Can administrators inspect a failed transfer?
Current operator surfaces include transfer state, selected path context, history, warnings, errors, diagnostics, and supported recovery actions according to role.
Does RIPTON replace infrastructure monitoring?
No. RIPTON exposes product and transfer evidence, but customer infrastructure monitoring, SIEM, storage governance, and broader incident operations remain with the customer's stack.
Evaluate the workflow
Review the operating model with the people who will support it.
Bring your deployment boundary, identity model, node topology, storage context, and support requirements. We will map the current administrative surfaces to them.