I know that there are several similar discussions here, but I have hard time reconciling them and do not understand the implications of AGPL in few usage scenarios.
Could someone help me understand, please, will or will not AGPL license extend to my software in following cases (sorry for a lot of “I”-s and “my”-s, just want to be a clear in the definition):
my company implements software which populates our DB with some data collected on behalf of our customers; Metabse is deployed/hosted on our servers as-is, and uses data from aforementioned DB; our customers access dashboards directly in Metabase UI itself (Metabase as-is, with Metabase logo) - is this a valid usage scenario and won’t AGPL extend to our software in this case (the data pipeline which populates the DB)?
same scenario as above, but my company also has a custom-built website, and Metabase dashboards are embedded into our website, but with Metabase logo and attributions on the embedding pages; our customers access our custom-built website - does AGPL extend to our software implementing the aforementioned custom web site (embedding software), provided that Metabase branding is kept and attributions are made?
In particular, with regards to latter question, I have found these two threads, which seem to contradict:
In this question - Embed Metabase UI in a web form? - answers mention that “… note that under our license (AGPL), we’d expect any application that uses Metabase components and is redistributed to be open sourced itself.”
But in this question - Embedding Metabase to Another Application - answers mention that “Embedding Metabase in another app is totally okay provided you keep the Metabase branding intact.”