[ramnivasl]

We will eventually offer it as a service.

About the license. Indeed, it is BSL with an additional grant that lifts all restrictions on its users (may run it wherever they like, may even modify and run that version), but it restricts being provided as a service. We believe this strikes a good balance between user freedom and monetization strategy. I would be curious to learn your thoughts.

[threecheese]

I am not at all afraid of the BSL, personally, and believe that it’s at least *a* solution to the fucked up economics of our industry. Professionally, we use two products having BSL-like licenses; one is under a support contract, and the other isn’t, and for the latter workload (CPAL) I was grilled by our legal department for weeks to ensure we abided by the stipulations. My only worry is that the leader who comes in after me might not be aware and may violate accidentally opening the org to risk. So there definitely is friction in the enterprise when using this type of license, but IMO it’s worthwhile to make sure software providers can still earn and not become outcompeted on their own capability by the large providers. For this reason I continue to recommend using these solutions in our workloads.