It is unclear in your question how your program relates to this AGPL software. There are at least two possibilities:
If your software keeps the AGPL code as a clearly separated component that your code uses as an external program (e.g. in Java/GWT, Runtime.getRuntime().exec(params)), then your program does not need to be licenced as AGPL and you do not have to distribute the sources of your code, but you must make the sources of the AGPL software as easily available as your application (section 6d of AGPL v3).
If your software merges somehow with the AGPL software, even just creating a wrapper around it, in a way that the separation is not clear or they cannot "reasonably [be] considered independent and separate works in themselves", then your program can be considered a derivative work and therefore must be licenced as AGPL, and you must distribute the source code of both your program and of the original AGPL software.
I would like to stress that there is nothing wrong with charging for access / use of AGPL software. You only need to provide the source, nothing prevents you from charging a fee or earning money from advertising (like those websearch companies that run on modified linux kernels).
根据 http://en.wikipedia.org/wiki/Affero_General_Public_License AGPL 的两个版本都旨在弥补普通 GPL 中应用程序服务提供商所感知的“漏洞”（“ASP 漏洞”），即使用但不分发软件时，不会触发 Copyleft 条款。每个版本与其所基于的 GNU GPL 版本的不同之处在于具有解决通过计算机网络使用软件的附加条款。附加条款要求 AGPL 许可作品（通常是 Web 应用程序）的任何网络用户都可以使用完整的源代码。
As per http://en.wikipedia.org/wiki/Affero_General_Public_License Both versions of the AGPL were designed to close a perceived application service provider "loophole" (the "ASP loophole") in the ordinary GPL, whereby using but not distributing the software, the copyleft provisions are not triggered. Each version differs from the version of the GNU GPL on which it is based in having an additional provision addressing use of software over a computer network. The additional provision requires that the complete source code be made available to any network user of the AGPL-licensed work, typically a Web application.
长答案是肯定的，但您还必须发布您的来源。某些应用程序使用此结构，例如官方 XChat windows 版本。
In short, no. According to Wikipedia the AGPL license is just like the GPL license with added clauses for use over a network.
The long answer is yes, but you'd also have to publish your source. Some applications use this structure, for example the official XChat windows builds.
发布评论
评论（3）
您的问题不清楚您的程序与该 AGPL 软件有何关系。至少有两种可能性：
我想强调的是，对 AGPL 软件的访问/使用进行收费并没有什么问题。你只需要提供源代码，没有什么可以阻止你收取费用或通过广告赚钱（就像那些运行在修改后的Linux内核上的网络搜索公司）。
It is unclear in your question how your program relates to this AGPL software. There are at least two possibilities:
I would like to stress that there is nothing wrong with charging for access / use of AGPL software. You only need to provide the source, nothing prevents you from charging a fee or earning money from advertising (like those websearch companies that run on modified linux kernels).
根据 http://en.wikipedia.org/wiki/Affero_General_Public_License
AGPL 的两个版本都旨在弥补普通 GPL 中应用程序服务提供商所感知的“漏洞”（“ASP 漏洞”），即使用但不分发软件时，不会触发 Copyleft 条款。每个版本与其所基于的 GNU GPL 版本的不同之处在于具有解决通过计算机网络使用软件的附加条款。附加条款要求 AGPL 许可作品（通常是 Web 应用程序）的任何网络用户都可以使用完整的源代码。
As per http://en.wikipedia.org/wiki/Affero_General_Public_License
Both versions of the AGPL were designed to close a perceived application service provider "loophole" (the "ASP loophole") in the ordinary GPL, whereby using but not distributing the software, the copyleft provisions are not triggered. Each version differs from the version of the GNU GPL on which it is based in having an additional provision addressing use of software over a computer network. The additional provision requires that the complete source code be made available to any network user of the AGPL-licensed work, typically a Web application.
简而言之，不。根据维基百科，AGPL 许可证就像 GPL 许可证一样，添加了通过网络使用的条款。
长答案是肯定的，但您还必须发布您的来源。某些应用程序使用此结构，例如官方 XChat windows 版本。
In short, no. According to Wikipedia the AGPL license is just like the GPL license with added clauses for use over a network.
The long answer is yes, but you'd also have to publish your source. Some applications use this structure, for example the official XChat windows builds.