Softwr

Backup · head to head

Kopia vs Scality RING

Kopia logo

Kopia

Backup

Open source deduplicating backup with client side encryption and a repository on almost any storage

From
Free
Rated
-
Scality RING logo

Scality RING

File Storage

Petabyte-scale object storage software on your own hardware

From
On request
Rated
-

The short version

  • Only Kopia has a free tier, so it costs nothing to try first.
  • Each has a real cost: Kopia space is only reclaimed when maintenance runs, and in a shared repository full maintenance is owned by one client, so if that machine goes away the repository grows for ever while every backup still reports success.; Scality RING hardware is bought separately, so the software quote understates total cost and the buyer carries the sizing risk if the drive and server specification is wrong.
  • They diverge on capability: Kopia covers Content defined chunking, Scality RING covers S3-compatible object storage.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Kopia and Scality RING actually diverge.

Attributes where Kopia and Scality RING differ
AttributeKopiaScality RING
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsLinux, macOS, Windows, DockerLinux
CategoryBackupFile Storage

Identical on both: user rating (Not yet rated).

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 Kopia

  • Content defined chunking
  • Global deduplication
  • Pack blobs
  • Client side encryption
  • Desktop and command line
  • Repository verification

Only in Scality RING

  • S3-compatible object storage
  • File and object access
  • Erasure coding
  • Object lock
  • Multi-site geodistribution
  • Hardware independence
  • ARTESCA

What people use each for

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

Kopia

  • Backing up laptops and workstations to cheap object storage with a desktop interface rather than a cron jobnot Scality RING
  • Deduplicating backups of several similar machines into one repository so common content is stored oncenot Scality RING
  • Replacing a chunk based tool whose per object charges made a cheap bucket expensivenot Scality RING
  • Keeping an encrypted offsite copy where the storage provider must never be able to read the contentsnot Scality RING

Scality RING

  • A broadcaster archiving decades of video where hyperscaler storage and egress costs would be prohibitivenot Kopia
  • A hospital group holding medical imaging on premises for data residency and retention reasonsnot Kopia
  • An enterprise building an immutable on premises backup target for Veeam or Commvault with object locknot Kopia
  • A service provider offering S3-compatible storage to its own customers on hardware it controlsnot Kopia

Where each one falls short

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

Kopia

  • Space is only reclaimed when maintenance runs, and in a shared repository full maintenance is owned by one client, so if that machine goes away the repository grows for ever while every backup still reports success.
  • The repository format has changed across versions and mixing client versions against one repository is discouraged, so a fleet must be upgraded together rather than machine by machine.
  • There is no central orchestration or reporting for many machines, so monitoring a fleet means building your own alerting around exit codes.
  • Restoring many small files is slower than the backup was, because content must be reassembled from pack blobs, and this is rarely tested until the day it matters.
  • Encryption is client side with no escrow, so a lost repository password means the data is unrecoverable and there is no vendor to appeal to.

Scality RING

  • Hardware is bought separately, so the software quote understates total cost and the buyer carries the sizing risk if the drive and server specification is wrong.
  • Running distributed erasure coded storage requires operations skills, and organisations that expected appliance simplicity end up staffing a storage team they had not budgeted.
  • Rebuild times after a drive failure on large capacity disks are measured in hours or days, and capacity planning has to leave headroom for that degraded window.
  • Pricing is per usable terabyte and quoted, so cost comparisons against cloud object storage require modelling your own retrieval patterns rather than reading a rate card.
  • Small deployments carry a minimum viable node count for erasure coding to work sensibly, which makes the entry footprint larger and less economic than the per-terabyte price implies.

Pricing, plan by plan

Kopia

Free
  • KopiaFree
    • Full functionality, no data limit
    • Desktop application included
    • Any supported storage back end

Scality RING

On request
  • Scality RING$undefined/year
    • Priced per usable terabyte, subscription or perpetual
    • Server hardware purchased separately by the customer
    • Support tiers quoted separately
  • Scality ARTESCA$undefined/year
    • Lighter object store for smaller footprints
    • Priced per usable terabyte
    • Commonly deployed as an immutable backup target

Which should you pick?

Choose Kopia if

  • You need content defined chunking.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Docker.
  • You also want global deduplication.

Choose Scality RING if

  • You need s3-compatible object storage.
  • You work on Linux.
  • You also want file and object access.

Questions people ask

Is Kopia or Scality RING better?
Neither clearly leads. Kopia starts at Free and Scality RING at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Kopia or Scality RING?
Kopia has a free tier; the other does not. Paid plans start at Free for Kopia and On request for Scality RING.
Does Kopia or Scality RING run on more platforms?
Kopia runs on Linux, macOS, Windows, Docker. Scality RING runs on Linux.
Can I use Kopia for free?
Yes. Kopia has a free tier, so you can try it without paying. Scality RING starts at On request.
What is Kopia best used for?
Kopia is most often used for backing up laptops and workstations to cheap object storage with a desktop interface rather than a cron job, deduplicating backups of several similar machines into one repository so common content is stored once, replacing a chunk based tool whose per object charges made a cheap bucket expensive, keeping an encrypted offsite copy where the storage provider must never be able to read the contents. Of those, backing up laptops and workstations to cheap object storage with a desktop interface rather than a cron job and deduplicating backups of several similar machines into one repository so common content is stored once are not what Scality RING is typically brought in for.
What can Kopia do that Scality RING cannot?
Kopia covers Content defined chunking, Global deduplication, Pack blobs, Client side encryption. Scality RING covers S3-compatible object storage, File and object access, Erasure coding, Object lock.

Answered from the vendors’ own pages

Kopia: Is a partly corrupt repository still restorable?

Partly. Deduplication means one damaged pack blob affects every snapshot referencing its contents, but unaffected files still restore. Run verification regularly rather than assuming.

Scality RING: Do we buy hardware from Scality?

No. RING is software; you buy commodity servers and drives yourself, which is the point for buyers who want to rebid hardware at each refresh.

Kopia: How does it compare with restic?

Similar guarantees, with packing that behaves better on per operation billing, a desktop interface, and compression enabled by default.

Scality RING: Is it S3-compatible enough for backup software?

Yes, it is a common object lock target for Veeam, Commvault and Rubrik. Verify the specific S3 features your backup product needs during a proof of concept.

Kopia: Do I need to run maintenance manually?

It is scheduled automatically by default, but you must ensure the client that owns full maintenance keeps running, otherwise deleted snapshots never free space.

Scality RING: What is ARTESCA?

A lighter object store from the same company, aimed at smaller footprints and backup targets rather than multi-petabyte archives.

Kopia: Can several machines share one repository?

Yes, and that is where deduplication pays off, but they should run compatible versions and only one owns full maintenance.

Share

Related pages

Other head to heads