Introducing STORJ Connect

As mentioned in my “How to Survive - without reducing SNO compensation” thread, there’s one crucial aspect that’s missing. It’s time to introduce a new solution. (I don’t care about the old numbers; that video primarily focuses on the features. Prices will be slightly higher, but they’re still cheaper than AWS, and, of course, completely free of any SNO cuts.) :slight_smile:

What do you think, that is what we need, right?

Post what you want to say in text form. Nobody has time to sit through a video. It’s literally the worst possible way to convey anything.

Lol. You’re one of the most active people on the Storj forum. If there’s one thing you clearly have, it’s time. :smiley:

You probably can’t use the Storj name… but I can’t argue with more S3 competition! Maybe partner with the new-Satellite guy to jumpstart your new company?

I don’t think you’ll have any problems attracting SNOs… especially if they can add your new Satellite in parallel. That way they could grow on your side… while Storj continues through CH11.

Will you be based in the EU, or the US? Either way: go for it!

Haha, I think you misunderstood what this is. :grinning_face_with_smiling_eyes:

First of all, that’s an AI voice, so the pronunciation of Storj is acceptable to me.

Second: whenever you read a post from me, do you immediately ask yourself, “How can I find something to shit on here? Where’s the hook?” :grinning_face_with_smiling_eyes:

I’m not building a new Satellite or a Storj competitor.

This is meant to be a toolbox for Storj and Storj customers — making Storj much easier and more convenient to actually use: Finder integration, file management, CDN/CMS integrations, cloud sync, monitoring, AI workflows, and much more.

The customer can also choose how they want to connect: directly to Storj or via the S3-compatible gateway.

Basically, the idea is to build the kind of user-facing tooling around Storj that I think has been missing for years.

So no new storage company, no competing network, and no new Satellite planned here. :wink:

Quite the opposite: the whole point is to make Storj more useful and accessible to customers.

I have time. I don’t have time to waste. Those are different things.

You had already decided it was a waste of time before the premiere countdown had even finished. :grinning_face_with_smiling_eyes:

That’s not really judging whether something is worth your time — that’s rejecting it based on the format before you even know the content.

Pretty narrow selection criteria.

Correct. But very effective.

Yeah, you probably cannot use the word “Storj” this way, it’s a trademark. I think the borderline acceptable legally way is to use a suffix like “YourProductName for Storj”.

Not bothering with the video either. Videos take disproportionately long to consume compared to the amount of content they usually provide, not worth it.

This! I thought he meant a competitive product to Storj - but if it’s a separate app… then they may just give him permission. Like to call it “Connect for Storj” or something. As long as it’s clear it’s from a 3rd-party (so Storj doesn’t support it)… then it could bring more customers to the network and GfTmbH could make some license fees.

Win Win!

If you can build this app/product - please do it, but you need to rename it, because it’s a third party product, so it shouldn’t sound like made and supported by Storj, it also a trademark, so you cannot use a logo like this.

Or do you mean that Storj could build it?
I think the similar idea was behind the current Storj Console, it has some links for integrations and they were planned to be extended later.

You have to watch the last 2 overlays in the video. STORJ Connect would be my gift to STORJ, provided that you reverse the payment cuts.

Personally I see value in this vision, however the implementation is not so easy.

Some parts require substantial investment (for example CDN), other parts require maintaining many small integration, which also very cost sensitive, and not sure if it can be converted to significant more revenue. Implementing a vision/features which may not increase the revenue is risky. Other approach is finding customers who are willing to pay if one or two new features are implemented, and focus on that.

Still I like to big picture + to provide better statistics and visibility. But let’s assume it’s expensive to implement all of these. What would you implement if you can pick only one of these?

BTW: The video is a little bit repetitive, I would recommend not reading all the numbers at every page, instead show real integration workflows and functions.

I think there may be a misunderstanding about what I am proposing here.

I am not suggesting that Storj should assign a development team and build all of these features itself. I am offering to build the toolbox.

Finder/File Provider integration, file and bucket management, CMS integrations, cloud sync, monitoring, AI-assisted configuration, access management and the other client-side integrations can all be developed and maintained by me.

So for most of this, the implementation cost for Storj would effectively be close to zero. What I would need from Storj is mainly stable APIs/documentation, possibly a few additional API endpoints where data is currently not exposed, coordination regarding branding and integration into the Storj ecosystem — and one important commitment:

If I donate a project of this scope to Storj and spend the time building and maintaining a substantial part of the customer-facing infrastructure around it, I would expect a clear commitment that the proposed SNO payment cuts are withdrawn.

I do not think it would make much sense for me to invest a very substantial amount of unpaid development work into strengthening the Storj ecosystem while, at the same time, the infrastructure providers I am part of are being asked to absorb further compensation cuts.

From my perspective, this could be a fair exchange: I contribute a significant software project that would otherwise require substantial development resources, and Storj commits to preserving the current SNO compensation structure instead of proceeding with the proposed cuts.

The CDN part also needs a distinction. I am not suggesting that Storj immediately builds and operates its own global CDN infrastructure. Storj Connect can initially integrate existing CDN providers and configure Storj as the origin. A native Storj CDN could be a completely separate future project if there were sufficient customer demand.

The same applies to the “many small integrations” problem: if I build and maintain those integrations, Storj does not have to employ people to maintain each of them.

So if the question is what I would build first, I would start with the common foundation: one application that makes Storj usable like a normal cloud storage product — account/access setup, Buckets, Files and native Finder integration. Everything else then becomes a module on top of that foundation.

And yes, I agree with you about the video. The next version should show actual workflows instead of reading statistics: connect an account, mount Storj in Finder, upload a file, connect a WordPress site, configure a CDN, sync another cloud provider, etc. That would demonstrate much better what the product could do.

Could Storj use some of the savings from the recent payout reduction to hire you (or someone else) as a contractor to do the work? It sounds like it would cost them the same… and they’d have control of the upgrades (instead of hoping-for-the-best from donated code)?

You definately deserve compensation. If you don’t want to do it on-contract… even in down markets people will pay for tools - I bet you could license your improved UI

Simply saving money on payouts was a great change: if a slice of those savings can also fund improvements that would be amazing!

Thanks, I really appreciate that :heart: But honestly, I’m trying to save your wallet too.

I’d rather contribute this for the benefit of all SNOs than turn it into my own little business competing for an ever-shrinking slice of the pie.

I still think the payment cuts are a serious mistake. Saving a few thousand now could easily cost Storj far more later if operators stop expanding, reinvesting, sending open letters to customers or simply leave.

How many devs for how many years are you proposing to work on this? And who will do the customer support? Are you offering to do this as well?

And all of this just in exchange for revoking the 18% payment cut? Your investment in storj must be huge to justify this… :thinking:

Yes, my investment in Storj is well into six figures, so 18% absolutely matters to me.

But this also isn’t some multi-year development project. We’re talking more like 1–2 months, and the number of devs needed will become clear as it develops.

As for customer support, I’d actually expect the opposite of extra workload: a better, more intuitive interface should let customers act more confidently on their own and reduce support friction.

And more broadly, I hate to see Storj fall into the worst side of capitalism, where every problem is solved by squeezing the people with the least leverage. Most of us are doing reasonably well here. Storj’s current financial pressure comes from legacy debt and past decisions, not from SNO payouts.

Even if you could manage to show a first version in 1..3 month (I strongly doubt on that) such project is not fire and forget. It needs ongoing work for improving features, bugfixing, adjustment for changes on customer side or storj api.

You are proposing some maybe nice solution in maybe some years in exchange for higher payment now. That is not going to work.

@alpharabbit Doubts resolved :slight_smile: