Ripplic watches a folder on your Mac and replicates every change,
one-way, to the destinations you choose: Amazon S3, Cloudflare R2,
Google Cloud Storage, Backblaze B2, MinIO, and any S3-compatible storage.
Your source is the single source of truth. Changes flow outward — never back. No merge conflicts, no sync surprises, no accidental overwrites at home.
Folders are watched with file-system events. New files ripple out within moments — not on a nightly schedule.
One source, multiple destinations. Mirror the same folder to Amazon S3, Cloudflare R2, and a self-hosted MinIO at once — every copy kept current independently.
Sources won't stay local. Google Drive, Dropbox and OneDrive as sources — replicating Drive to S3, or Dropbox to R2 — are planned for a future release, not in the first version.
Transfers go directly from your Mac to your storage — no middleman servers. Access keys live in the macOS Keychain. No account, no analytics.
Incremental by default: only changes are transferred, interrupted syncs pick up where they left off, and nothing at the destination is deleted without your say-so.
Three ways people put one-way replication to work.
Point Ripplic at your working drive — even an external SSD — and every RAW file and cut ripples to Amazon S3 and Backblaze B2 the moment it lands. The off-site copies of your 3-2-1 backup happen on their own, so a failed drive is an inconvenience, not a career event.
Mirror the same folder to Amazon S3, Cloudflare R2, and the MinIO box in your closet — at the same time, kept current independently. No native cloud tool replicates across vendors; Ripplic does it from one window. Any provider can raise prices or vanish, and your data doesn't care.
Watch your output folder — site builds, game assets, client deliverables — and every save lands on the bucket behind your CDN within moments. One-way means publishing stays unambiguous: your Mac is the source of truth, and nothing upstream ever overwrites your originals.
One window manages every pipeline, and setting up a new one takes a single form.
Define a pipeline once. Ripplic keeps every destination current from then on.
A folder on your Mac or an external drive. Cloud sources like Google Drive and Dropbox are coming in a later release.
Amazon S3, Cloudflare R2, Google Cloud Storage, Backblaze B2, MinIO — one or several.
Every change at the source replicates outward automatically. You just keep working.
No — and that's the point. Ripplic is strictly one-way: the source is authoritative, and changes replicate outward to destinations. That means no merge conflicts, no "which copy wins?" ambiguity, and no risk of a destination overwriting your originals. If you need two directions, you can define two opposite pipelines between different folders.
Any S3-compatible object storage — Amazon S3, Cloudflare R2, Google Cloud Storage, MinIO, Backblaze B2, and others that speak the same API. Google Drive destinations are included in 1.0; Dropbox and OneDrive are coming soon.
Not yet. The first release syncs from a folder on your Mac. Cloud sources — following Google Drive, Dropbox and OneDrive change feeds to enable cloud-to-cloud replication such as Drive → S3 — are planned for a later release.
Never. There are no Ripplic servers. Transfers go directly from your Mac to your storage providers, using credentials that stay in your macOS Keychain.
Not without your explicit say-so. When files disappear from the source, the destination copies are flagged — you decide whether to keep or remove them.
It's out — Ripplic is on the Mac App Store for a one-time $49.99. No subscription.