Softwr

File Storage · head to head

Cloudflare R2 vs rustic

Cloudflare R2 logo

Cloudflare R2

File Storage

S3-compatible object storage that charges nothing for egress to the internet

From
Free
Free plan
Yes
rustic logo

rustic

Backup

Rust reimplementation of restic that reads and writes the same repository format

From
Free
Free plan
Yes

The short version

  • rustic is free; Cloudflare R2 starts at $0.015/mo.
  • Only Cloudflare R2 lists zero egress billing; only rustic lists configuration profiles.
  • Where rustic falls short: command names, flags and behaviour do not map one to one onto restic, so scripts and runbooks need rewriting rather than a binary swap.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cloudflare R2 and rustic actually diverge.

Attributes where Cloudflare R2 and rustic differ
AttributeCloudflare R2rustic
Pricing modelPer gigabyte stored per monthOpen source, no licence fee
PlatformsWeb, APILinux, macOS, Windows
CategoryFile StorageBackup

Identical on both: starting price (Free), free tier (Yes).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Cloudflare R2

  • Zero egress billing
  • S3 API compatibility
  • Worker binding
  • Jurisdictional restriction
  • Infrequent Access tier
  • Custom domain serving

Only in rustic

  • restic format compatibility
  • Configuration profiles
  • Deduplicated encrypted backups
  • Cold and append only storage support
  • Multiple back ends
  • Library crates

What people use each for

The jobs each tool is most often brought in to do.

Cloudflare R2

  • Serving a large media or asset library to the public where transfer out, not storage, is the dominant costnot rustic
  • Hosting a container or artefact registry that thousands of CI runners pull from every daynot rustic
  • Distributing model weights or open datasets that are downloaded far more often than they are updatednot rustic
  • Moving off S3 specifically to stop paying data transfer charges on a read heavy bucketnot rustic

rustic

  • An existing restic user who wants configuration files rather than long command lines in cronnot Cloudflare R2
  • Backing up a memory constrained machine where the reference implementation is uncomfortably heavynot Cloudflare R2
  • Writing to append only or cold object storage where the default tooling assumes rewritable bucketsnot Cloudflare R2
  • Keeping a second implementation available so a long lived archive does not depend on one codebasenot Cloudflare R2

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cloudflare R2

  • There is no archive tier below Infrequent Access, so genuinely cold data costs roughly ten to fifteen times what it would cost in a deep archive class and there is nowhere cheaper to lifecycle it to
  • Class A operations are billed at 4.50 USD per million, so a workload that writes millions of small objects can spend more on operations than on the storage those objects occupy
  • Infrequent Access carries both a retrieval fee and a thirty day minimum storage duration, so data that is deleted or re-read sooner ends up more expensive than if it had stayed on Standard
  • You choose a location hint rather than a region, so you cannot prove to an auditor which datacentre holds an object unless you use a jurisdiction restricted bucket, and jurisdictions are limited
  • Support level follows your Cloudflare account plan rather than the storage spend, so a team on a low tier account gets ticket support with no storage specific SLA, and an R2 incident is a Cloudflare incident you cannot fail over from because the free egress only exists inside Cloudflare

rustic

  • The project is small with a short list of active maintainers, so bus factor is a genuine consideration for software whose job is to still work in five years
  • It inherits the restic repository format, so design limits in that format, including the cost of pruning large repositories, are inherited rather than fixed
  • Command names, flags and behaviour do not map one to one onto restic, so scripts and runbooks need rewriting rather than a binary swap
  • Far fewer people have performed a real restore from it under pressure, and backup software is one of the few categories where being second most used is itself a risk
  • Alternating between rustic and restic against one repository works but doubles the surface for a version incompatibility to corrupt state, so most operators should pick one and stay with it

Pricing, plan by plan

Cloudflare R2

Free
  • Free tierFree
    • 10 GB stored per month
    • 1 million Class A operations
    • 10 million Class B operations
  • Standard$0.015/mo
    • Per gigabyte stored per month
    • 4.50 USD per million Class A operations
    • 0.36 USD per million Class B operations
  • Infrequent Access$0.01/mo
    • Per gigabyte stored per month
    • Per gigabyte data retrieval fee
    • Thirty day minimum storage duration

rustic

Free
  • rusticFree
    • Full functionality, no data limit
    • All supported storage back ends
    • Community support via GitHub

Which should you pick?

Choose Cloudflare R2 if

  • You need zero egress billing.
  • You want to start without paying.
  • You work on Web, API.
  • You also want s3 api compatibility.

Choose rustic if

  • You need restic format compatibility.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want configuration profiles.

Questions people ask

Is Cloudflare R2 or rustic better?
Neither clearly leads. Cloudflare R2 starts at Free and rustic at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cloudflare R2 or rustic?
Cloudflare R2 starts at Free and rustic at Free.
Does Cloudflare R2 or rustic run on more platforms?
Cloudflare R2 runs on Web, API. rustic runs on Linux, macOS, Windows.
Can I use Cloudflare R2 for free?
Both have a free tier, so you can try either at no cost before committing.
What is Cloudflare R2 best used for?
Cloudflare R2 is most often used for serving a large media or asset library to the public where transfer out, not storage, is the dominant cost, hosting a container or artefact registry that thousands of ci runners pull from every day, distributing model weights or open datasets that are downloaded far more often than they are updated, moving off s3 specifically to stop paying data transfer charges on a read heavy bucket. Of those, serving a large media or asset library to the public where transfer out, not storage, is the dominant cost and hosting a container or artefact registry that thousands of ci runners pull from every day are not what rustic is typically brought in for.
What can Cloudflare R2 do that rustic cannot?
Cloudflare R2 covers Zero egress billing, S3 API compatibility, Worker binding, Jurisdictional restriction. rustic covers restic format compatibility, Configuration profiles, Deduplicated encrypted backups, Cold and append only storage support.

Answered from the vendors’ own pages

Cloudflare R2: Is egress really free, with no hidden transfer charge?

Yes for data served out of R2 to the internet. You still pay per operation for the requests that serve it, and if you pull data into R2 from another provider you pay that provider the egress on the way in.

rustic: Can it read my existing restic repository?

Yes, that is the point of the project. Take a copy and verify before you rely on it, as with any change to backup tooling.

Cloudflare R2: How does the total cost compare with S3 for a public download bucket?

Storage is more expensive per terabyte than S3 Infrequent Access, but S3 charges roughly 90 USD per terabyte served. Any bucket that serves more than about a fifth of its stored volume each month is cheaper on R2.

rustic: Should I switch from restic?

Only for a specific reason such as configuration profiles, memory use or cold storage handling. Compatibility means there is no cost to trying and no cost to going back.

Cloudflare R2: Can I use R2 without using the rest of Cloudflare?

Yes, it works through the plain S3 API from anywhere. You lose the Worker binding and the free CDN caching in front of it, which is where a lot of the practical benefit sits.

rustic: Is it production ready?

It is used in production by a small community, but it is younger and less exercised than the implementation it is compatible with. Test restores accordingly.

Cloudflare R2: Does R2 have a cold archive class like Glacier?

No. Infrequent Access is the coldest tier, at two thirds of the Standard rate plus retrieval fees.

rustic: Does it support the same back ends?

The common ones, including local, SFTP, S3 compatible storage and rclone. Check the current list before committing to an unusual target.

Share

Related pages

Other head to heads