I’m a bit confused with AGPL license, so I ask for advice. I read contradictory things on the matter.

I want to make an android app. The backend will use AGPL modified material : stable diffusion WebUI. The backend will probably have some more stuff (like AWS integration code) AND will be usable without the front-end (it’s gonna be an API, a project in itself). The front-end (android app) will be usable witout THIS specific backend (but will require a backend, IE an API who return images).

So, tell me if any of these are wrong :

  1. (Almost sure of that) Everything related to the stable diffusion WebUI must be AGPL.

  2. (Quite sure of that) The whole backend (including AWS-related stuff) MUST be AGPL.

  3. (No idea if it’s true) The android app itself (wrapping) can be distributed with an other license (for example CC-NC).

Just making sure I get things right!

  • How does the front-end communicate with the back-end? HTTP requests or other well-documented API? Some interface unique to your app?
    – MadHatter
    Feb 7, 2023 at 22:48
  • Yes, them will communicate, probably with the AWS API Gateway Feb 8, 2023 at 15:04
  • Who will define the API? You? Or does the AWS API gateway itself impose a standard for request format and transport?
    – MadHatter
    Feb 8, 2023 at 15:29
  • AWS API Gateway impose a format (HTTP), but I will be defining the API (what requests will be processed and how). Feb 8, 2023 at 16:40
  • 1
    I just checked again the AWS API Gateway doc, both HTTP and REST are available. Are you saying that, if my API is easily usable by any user (aka i’m using standard request and I document them), then the backend can be considered as a project in itself ? (therefore allowing my front-end to be CC-NC?) Feb 9, 2023 at 6:24


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.