Hacker News new | past | comments | ask | show | jobs | submit login
Ask HN: What license a SaaS company should use when open-source their software?
1 point by ciaovietnam 21 days ago | hide | past | favorite | 4 comments
Hi HNers,

I've developed a low code CMS and Ecommerce SaaS platform (similar to WordPress) that supports 3rd party apps/plugins/templates. To make it easier for developers/freelancers/agencies to create custom apps/plugins/template, I've decided to make the source of the base CMS system available but one thing I'm really concerned is to choose the appropriate license for the software.

I think most open source licenses were created before SaaS era so they do not really fit SaaS business model where direct competition to the platform is not preferred. We can see the recent drama between WordPress and WP Engine as an example, another example is Elastic Search and AWS which has led to AWS forking and promoting OpenSearch instead. Cases like these may discourage the founders/developers from contributing more to the software and divide the community into different groups which is something most founders try to avoid. I've explored SaaS friendly licenses such as MongoDB's Server Side Public License or ElasticSearch's Elastic License 2.0 but both licenses are not considered open source license by the OSI standards, moreover they are still ambiguous and may create more confusion to anyone wanting to use the software.

I just want other developers to use the software to create custom plugins/apps or make web/mobile apps for their clients, they may even provide hosting for their clients as part of their development service (this is not considered direct competition if the hosting fee is 30% or less of the total charge) but I do not want someone to just take the code and simply provide mass hosting for it (this is direct competition). What license do you guys think it will work for my case? I would prefer to utilize an existing license that is associated with a well-established software project. I am not inclined to use or create a new license, as this would require developers and companies to assess the license before proceeding with its use.




You might want to consider just open sourcing portions of your code that you believe could benefit from community involvement, and keep certain things proprietary. If that is an option you could have separate repos and publish the ones you want to share.

If that’s not an option, it may be that opening up the code doesn’t fit your business model


Yeah, that's exactly what we have in mind, the core source code is available to anyone to utilize for any commercial purposes except providing mass hosting for the source code without any substantial development/customization. Do you think this restriction will prevent people from using the software?


You might want to look into the "commons clause". It is a non opensource addition to a license, but is relative simple.

You will not find an OSI license with the protections you want because it is a violation of open source principles.


Yeah, the Common Clause license is pretty close to what I want, I'm just concerned with the SaaS offering in one of the examples in the license:

"Let’s apply the example to Commons Clause licensed software. Commons Clause-licensed Redis Graph is a graph database module for BSD-licensed Redis. Can you create applications with Redis Graph and distribute and/or sell them? Yes. Can you redistribute Redis Graph along with your application? Yes. Can you offer that application as SaaS and charge for it? Yes. Can you take Redis Graph itself, call it ElastiGraph and offer it as SaaS and charge for it. No."

It could be that the application developed with Redis Graph is totally different to Redis Graph so SaaS offering is allowed. I will check this further, thanks for your suggestion.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: