I am developing an application (Budibase) that will be used to build and host web applications. My application is a Low Code Development Platform. Think Wordpress, except that the output would be a Web 2.0 Application (e.g. like Trello), instead of a website.
My goals are
- To allow any application built with the system to be closed source
- To prevent another project/organisation using any of our code to build a competing, closed sourced (or relicensed) Low Code Platform.
So, overall, I wish to license using a GPL-like license. AGPL feels right to me.
However, I believe that AGPL causes an issue. The core library is distributed to the browser, and used by every (closed source) application that is built on the platform.
I feel like the core library should be
AGPL when linked in a web server environment
MPL when linked in a browser environment
Do you know of any examples like this in the world?
Or do you have any alternative suggestions as to how I could license my core library?
Do you think my "dual OS licence" suggestion would be acceptable today? (this is purely opinion, I know, thought I'd sneak it in)