AGPLv3 License Question

[dashi]

Hello Proxmox Gurus!

I'm an engineer working for a company that's looking to move away from VMware products and we're exploring Proxmox as a virtualization solution. In short, I'm looking to confirm that AGPLv3 is compatible with our product.

Specifically, our product imports the PVE API (proxmoxer) and commands clusters of Proxmox machines to clone and modify VMs from templates through the REST interface. Our product does not modify the Proxmox OS or binaries, it only commands them using the REST APIs to perform virtualization functions.

We are looking to release our product with a closed-source license to paying customers. Is that integration compatible with AGPLv3, or does simple interfacing require distribution of our source code?

Thank you for your help!

 

[esi_y]

Hello Proxmox Gurus!

I'm an engineer working for a company that's looking to move away from VMware products and we're exploring Proxmox as a virtualization solution. In short, I'm looking to confirm that AGPLv3 is compatible with our product.

Specifically, our product imports the PVE API (proxmoxer) and commands clusters of Proxmox machines to clone and modify VMs from templates through the REST interface. Our product does not modify the Proxmox OS or binaries, it only commands them using the REST APIs to perform virtualization functions.

It is highly probable your product, as described will be considered a "mere aggregation".

We are looking to release our product with a closed-source license to paying customers. Is that integration compatible with AGPLv3, or does simple interfacing require distribution of our source code?

Having a standalone product that accesses another via API especially if you do not ship it bundled is not something I would worry about in terms of licensing compatibility.

Thank you for your help!

But this is not something you can ask on a forum, you certainly do not ask the vendor, you ask your company's counsel. They do not lincense out AGPL out of goodness of their heart.

 

[spirit]

We are looking to release our product with a closed-source license to paying customers. Is that integration compatible with AGPLv3, or does simple interfacing require distribution of our source code?

yes, you can release it as closed-source, no problem.



BTW, open != free , you could still release your software as opensource with paying customers

 

[esi_y]

BTW, open != free , you could still release your software as opensource with paying customers

Now that you mention this, I wonder why nobody has any problem with Veeam. It's the one thing I would give to PBS, if I do not like it, at least I can change it.

 

[spirit]

Now that you mention this, I wonder why nobody has any problem with Veeam. It's the one thing I would give to PBS, if I do not like it, at least I can change it.

"nobody has any problem with Veeam" -> only ransomwares

 

[Johannes S]

We are looking to release our product with a closed-source license to paying customers. Is that integration compatible with AGPLv3, or does simple interfacing require distribution of our source code?

This looks like a question for lawyers not technicians or forum lurkers like myself. So I would sugggest to ask your lawyer and proxmox Office. Their contact Mail is on
https://www.proxmox.com/en/about/contact

Hope this helps

 

[Stoiko Ivanov]

Specifically, our product imports the PVE API (proxmoxer) and commands clusters of Proxmox machines to clone and modify VMs from templates through the REST interface. Our product does not modify the Proxmox OS or binaries, it only commands them using the REST APIs to perform virtualization functions.

In general please note that the AGPLv3 is quite similar to the GPL in what users of a software licensed by it can do.
Because as with the GPL, most restrictions and obligations only apply if one modifies the software in question under that license.

Adopting/Using software with the AGPLv3 license should not be an issue, especially if you do not plan to modify said software at all.

You are also allowed to access the Proxmox VE API without any obligations on the source of the program doing so.

Calling our existing command line utilities from some scripts, or things like automation stacks, is also fine, as this is a clear API boundary too.

I hope this helps!

 

[sterzy]

BTW: If you want an explainer of the differences between GPL and AGPL in more laymen's terms, the FSF has this article for you [1].

[1]: https://www.gnu.org/licenses/why-affero-gpl.html