If you haven’t already, please read the open letter to the community (An open letter to the Storj token community: the restructuring, the network, and a proposed path to shared ownership) first. That thread is the place for questions about the restructuring, the token, and the shared-ownership proposal — this thread is narrower.
I work at Storj, and I’m asking a practical question on behalf of a decision we may have to make together:
How far could storage node payouts be reduced, before operators are forced to shut down?
I can’t answer that with just one datapoint from my nodes. I need to know your economics — and those vary enormously between a Pi at home on cheap power and a rack in a datacenter. So instead of guessing, I’d like to gather real datapoints.
A number you can share without exposing your setup
The trick is to normalize: your monthly running cost ÷ your current monthly payout = the share of today’s rates at which you break even. Expressed that way, a small and a large operator produce directly comparable numbers, and nothing about your node count, locations, or costs has to leave your hands.
To make that easy I built a small calculator. It runs entirely in your browser — nothing you type is sent anywhere — and it outputs a copy-ready result with only percentages and $/TB, no costs or counts:
Note on the math: I’m treating today’s Reed-Solomon numbers as fixed on purpose — they’re tuned for the balance between durability, storage overhead, and repair traffic that keeps download performance where customers need it, and that balance is worth protecting. Keeping RS constant means the ratio between data at rest and egress/repair traffic stays constant too — so any payout reduction has to apply proportionally to both storage and egress. Cutting egress alone would force the RS numbers to change, spike repair traffic, and degrade the download performance customers rely on. Baseline is today’s $1.50/TB storage, $2.00/TB egress.
The calculator groups the result into four tiers, from deepest cut to shallowest:
- Survival — covers base running costs only; temporary, since nothing is set aside to replace a failed drive.
- Barely sustainable — also covers replacing failed drives, so the fleet doesn’t shrink; but nothing left for growth or your time.
- Slow growth — adds a small budget to expand capacity over time or just a small profit for your own pocket.
- Moderate growth — adds a larger expansion budget.
What I’m asking of you
Run your own numbers and share just the result
How I am going to read your numbers is as follows:
- The cut you can tolerate indefinitely would be somewhere between slow and moderate growth.
- The deeper cut you could tolerate temporarily would be somewhere between survival and barely sustainable. Feel free to add for how many months you would be able to tolerate it.
- Optional context you might want to add
Higher-cost setups matter as much as cheap ones — more, honestly. The goal is honest data to inform a hard decision, not a race to the bottom.
I’ll post my own numbers as one datapoint in a reply below — with the operator hat firmly on, not as any kind of official position.