The way I interpret it: If you aren't making your source code available, and you can't use the Community edition, you'll need a license.
"You distribute your software and do not want to open source the code for your product (as per the GPL). Instead, contact Neo Technology for a commercial OEM setup." "If your product is Open Source software - Neo4j is, too. If not, you must obtain an OEM license from Neo Technology since neither the GPL nor the AGPL permit closed source OEM scenarios." -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Sidharth Kshatriya Sent: Friday, June 24, 2011 7:32 AM To: [email protected] Subject: [Neo4j] Licensing Question for Advanced/Enterprise Edition (AGPL License) I have some questions related to AGPL licensing for Neo4j. If I understand correctly: 1) If I am making a SaaS software which uses Neo4j *and* 2) If I am calling Neo4j from my own code or in other words my software is a client to the Neo4j database server *and* 3) If I am NOT modifying Neo4j code in any way *and* 4) My organization allows me to use AGPL *and* 5) I am not distributing any software which uses Neo4j *Then:* *Simply calling the Neo4j Enterprise Edition/Advanced edition from my own client code does not make my own source code liable to be released under the AGPL. Am I correct in my understanding?* So practically speaking AGPL only means that *if I ever made modifications to Neo4j codebase I would need to give that back to the community? * An answer by a Neo4j team member would be useful. Thanks, Sidharth * * -- Sidharth Kshatriya www.sidk.info _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
