I don’t mean that nobody had ever heard of Storj. The company spent years attending exhibitions, conferences and industry events, presenting decentralized storage and talking about the technology.
The more interesting question is:
What exactly were they showing potential customers at those exhibitions?
How to generate an access key?
How to configure S3 credentials?
How to install another tool, read documentation, change existing workflows and then explain to employees why they need to do any of this?
For a business, moving away from Google Drive, Dropbox, OneDrive, a NAS or a conventional S3 provider has a real cost. It means changing processes, training people, spending engineering time and accepting additional operational risk.
So a perfectly rational customer looks at Storj and asks:
“What exactly am I getting in return for all this effort?”
And if the answer is simply somewhat cheaper storage, that is often nowhere near enough.
That, in my view, has always been one of Storj’s biggest failures. They tried to sell the technology instead of delivering a finished product.
Customers do not care how elegantly their files are split into pieces and distributed around the planet.
They want to click a button, mount a drive, move their data and forget about it.
Storj’s answer for years often felt more like:
“Here is an API, some documentation and an access key. Good luck.”
And now, if the business really is struggling, perhaps it is time to stop looking for savings primarily from node operators — the people who supplied the disks, bandwidth and electricity that made the network possible.
Maybe management should take a serious look at its own cost structure for a change.
Because from the outside, it certainly looks like developers and management have been living quite comfortably for years while building a product that still requires far too much effort from an ordinary customer.
If the economics no longer work, the first people expected to tighten their belts should be the people who spent eight years running the business — not the people whose hardware kept the network alive.