Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I m thinking of using iTextSharp, which is licensed under Affero GPL, in an internal closed-source WinForms project. No one outside my company will be using it.

GPL (and Affero GPL as well) typically demands that the source be provided with the binary. Given that this is an internal project, do I need to provide my employees with the source code of the project?

share|improve this question
up vote 16 down vote accepted

If you confine use of the library to within the walls of your corporation, you do not have to distribute the source (even to your employees), because you are not redistributing (selling or giving away a software product that includes the library) outside of your organization.

The GPL allows you to freely use the code inside a corporation without restrictions, and that includes (by necessity) your ability to prevent your employees (as a matter of company policy) from distributing the source code outside the organization.

From the Gnu Licensing FAQ:

Is making and using multiple copies within one organization or company “distribution”?
No, in that case the organization is just making the copies for itself. As a consequence, a company or other organization can develop a modified version and install that version through its own facilities, without giving the staff permission to release that modified version to outsiders.

However, when the organization transfers copies to other organizations or individuals, that is distribution. In particular, providing copies to contractors for use off-site is distribution.

share|improve this answer
The AGPL has a few more restrictions, if you distribute a service generated from an AGPL app then you are distributing the app. – Martin Beckett Aug 12 '11 at 3:31
@martin: Yes, but if you are using the site or service internally (i.e. it's on the intranet, and not on an internet-facing web server), then it is not considered redistribution, and you are still OK. The GPL differs from the AGPL in that, if you are using open-source software to run a public web site or service, the GPL doesn't consider the use of that site or service by the public redistribution, but the AGPL does. – Robert Harvey Aug 12 '11 at 3:33
your answer is correct. I was just pointing out that you linked to the GPL not AGPL faq, although for this use the difference doesn't matter – Martin Beckett Aug 12 '11 at 12:32
It doesn't matter anyway. A license cannot set its own scope, and whether you are 'distributing' the software or not is a question of license scope. (Copyright law says you cannot distribute a work without a license.) By law, if you are not making the copyrighted work itself available, you are not distributing it. – David Schwartz Aug 13 '11 at 12:58
@David - the license can set any requirements it wants. I can licence my software not to be used commercially, not to be used to control nuclear power stations, or not for use by ginger haired people. The license can apply to the use of the software and it's output - not just it's own distribution – Martin Beckett Aug 14 '11 at 15:39

You have to offer to supply the source and any modifications - to anyone you distribute the binary to.
Since you only distribute it to users inside your company that shouldn't be too much of a problem !

note: the AGPL is basically the GPL with the addition that you consider web users of a service based on the code to have had the software distributed to them - and so get the source.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.