Should SodiumSuite Be Open Source
-
The idea behind SS, and I'll fork this thread in a few minutes, is completely to be ground breaking and disruptive. If (when) it gets the full steam ahead nod the only reason that it is being done at all is to do stuff that no one else is doing. It's not meant to improve on an existing model or product category. RMM is the easiest category to point to as being similar, so the comparison is easy to make. And I'll not argue that SS should eventually cover all RMM functionality, but intends to do so in a totally different way than, AFAIK, any RMM maker does it or plans to do it.
If we were making a competitor to any existing RMM, I'd 100% agree that open source is the way to do that. I'd also say that there is likely no real market for it and the project should not get the green light.
-
@stacksofplates said in Looking for free RMM kind, or at least with H/W and S/W inventory software with agent.:
KACE does exactly what SS does.
It's been a long time since I used KACE first hand. But looking at their site, either they are totally misrepresenting what they make (in a way that wouldn't make sense by underplaying what they can do) or I think the idea and goals of SS have been missed.
Most of the details of SS game plan were only divulged off camera at MangoCon 2. What makes it special has never been talked about publicly. Not that it's a huge secret, but it's not at a stage where we talk about it on ML because firms with deep pockets could use the design ideas to get market.
But from looking at KACE, they don't promote their product as being very similar to SS other than they overlap in "doing IT tasks" in the general sense.
-
@scottalanmiller said in Looking for free RMM kind, or at least with H/W and S/W inventory software with agent.:
@stacksofplates said in Looking for free RMM kind, or at least with H/W and S/W inventory software with agent.:
KACE does exactly what SS does.
It's been a long time since I used KACE first hand. But looking at their site, either they are totally misrepresenting what they make (in a way that wouldn't make sense by underplaying what they can do) or I think the idea and goals of SS have been missed.
Most of the details of SS game plan were only divulged off camera at MangoCon 2. What makes it special has never been talked about publicly. Not that it's a huge secret, but it's not at a stage where we talk about it on ML because firms with deep pockets could use the design ideas to get market.
But from looking at KACE, they don't promote their product as being very similar to SS other than they overlap in "doing IT tasks" in the general sense.
Well having used both, the initial SS and KACE they were very similar.
-
@stacksofplates said in Looking for free RMM kind, or at least with H/W and S/W inventory software with agent.:
Well having used both, the initial SS
Well, that was a tech preview without any of the cool functionality in it yet. So I can totally see why it would give that impression. That was a framework being set up with some hopefully usable components to use for testing and demonstration.
-
@scottalanmiller said in Should SodiumSuite Be Open Source:
It's been kicked around but adds a ton of complication to any monetization strategy.
You can't monetize something that doesn't exist!
Also, I thought the plans were to provide a SaaS? You don't need to sell the software if you monetize the service. What's the monetization strategy?
-
@Obsolesce said in Should SodiumSuite Be Open Source:
@scottalanmiller said in Should SodiumSuite Be Open Source:
It's been kicked around but adds a ton of complication to any monetization strategy.
You can't monetize something that doesn't exist!
Also, I thought the plans were to provide a SaaS? You don't need to sell the software if you monetize the service. What's the monetization strategy?
Yes this is how many open source projects are monetizing. They just offer a SaaS version of their product
-
@Obsolesce said in Should SodiumSuite Be Open Source:
@scottalanmiller said in Should SodiumSuite Be Open Source:
It's been kicked around but adds a ton of complication to any monetization strategy.
You can't monetize something that doesn't exist!
That is true as well. Open Source will dramatically reduce your development costs as you have interested parties actually contributing to project
-
@IRJ said in Should SodiumSuite Be Open Source:
@Obsolesce said in Should SodiumSuite Be Open Source:
@scottalanmiller said in Should SodiumSuite Be Open Source:
It's been kicked around but adds a ton of complication to any monetization strategy.
You can't monetize something that doesn't exist!
Also, I thought the plans were to provide a SaaS? You don't need to sell the software if you monetize the service. What's the monetization strategy?
Yes this is how many open source projects are monetizing. They just offer a SaaS version of their product
Yeah look at things like OpenShift or Terraform Cloud. Especially Terraform Cloud, there isn't really a competitor for Terraform and the same with any of Hashicorp's tools.
-
@IRJ said in Should SodiumSuite Be Open Source:
@Obsolesce said in Should SodiumSuite Be Open Source:
@scottalanmiller said in Should SodiumSuite Be Open Source:
It's been kicked around but adds a ton of complication to any monetization strategy.
You can't monetize something that doesn't exist!
That is true as well. Open Source will dramatically reduce your development costs as you have interested parties actually contributing to project
You could also do the open core model, which a lot of FOSS software does. Have the core functionality, maybe RMM specific stuff, be open source but all the "game changing" things be behind a pay wall.
-
@coliver said in Should SodiumSuite Be Open Source:
@IRJ said in Should SodiumSuite Be Open Source:
@Obsolesce said in Should SodiumSuite Be Open Source:
@scottalanmiller said in Should SodiumSuite Be Open Source:
It's been kicked around but adds a ton of complication to any monetization strategy.
You can't monetize something that doesn't exist!
That is true as well. Open Source will dramatically reduce your development costs as you have interested parties actually contributing to project
You could also do the open core model, which a lot of FOSS software does. Have the core functionality, maybe RMM specific stuff, be open source but all the "game changing" things be behind a pay wall.
Wazuh Cloud is a cool offering. It gives you a 30 day trial on their cloud so you get used to it.
-
@Obsolesce said in Should SodiumSuite Be Open Source:
You can't monetize something that doesn't exist!
Obviously a pretty valid point.
-
@Obsolesce said in Should SodiumSuite Be Open Source:
Also, I thought the plans were to provide a SaaS? You don't need to sell the software if you monetize the service. What's the monetization strategy?
SaaS monetization is the strategy. No need to sell software, hence my point in not making any "software" at all. It's purely a service.
-
@IRJ said in Should SodiumSuite Be Open Source:
@Obsolesce said in Should SodiumSuite Be Open Source:
@scottalanmiller said in Should SodiumSuite Be Open Source:
It's been kicked around but adds a ton of complication to any monetization strategy.
You can't monetize something that doesn't exist!
That is true as well. Open Source will dramatically reduce your development costs as you have interested parties actually contributing to project
Open source will potentially do that, it could also make it higher. It's not as clear cut as that. The first struggle would be attracting open source developers interesting in contributing who produce more than they cost in additional communications and direction needed.
If there were an existing body of open source people clamouring to do this who wanted to get involved, we'd be having a very different discussion. But the assumption is that the interest, at least up front, is extremely small and would undermine the existing interest without generating anything new.
-
@coliver said in Should SodiumSuite Be Open Source:
@IRJ said in Should SodiumSuite Be Open Source:
@Obsolesce said in Should SodiumSuite Be Open Source:
@scottalanmiller said in Should SodiumSuite Be Open Source:
It's been kicked around but adds a ton of complication to any monetization strategy.
You can't monetize something that doesn't exist!
That is true as well. Open Source will dramatically reduce your development costs as you have interested parties actually contributing to project
You could also do the open core model, which a lot of FOSS software does. Have the core functionality, maybe RMM specific stuff, be open source but all the "game changing" things be behind a pay wall.
If we can identify, and separate, those functionalities, this has the best potential to work. There are certainly "boilerplate" components that we need, but aren't game changing in any way. It still carries risk that opening it could garner no additional assistance while making internal development slower, though. But it has potential if there were good people looking to work on specific components.
-
@scottalanmiller said in Should SodiumSuite Be Open Source:
If there were an existing body of open source people clamouring to do this who wanted to get involved, we'd be having a very different discussion. But the assumption is that the interest, at least up front, is extremely small and would undermine the existing interest without generating anything new.
You cant say there's no
if you dont throw out a line or two.You can always move from open to closed source as you see fit as well. Alot of the ML community was interested in helping troubleshoot bugs with SS. So why wouldnt they be interested in making minor contributions.
You probably wont catch a marlin on your first cast, but eventually you will find someone who starts using SS as a daily driver and really starts contributing
-
@IRJ said in Should SodiumSuite Be Open Source:
Alot of the ML community was interested in helping troubleshoot bugs with SS. So why wouldnt they be interested in making minor contributions.
Presumably because willingness to contribute as IT professionals in an IT community wouldn't imply willingness to code. One is the expected skill set of a community of target users. The other is not unexpected, but not directly correlated skill that isn't what the community is about.
-
@IRJ said in Should SodiumSuite Be Open Source:
You probably wont catch a marlin on your first cast, but eventually you will find someone who starts using SS as a daily driver and really starts contributing
Yeah, that's great when it happens. It's boot strapping right now that's the challenge (core team being tied up.)
-
@scottalanmiller said in Should SodiumSuite Be Open Source:
@IRJ said in Should SodiumSuite Be Open Source:
Alot of the ML community was interested in helping troubleshoot bugs with SS. So why wouldnt they be interested in making minor contributions.
Presumably because willingness to contribute as IT professionals in an IT community wouldn't imply willingness to code. One is the expected skill set of a community of target users. The other is not unexpected, but not directly correlated skill that isn't what the community is about.
I am not a dev myself, at all. I am able to improve code sometimes on open source projects. Not in a major way, but every little bit helps.
-
@scottalanmiller said in Should SodiumSuite Be Open Source:
@IRJ said in Should SodiumSuite Be Open Source:
You probably wont catch a marlin on your first cast, but eventually you will find someone who starts using SS as a daily driver and really starts contributing
Yeah, that's great when it happens. It's boot strapping right now that's the challenge (core team being tied up.)
Hmm maybe you should hire a contractor with both salt and development experience....
-
@scottalanmiller said in Should SodiumSuite Be Open Source:
@IRJ said in Should SodiumSuite Be Open Source:
@Obsolesce said in Should SodiumSuite Be Open Source:
@scottalanmiller said in Should SodiumSuite Be Open Source:
It's been kicked around but adds a ton of complication to any monetization strategy.
You can't monetize something that doesn't exist!
That is true as well. Open Source will dramatically reduce your development costs as you have interested parties actually contributing to project
Open source will potentially do that, it could also make it higher. It's not as clear cut as that. The first struggle would be attracting open source developers interesting in contributing who produce more than they cost in additional communications and direction needed.
If there were an existing body of open source people clamouring to do this who wanted to get involved, we'd be having a very different discussion. But the assumption is that the interest, at least up front, is extremely small and would undermine the existing interest without generating anything new.
We don't even know which language... or at least I don't.
