What are Apache, GPL and AGPL licenses – misconceptions, lies, facts

openobserve.ai

3 points·prabhatsharma··3 comments

> You are building a software that uses an AGPL software by calling its APIs : Your software is a covered work and you need to license it under AGPL and make the source code available to your users. A concrete example would be a monitoring software that calls OpenObserve APIs to provide its core functionality.

So, if you use it for logging and send logs to OpenObserve using the OpenObserve API, you need to license your software under AGPL.

Short answer - no. You don't have to if you are sending logs data.

Long descriptive answer. It depends on, if your software is a covered work.

You are building a software that uses an AGPL software by calling its APIs : Your software is a covered work and you need to license it under AGPL and make the source code available to your users. A concrete example would be a monitoring software that calls OpenObserve APIs to provide its core functionality.

You are building a software and use a software licensed under AGPL to monitor your application: Your software is not a covered work and you can license it under any license you want. A concrete example would be - you using OpenObserve to monitor your closed source e-commerce application.

> You are building a software and use a software licensed under AGPL to monitor your application:

If you are using a software licensed under AGPL to only monitor your application, but you do that by calling its APIs, your software is a covered work, isn't it?

Reply on news.ycombinator.com