I’m interested in forking the baserow codebase(s) and using it to build on top-of. However, the licensing seems convoluted. Ideally, I like something like Apache 2.0. I want to do things commercially with this software, but I find the licenses to be somewhat convoluted.
I basically want to build ontop of baserow a very specific niche feature. Then repackage and sell it to specific niche companies after trying it out as an internal tool for myself. There are no guarantees that what I want to build will be wanted by anyone else. I want to keep a majority of the code I write closed source and just use some of the existing architecture baserow has in-place. It would not be a SaaS and wouldn’t directly compete with baserow in my opinion. I’m not sure if this is permissible under the multiple licenses within the baserow repo. I would obviously have to fork the repo and self-host.
Basically, I want to know the following:
Are the people at baserow okay with this kind of thing?
Is this permissible under the current licenses and how do I do this in a way that stays true to the licenses under the repo?
The stuff I would build would be separate both in architecture of hosting and separate codebases. The only unique differences that would be part of the existing codebase would be a different cost structure. It would be by transaction and not per month. A pay-per-use pricing model. I basically want to use baserow as a high-fidelity front end, because I don’t care to rebuild a spreadsheet interface from the ground up but I feel like it would be a good way to do what I am trying to accomplish with less risk. My background is in software development and I am extremely comfortable with hosting and code.
All the best,