Encrypted discussion
New comment text, review notes, display names, and mention addresses are encrypted on the device with the file key.
A secure client file portal for collection, delivery, and review.
Give a client a focused way to send encrypted files or receive a protected copy without opening your wider workspace. Then keep internal comments and review decisions attached to the file as the work moves forward.
Founding beta: RonikCloud has not been independently audited. Use non-critical copies and keep another backup.
Focused collectionA request page instead of workspace access
Protected deliveryA separate password-encrypted share copy
Deliberate limitsExpiry, request budget, and revocation
Visible review statePending, approved, or changes requested
Collect the source, do the work, deliver the result.
RonikCloud combines focused public transfer pages with a private workspace, so you can choose a narrower access path for the job instead of inviting every client into your files.
Request files
Create a request and privately send its URL to the contributor who needs to upload source material.
Receive encrypted work
The contributor's browser encrypts the request details, submitted filename, content type, and file body.
Review privately
Keep encrypted new comments and review notes with a pending, approved, or changes-requested status.
Deliver deliberately
Send a separate password-protected encrypted copy with a defined expiry and request budget.
Let a client upload through a focused request page.
A file request is designed for one collection task. The request title, submitted filename, content type, and file body are encrypted on the contributor's device before storage.
- Private URL fragmentThe encryption key travels in the private URL fragment, which browsers do not send as part of the HTTP request.
- Claimed as one operationA completed encrypted upload is claimed in the same transaction that decrements the request's remaining allowance.
- Owner-controlled requestThe owner can close a request when collection is finished instead of leaving it available indefinitely.
- Sensitive capabilityAnyone who receives an active request URL may be able to submit, so send it through a trusted channel.
Keep the workspace original separate from the public link.
RonikCloud creates a separate encrypted share copy. The browser derives a proof from the password, the backend checks that proof before encrypted bytes leave storage, and the recipient's browser decrypts the protected file.
- Password boundaryThe shared filename, content type, and file content stay inside the password-protected encrypted copy.
- Defined lifetimeSet an expiry so the link is not intended to remain open forever.
- Request budgetSet a limit on encrypted-payload requests and track its use from the owner view.
- RevocationClose one link or revoke every active link you own. Already-downloaded recipient copies cannot be recalled.
Turn a handoff into a visible internal review state.
After collection or before delivery, your collaborators can keep discussion and the current decision attached to the relevant file instead of reconstructing it across unrelated messages.
Clear review status
Keep work pending, mark it approved, or request changes with a protected review note for internal collaborators.
Honest failure state
If collaboration cannot load, RonikCloud shows it as unavailable with a retry instead of presenting a misleading empty discussion.
Use the specialist business tools you already rely on.
RonikCloud is built around private storage, encrypted collection, protected delivery, file comments, and review status. It does not currently replace invoicing, contracts, scheduling, or a full customer relationship manager.
This is not a white-label portal. Clients see focused RonikCloud file-request or password-share pages, while you retain the private workspace and its broader controls.
Security boundary: The service still processes the identifiers, timestamps, limits, access relationships, review status, routing, and security records needed to run these features. Network activity remains observable to service infrastructure.
For bookkeeping and accounting documents, review the narrower workflow and compliance limits in secure file sharing for accountants.
Fit the client portal into storage that stays understandable.
Explore the workflow from the perspective of encryption, delivery, freelancer operations, or small-team access.
Encrypted file sharing
Read the password proof, separate share-copy, expiry, request-budget, and revocation model in more detail.
For freelancers
Connect collection and delivery with private project storage and a straightforward review workflow.
For small teams
Use roles, deliberate invitations, and member-bound encrypted folders for people inside the workspace.
Secure cloud storage
Understand encryption, user-held recovery, private device state, and the metadata the service still needs.
Secure client file portal FAQ
Does a client need access to my RonikCloud workspace?
No workspace access is needed to use a public file-request page or receive a password-protected share copy. The client uses a focused browser page while the owner keeps control of the workspace. Links and passwords still need to be shared carefully.
Is the RonikCloud client portal white-label?
No. RonikCloud currently provides focused file-request and password-share pages rather than a custom-branded portal, customer relationship manager, or full project-management suite.
What controls are available for a delivered file?
A new protected share can have a password, expiry, and encrypted-payload request budget. Its owner can revoke the link or use an emergency revoke-all action. Revocation cannot recall a copy that a recipient already downloaded.
Does encrypted client exchange hide every activity detail?
No. The service still processes opaque file and account identifiers, timestamps, access relationships, review status, notification routing, request limits, and limited security records. Network infrastructure can observe connection data, timing, and traffic volume.
Collect the source and deliver the result with narrower access.
Join the tester program with a real client-shaped use case, or review the product and current pricing first.
Founding beta: RonikCloud has not been independently audited. Use non-critical copies and keep another backup.