Hi, Is there a licensing guide available somewhere for the “Frappeverse” (Frappe Framework + Apps)? In another topic @rmehta confirmed that the current strategy of Frappe is to release new apps under the AGPL license. I think this is a good strategy because it can ensure the long-term success of t…

@peterg Lets use an example of using AGPLed code like Builder: When you do frappe.get_doc("Builder Page", ...) aren’t you effectively using builder as a library? You’re not just exchanging data here, you get access to class defined inside builder, you can execute builder code with it and so on. I…

If this is Frappe’s stance, I hope you’ll make it publicly explicit. I don’t think I’ve ever seen this stated anywhere before. I don’t agree with your interpretation, but it is significant if this is Frappe’s official position. Even as GPL, there are huge implications for ERPNext here as well.

If this is Frappe’s stance, I hope you’ll make it publicly explicit. I’ll talk to others and draft a document. In any case, we are not litigious about licenses so far :smile: I deliberately used “In spirit of license”. If you need your product/service to be proprietary while depending on AGPL c…

Someone else can still sue you for license violation, our interpretation doesn’t matter. E.g. Software Freedom Conservancy sues Vizio for GPL violations | ZDNET

In principle we are very much for the idea of free software and that the primary goal of free software is freedom and not making a business. Our new licenses reflect that. Though we have not explictly mentioned, applications that are used by end customers are AGPL and pure developer tools (like Fra…

Frappe’s commitment to open source is clear and beautiful. I’ve really admired the organizations ethos, long after I came to enjoy the framework. I think where things get less clear is what counts as “incorporating” AGPL/GPL software. In Ankush’s example, I appreciate that a get_doc call and an im…

[image] peterg: If Frappe’s stance is that class access is the threshold here, I’d wonder about Rushabh’s earlier statement about Builder pages. If they make API calls that return class instances, wouldn’t they also have to be licensed AGPL? This is an interesting question, specially for Buil…

@ankush When you do frappe.get_doc("Builder Page", ...) aren’t you effectively using builder as a library? You’re not just exchanging data here, you get access to class defined inside builder, you can execute builder code with it and so on. What if you do the same thing over the REST API that Fr…

[image] ankush: Someone else can still sue you for license violation, our interpretation doesn’t matter. E.g. Software Freedom Conservancy sues Vizio for GPL violations | ZDNET Software Freedom Conservancy usually represents specific developers whose GPL licensed code was incorporated into …

[image] rmehta: This is an interesting question, specially for Builder because Builder is both the design and publishing tool. Builder pages though I reckon are not derivative of Builder (just like documents written in say Libre Office are not derivatives of Libre Office) and should not be subje…

Frappe.io Frappe Cloud Documentation Partners Frappe School Marketplace Community Chat (new!)

Frappe Forum

Frappe Licensing & Software Architecture

Community

revant_one July 16, 2026, 10:15am 28