Getting started

Start with your organization's RIPTON workspace URL and an account with permission to send packages. Obtain the URL and sign-in instructions from your administrator or RIPTON onboarding contact. The marketing website and billing customer portal are not your transfer workspace.

• Your organization's HTTPS workspace URL, written as <your-workspace-url> in this guide; replace the placeholder with the address you were given.
• An activated account or invitation, a small non-sensitive test file, and a recipient whose access you can verify.
• RIPTON Desktop installed and running for the Desktop transfer path. Your administrator must have configured reachable transfer storage. Browser transfers require an eligible Web Edge node and enabled policy.

1. 1Open <your-workspace-url> in your browser and follow your organization's sign-in or invitation instructions. Do not substitute localhost or the public marketing website.
2. 2Open RIPTON Desktop on the same workstation if you are using the Desktop path. Return to the browser workspace and open Send to reach Send a package.
3. 3Check that the page detects Desktop before choosing files. Follow any connection or update prompt shown by your installed release. If Desktop is not detected, see the troubleshooting section below; do not assume the transfer will automatically use Web Edge.

1. 1In Recipients, enter your test recipient's email and press Enter to add it. Confirm that the recipient is correct before sending.
2. 2Enter a Title, such as First transfer test. Add an optional Note explaining that this is a test.
3. 3Select Add files and choose your small test file. On the Desktop path, RIPTON Desktop opens the native file picker. Confirm the selected file name and size before continuing.
4. 4Review More options and complete any required metadata. For this first test, avoid scheduling a future release and ensure any expiration allows enough time for the recipient to download. Follow your organization's delivery policy.
5. 5Select Notify recipients when delivered if email notification is needed and configured for your workspace, then select Send package once.

1. 1Open Sent and select the package you just created. Review its file list, status, and activity while the transfer runs.
2. 2Wait for the upload to finish. If it fails or remains in progress, record the displayed error and package ID before retrying; do not create repeated packages to hide an unresolved failure.
3. 3Confirm that the intended files are present and available before asking the recipient to download. A completed upload does not prove that the recipient has downloaded or reviewed the files.

1. 1Ask the test recipient to open their package notification or the package available to their account. They must follow the access and authentication requirements configured for that delivery; do not share the sender's credentials.
2. 2Open the package and use its download action. Follow the displayed Desktop or browser instructions available for that package, and choose a local destination when prompted.
3. 3Wait for the recipient download to finish, then open the downloaded test file and compare its name and size with the original. For an integrity check, compare SHA-256 hashes of the original and downloaded file on their respective machines.

# Run separately on the original and downloaded file.
# macOS
shasum -a 256 '/path/to/test-file'

# Linux
sha256sum '/path/to/test-file'

# Windows PowerShell
Get-FileHash -Algorithm SHA256 -LiteralPath 'C:\path\to\test-file'

Your first-transfer check passes when the upload completes, the intended recipient can download the package, and the downloaded file matches the original. Retain the package ID and any test results before moving to a larger workload.

A RIPTON deployment needs PostgreSQL, the control service, at least one transfer node, the web UI, and RIPTON Desktop on user workstations. Use a single Linux host only for a pilot or evaluation.

• Ubuntu 22.04 or 24.04 with root or sudo access
• PostgreSQL reachable from ript-control
• TCP 8080 for control and TCP 9092 for the node API
• UDP 33001-33008 between Desktop clients and the transfer node
• The release archive unpacked on the Linux host

tar -xzf ripton-release-VERSION-linux-amd64.tar.gz
cd ripton-release-VERSION
sudo scripts/install-single-machine.sh

1. 1Open the UI and create the first administrator account.
2. 2Open Admin, then Nodes, and register the local rnode.
3. 3Run Check connectivity and assign the node as Default storage.
4. 4Install RIPTON Desktop on a workstation that can reach the node transfer ports.
5. 5Send a small non-sensitive file and download it as the recipient.

curl -fsS http://localhost:8080/healthz
curl -fsS http://localhost:8080/readyz
curl -fsS -u '<user>:<password>' http://localhost:9092/api/v1/ping
sudo scripts/ript-smoke-check.sh

The install is ready for evaluation when control is ready, node connectivity passes, Desktop can upload a test package, the package reaches a completed state, and the downloaded SHA-256 checksum matches the original.

Repeat the test with a representative workload before increasing scale. Explore Shared Inboxes for repeat inbound deliveries and public links only where your organization's policy permits them. Administrators can continue with Choose a deployment path, Register and troubleshoot a node, and Operations and troubleshooting in this documentation. Introduce automation after the manual transfer and recipient-access checks work reliably.