RevaultUse the web app to upload individual encrypted file backups directly from your browser to an S3-compatible bucket you control.
Download RevaultSecurity modelIf you already manage object storage, Revault’s web app can send encrypted backups directly to your chosen HTTPS S3-compatible endpoint. This is a separate browser feature: native mobile sync uses private iCloud, private Google Drive or Pro Revault Cloud.
Configure the bucket and HTTPS endpoint from the web vault’s Storage settings. Selected device files are encrypted locally before a direct browser upload. You manage the provider, its credentials, access rules and storage costs.
Each uploaded file becomes a separate .qvault object containing an authenticated encrypted inventory and wrapped vault keys. Random object names avoid exposing the original filename. This is an explicit backup upload, not automatic native cloud sync.
Download the encrypted object from your provider and use the vault’s recovery key to restore it. Keep that key separately from bucket access. Revault cannot recover a lost key or manage the lifecycle of objects in your own storage account.
This feature belongs to the separate browser vault experience. It sends encrypted per-file backup objects to an HTTPS S3-compatible endpoint you configure. Native iOS and Android vault sync uses platform clouds or Revault Cloud instead. Choose this route when managing your own bucket is an intentional responsibility, not when you want a ready-made mobile synchronization provider.
The browser needs permission to make requests to the selected endpoint, so both bucket credentials and CORS rules matter. Limit credentials to the intended backup bucket or prefix, keep the bucket private and allow only the site origins and operations your workflow needs. A successful provider login alone does not mean a cross-origin browser upload will be accepted. The provider controls its own costs, object retention and access logs.
Each upload is an independently downloadable .qvault object with an encrypted inventory and wrapped keys. Random object names do not expose the original filename, but the provider still observes object size and request activity. Download a completed object, restore it with the matching recovery phrase and verify the content before trusting the bucket as a backup destination. Bucket access by itself is not the vault decryption secret.
The bring-your-own S3 upload described here is a browser backup feature. The native apps offer their platform’s private storage and Pro Revault Cloud. A per-file S3 object upload is not an ongoing device-sync connection.
Browsers enforce cross-origin access rules. Check the endpoint, region and signing configuration, scoped credentials and the provider’s CORS response. Avoid solving a CORS problem by making encrypted backup objects publicly readable.
No. Existing objects are separate packages with their own saved key wrappers. Keep the recovery secret that matches each retained backup or replace and verify the backups after a recovery change.
Choose the settings that fit your files, and keep a recovery plan before you rely on a single device.
Download RevaultChoose private iCloud or Google Drive sync, or Pro Revault Cloud for iPhone and Android together. Keep other vaults entirely local.
Export a portable encrypted .qvault backup and keep its recovery key separately. Restore your files without a Revault account.
Move a vault to another phone with an encrypted transfer file and a separate transfer key, including when switching between iOS and Android.