Point Google Drive, Google Photos, Dropbox, OneDrive, Box or pCloud at a bucket you own. Bring your own keys, keep the data in your account, and let the schedule run without a cron job or a machine you have to maintain.
No credit card. Free plan includes 2 GB of transfer every month.
Drive / Dropbox
S3 · R2 · B2
Your bucket, your keys, your retention policy.
The problems people bring us, and what we do about them.
“My rclone cron works until it silently doesn't.”
Hosted schedules with automatic retries, per-file logs, and alerts to email, Discord or Telegram when a run needs attention — no box of your own to keep alive.
“Consumer cloud storage costs far too much per terabyte.”
Keep working files where they're convenient and mirror the bulk into object storage, where the same terabyte costs a fraction as much.
“I want backups in storage I control, not another SaaS silo.”
You supply the bucket and an access key scoped to it. The data lands in your account under your lifecycle rules — cancel us tomorrow and your backup is still yours.
“Signing S3 requests from a browser tool is asking for trouble.”
Requests are signed server-side with SigV4 and your keys are encrypted at rest with AES-256-GCM. A read-only key limited to one bucket is all we need.
S3, R2 and B2 with your own keys
Any S3-compatible endpoint works. Give us an access key scoped to a single bucket and nothing more.
Server-side copy where the provider allows it
Copies inside the same provider are asked of the provider itself, so bytes don't take a round trip they don't need.
Incremental object sync
Per-file state means repeat runs upload only what changed — important when the source has hundreds of thousands of files.
Nothing is stored on our servers
Files are streamed straight from the source cloud to the destination. Once a transfer finishes, no copy of your data remains with us — we keep only file names and sizes needed to resume the next run.
Public API and API keys
Trigger syncs and read job status from your own scripts if you'd rather drive it from CI than the dashboard.
Zip and Takeout handling
Compress a folder into your bucket, or unpack a Google Takeout archive into it with the album structure intact.
Review the list, then run it for real. Mirror mode never deletes anything you haven't seen first.
Handing a tool access to years of files deserves scrutiny. Here is exactly what happens.
No copies kept
Files stream from source to destination. Nothing remains with us after a transfer — only names, sizes and timestamps so the next run can skip unchanged files.
Tokens encrypted at rest
Cloud credentials are encrypted with AES-256-GCM and never written to logs. Disconnect a cloud, or delete your account and its data, whenever you want.
Least access we can ask for
For Google Drive we use the drive.file scope — we can only touch what you pick or what we create. Your data is never used to train AI models.
Create a bucket and an access key limited to it.
Connect the source cloud and paste the bucket credentials — we test them before saving.
Create a rule with the prefix you want to write under, then preview it.
Schedule it and wire the webhook into wherever you watch alerts.
Amazon S3, Cloudflare R2 and Backblaze B2 are supported directly, and other S3-compatible endpoints generally work with the same credentials plus region and bucket.
No. Use a key scoped to the one bucket you're writing to. Credentials are encrypted with AES-256-GCM before storage.
Yes. Create an API key in settings and call the public v1 API to start syncs and read job status.
No — you pay your storage provider directly. Our plans price the transfer we perform, starting free at 2 GB a month.