Softwr

File Storage · head to head

Nasuni vs Storj

Nasuni logo

Nasuni

File Storage

Cloud file storage that keeps the authoritative copy in object storage and caches it at each site

From
On request
Rated
-
Full reviewWebsite
Storj logo

Storj

File Storage

S3-compatible object storage distributed in encrypted pieces across independently operated nodes

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Storj has a free tier, so it costs nothing to try first.
  • Each has a real cost: Nasuni subscription is based on managed capacity, so cold data that would cost almost nothing in an archive tier keeps paying the full platform rate, and there is limited incentive structure to delete.; Storj billing includes a per segment charge and every object consumes at least one segment, so a bucket holding millions of small files can cost several times what the four dollar per terabyte headline implies.
  • They diverge on capability: Nasuni covers Edge caching appliances, Storj covers Erasure coded distribution.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Nasuni and Storj actually diverge.

Attributes where Nasuni and Storj differ
AttributeNasuniStorj
Starting priceOn requestFree
Pricing modelquotePer terabyte per month
Free tierNoYes
PlatformsWeb, Windows, VMware, Hyper-V, AWS, AzureWeb, API, Linux, macOS, Windows

Identical on both: user rating (Not yet rated), category (File Storage).

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 Nasuni

  • Edge caching appliances
  • Object storage back end
  • Continuous versioning
  • Global file lock
  • Rapid site recovery
  • Ransomware detection

Only in Storj

  • Erasure coded distribution
  • Client side encryption
  • S3-compatible gateway
  • Native uplink access
  • Object Lock and versioning
  • Storj Select

What people use each for

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

Nasuni

  • Consolidating file servers across many branch offices onto one namespace without shipping data between sitesnot Storj
  • Replacing a NAS plus backup plus offsite replication stack with a single recovery modelnot Storj
  • Engineering or media teams in different regions who need to work on the same large project filesnot Storj
  • An organisation that has been hit by ransomware on file shares and needs version level rollback rather than tape restoresnot Storj

Storj

  • An offsite backup or archive target where the data is large, written once and occasionally restorednot Nasuni
  • Serving large media files internationally without paying hyperscaler egress ratesnot Nasuni
  • Storing data where the objection to AWS, Azure or Google is jurisdiction and concentration rather than costnot Nasuni
  • A second, independent copy of a dataset that already lives in a hyperscaler bucketnot Nasuni

Where each one falls short

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

Nasuni

  • Subscription is based on managed capacity, so cold data that would cost almost nothing in an archive tier keeps paying the full platform rate, and there is limited incentive structure to delete.
  • Every site needs an appliance, virtual or physical, which is a footprint and a patching obligation at locations that previously had only a file server or nothing.
  • A read that misses the local cache is fetched from object storage, so the first access to a cold large file is at cloud latency and users experience it as the system being slow at random.
  • Global file lock serialises access across regions, so genuinely collaborative editing of the same large files still involves waiting for another site to release the lock rather than merging.
  • The object storage underneath is your contract, so API transaction and egress charges from Azure or AWS land on your cloud bill and are not covered by the Nasuni subscription you were quoted against.

Storj

  • Billing includes a per segment charge and every object consumes at least one segment, so a bucket holding millions of small files can cost several times what the four dollar per terabyte headline implies.
  • Reconstructing an object requires responses from dozens of independent nodes, so time to first byte is noticeably higher than a centralised bucket and it is a poor fit behind a latency sensitive read path.
  • Performance depends on the mix of node operators serving you at that moment rather than on a datacentre you can raise a ticket against, so slow reads are diagnosed statistically rather than fixed.
  • The hosted S3 gateway terminates encryption on Storj infrastructure, so using the convenient access path gives up the end to end encryption that is the main architectural argument for the service.
  • The S3 gateway is compatible rather than identical, so tools that lean on less common API calls, multipart edge cases or unusual header behaviour need testing before you commit a workload to it.

Pricing, plan by plan

Nasuni

On request
  • Nasuni File Data Platform$undefined/year
    • Subscription based on managed capacity
    • Edge appliances at each site
    • Continuous versioning and rapid recovery

Storj

Free
  • Free trialFree
    • 25 GB stored
    • 25 GB egress per month
    • No card required to start
  • Storj$4/month
    • 4 USD per terabyte stored per month
    • 7 USD per terabyte of egress
    • Per segment fee on top of stored volume

Which should you pick?

Choose Nasuni if

  • You need edge caching appliances.
  • You work on Web, Windows, VMware, Hyper-V, AWS, Azure.
  • You also want object storage back end.
Nasuni review

Choose Storj if

  • You need erasure coded distribution.
  • You want to start without paying.
  • You work on Web, API, Linux, macOS, Windows.
  • You also want client side encryption.
Storj review

Questions people ask

Is Nasuni or Storj better?
Neither clearly leads. Nasuni starts at On request and Storj at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Nasuni or Storj?
Storj has a free tier; the other does not. Paid plans start at On request for Nasuni and Free for Storj.
Does Nasuni or Storj run on more platforms?
Nasuni runs on Web, Windows, VMware, Hyper-V, AWS, Azure. Storj runs on Web, API, Linux, macOS, Windows.
Can I use Storj for free?
Yes. Storj has a free tier, so you can try it without paying. Nasuni starts at On request.
What is Nasuni best used for?
Nasuni is most often used for consolidating file servers across many branch offices onto one namespace without shipping data between sites, replacing a nas plus backup plus offsite replication stack with a single recovery model, engineering or media teams in different regions who need to work on the same large project files, an organisation that has been hit by ransomware on file shares and needs version level rollback rather than tape restores. Of those, consolidating file servers across many branch offices onto one namespace without shipping data between sites and replacing a nas plus backup plus offsite replication stack with a single recovery model are not what Storj is typically brought in for.
What can Nasuni do that Storj cannot?
Nasuni covers Edge caching appliances, Object storage back end, Continuous versioning, Global file lock. Storj covers Erasure coded distribution, Client side encryption, S3-compatible gateway, Native uplink access.

Answered from the vendors’ own pages

Nasuni: Do I still need a backup product?

That is the pitch: continuous versioning in object storage replaces the backup schedule for file data. Databases and virtual machines still need their own tooling.

Storj: Why is my bill higher than four dollars per terabyte?

Almost always the per segment fee. Objects are split into segments and small files each consume one, so a few million tiny objects generate a segment charge that dwarfs the storage line.

Nasuni: Who owns the storage account?

You do. Nasuni writes into object storage you contract for, which also means the cloud provider bills you directly for it.

Storj: Can node operators read my data?

No. Files are encrypted client side and each operator holds only an erasure coded fragment, which is not a readable portion of the file.

Nasuni: How fast is recovery of a whole site?

An appliance can be serving files within hours because data is pulled on demand, but performance stays degraded while the cache refills.

Storj: Is there a minimum retention period?

No. You are billed for what you store while you store it, unlike several competitors that bill a ninety day minimum whatever you delete.

Nasuni: Is pricing published?

No. Nasuni sells through quotes based on managed capacity and site count, so comparisons need a real proposal rather than a list price.

Storj: Is it fast enough to serve a website from?

For large files with parallel reads, yes. For many small objects where time to first byte matters, put a CDN in front of it or use something centralised.

Share

Related pages

More on Nasuni

More on Storj

Keep looking

Other head to heads