End-User License Agreement Template
The following is a template for an end-user license agreements (EULA) that you can use in your project to require the Maintenance Fee.
The Open Source Maintenance Fee EULA Template
Feel free to use this template as your project’s binaries’ EULA to require all revenue generating consumers to pay the Maintenance Fee.
End User License Agreement
This Open Source Maintenance Fee Agreement ("Agreement") is a legal agreementbetween you ("User") and <PROJECTNAME> ("Project") for the use of<SOFTWARENAME> ("Software"), an open source software project licensed underthe <OSILICENSE> ("OSI License"), an OSI-approved open source license.Project offers a Binary Release of the Software to Users in exchange for amaintenance fee ("Fee"). "Binary Release" refers to pre-compiled executableversions of the Software provided by Project. By accessing or using theBinary Release, User agrees to be bound by the terms of this Agreement.
1. Applicability
Project agrees to provide User with the Binary Release in exchange for theFees outlined in Section 2, subject to the terms of this Agreement. The Feeapplies only to Users that generate revenue by the Software.Non-revenue-generating use of the Software is exempt from this Fee. Inaddition, Users who pay separate support and/or maintenance fees to themaintainers of the Software are exempt from the Fee outlined in thisAgreement. This distinction ensures that duplicate fees are not imposed,promoting fairness and consistency while respecting alternative supportarrangements.
2. Monthly Fee and Payment Terms
Revenue-generating Users required to pay the Fee shall follow the paymentterms set forth by the Project. Failure to comply with these terms may resultin suspending access to the Binary Release. However, this does not restrictthe User from obtaining or redistributing binaries from other sources orself-compiling them.
3. Nature of the Fee
The Fee is not a license fee. The Software's source code is licensed to Userunder the OSI License and remains freely distributable under the terms of theOSI License and any applicable open-source licenses.
4. Conflicts with OSI License
To the extent any term of this Agreement conflicts with User's rightsunder the OSI License regarding the Software, the OSI License shall govern.This Agreement applies only to the Binary Release and does not limit User'sability to access, modify, or distribute the Software's source code orself-compiled binaries. User may independently compile binaries from theSoftware's source code without this Agreement, subject to OSI License terms.User may redistribute the Binary Release received under this Agreement,provided such redistribution complies with the OSI License (e.g., includingcopyright and permission notices). This Agreement imposes no additionalrestrictions on such rights.
5. Disclaimer of Warranty and Limitation of Liability
THE SOFTWARE AND BINARY RELEASE ARE PROVIDED BY THE PROJECT "AS IS" AND ANYEXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE PROJECT OR ITS CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USEOF THE SOFTWARE AND BINARY RELEASE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.