A guided path from "where do I put this file?" to proofs that your data is kept: links that keep working because they name the content, sharing and updating, end-to-end encrypted repositories, and checking Zaryn without trusting it. Pictures first, every step explained.
Put a file on Zaryn and get a link anyone can open. How much space you have, what "public" means here, and how to remove a file.
Use Zaryn as S3 storage with aws-cli, rclone, restic and any S3 SDK. Make a key, point the tool at the endpoint, and every object is checked on every read and counted once on your storage plan.
Step-by-step setup of Zaryn storage in rclone, restic, Kopia, Veeam, Synology Hyper Backup and Cloud Sync, aws-cli and any S3 tool. Three settings, copy, paste, done.
Encrypted, deduplicated backups of folders, servers and Postgres databases with one command. To your Zaryn storage, any S3-compatible bucket, or a disk. Only changes are sent, every restore is checked, and a schedule runs it for you.
Freeze a folder of a bucket as a dataset or model version. Exact files by their hashes under one root, kept when the bucket changes, linked to what they were trained on, downloaded in checked pieces that resume where they stopped.
Keep backups that ransomware can't delete, overwrite or encrypt, even with your own keys. Object lock (S3's API), a trash that puts a bucket back as it was, and delays on anything that lowers protection.
Check with cryptographic proofs, instead of taking anyone's word for it, that Zaryn really stores everything you pushed.
Encrypt a private repository's files on your own devices, so Zaryn stores only data it can't read.
