Protected on the device
File content, file names, and new folder labels are encrypted before storage. Optional image previews are also produced on the device within bounded limits.
Private cloud backup for working folders, with clear recovery limits.
Choose the folders that matter to your work. RonikCloud protects file content, file names, and new folder labels on your device before storage, then uses privacy-preserving comparisons to find work that needs uploading again.
Founding beta: RonikCloud has not been independently audited. Use non-critical copies and keep another backup.
Encrypt before storageProtection begins on your device
Private comparisonsRaw fingerprints stay in local encrypted state
Opaque object pathsNo readable filename in new storage keys
User-held recoveryExport an encrypted recovery kit
From a local working folder to protected cloud storage.
RonikCloud keeps encryption in the normal backup path, so privacy does not depend on remembering to move sensitive work into a separate vault first.
Choose a folder
Select a local folder, give its cloud destination a name, and decide whether its configured backup is enabled.
Compare privately
RonikCloud keeps raw file fingerprints locally and uses an account-keyed integrity tag for remote comparisons.
Encrypt locally
Changed file content and protected labels are encrypted on the device before the upload is committed.
Continue safely
A private transfer journal supports bounded retry and resume behavior when an encrypted upload is interrupted.
Protect the folders behind everyday client work.
Freelancers and small teams often keep active deliverables, source material, and administration in ordinary folders. A selected-folder workflow makes it easier to protect that work without redesigning how every project is organized.
- Active project foldersKeep changed files moving into encrypted storage while you continue using your usual local organization.
- Client deliverablesBack up the working copy, then use a separate password-protected encrypted share when a deliverable is ready.
- Private local stateSelected paths, raw comparison fingerprints, and transfer checkpoints stay in an authenticated, account-scoped encrypted cache.
- Bounded diagnosticsBackup diagnostics use fixed events, fixed error categories, and temporary opaque references instead of filenames or absolute paths.
Private content with explicit operational boundaries.
Client-side encryption protects the substance of your files and private labels. Running a cloud service still requires a limited amount of operational information.
Limited service metadata
The service still processes object sizes, upload times, opaque references, access relationships, keyed backup tags, storage routing, and account state.
Observable network activity
Infrastructure providers can still observe connection data, timing, traffic volume, and ordinary service logs. Client-side encryption does not hide every event.
Keep the keys and the second copy you may need later.
Account Security can export the standard encryption key in a recovery kit protected by a separate passphrase. RonikCloud does not upload that kit or passphrase, so store them safely and apart.
Trash and rewind tools can help restore supported workspace records, but encrypted cloud storage is not a substitute for an independent backup of irreplaceable data.
Current availability: Folder watching and background behavior depend on the build, device permissions, operating-system policy, and connectivity. A browser cannot keep watching a local folder after it closes.
Back up, deliver, and collaborate with narrower access.
Explore the parts of RonikCloud that fit the way you store files and exchange them with clients or teammates.
Understand secure storage
See how encryption, recovery, device state, and metadata boundaries work across the wider workspace.
Deliver encrypted files
Create a separate password-protected copy with expiry, a request budget, and revocation controls.
Build a freelancer workflow
Connect private storage with client collection, delivery, comments, and review decisions.
Protect small-team work
Use encrypted shared folders, member-bound keys, roles, and deliberate invitations.
Private cloud backup FAQ
What makes a RonikCloud folder backup private?
RonikCloud encrypts protected file content, file names, and new folder labels on the device before storage. Selected backup paths and raw comparison fingerprints stay in an authenticated encrypted device cache, while remote comparisons use an account-keyed integrity tag. Operational metadata and network observations are not hidden from all service infrastructure.
Can RonikCloud keep a selected folder up to date automatically?
Supported native builds can watch selected folders while RonikCloud is running, and supported release builds can continue through an enabled background worker. Scheduling depends on the build, device permissions, operating-system policy, and connectivity. A web browser cannot monitor a closed local folder.
Does RonikCloud replace an independent backup?
No. RonikCloud provides protected cloud storage, recovery tools for supported workspace records, and a user-held encryption recovery kit, but irreplaceable data should also have an independent backup stored separately.
Give your working files a private cloud destination.
Join the tester program and exercise a real backup workflow, or review the product and current pricing first.
Founding beta: RonikCloud has not been independently audited. Use non-critical copies and keep another backup.