Copyright 2025 Naked Software, LLC
Version 1.0.0 (May 26, 2025)
This Authorization Service License Agreement ("Agreement") is a legal agreement between you ("Licensee") and Naked Software, LLC ("Licensor") for the use of the Authorization Service software product ("Software"). By using the Software, you agree to be bound by the terms of this Agreement.
Licensor grants Licensee a non-exclusive, non-transferable, non-sublicensable license to use the Software for non-commercial, educational, or other non-production purposes. Licensee may not use the Software for any commercial purposes without purchasing a commercial license from Licensor.
To use the Software for commercial purposes, Licensee must purchase a commercial license from Licensor. A commercial license allows Licensee to use the Software in production environments, build their own version, and add custom features or bug fixes. Licensee may not sell the Software or any derivative works to others.
Licensee may create derivative works of the Software for their own use, provided that they maintain a valid commercial license. Licensee may not sell or distribute derivative works to others. Any derivative works must include a copy of this Agreement and retain all copyright notices.
Licensee may share their changes or bug fixes to the Software with others, provided that such changes are made freely available and not sold. Licensee is encouraged to contribute their bug fixes back to Licensor for inclusion in the Software.
Licensee may not:
- Use the Software for any commercial purposes without a valid commercial license.
- Sell, sublicense, or distribute the Software or any derivative works.
- Remove or alter any copyright notices or proprietary legends on the Software.
This Agreement is effective until terminated. Licensor may terminate this Agreement at any time if Licensee breaches any of its terms. Upon termination, Licensee must cease all use of the Software and destroy all copies in their possession.
The Software is provided "as is" without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and noninfringement. In no event shall Licensor be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Software or the use or other dealings in the Software.
In no event shall Licensor be liable for any indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of the Software, even if advised of the possibility of such damage.
This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction in which Licensor is located, without regard to its conflict of law principles.
This Agreement constitutes the entire agreement between the parties with respect to the Software and supersedes all prior or contemporaneous understandings regarding such subject matter.
By using the Software, you acknowledge that you have read this Agreement, understand it, and agree to be bound by its terms and conditions.
Authorization Service is a product that we are proud of. But it's not just the finished product that we're proud of. We're proud of the work and craftsmanship that goes into the source code for the product. We're so proud of the source code, that we want to share it with others to see.
Traditionally, there have been two models for software development: open source and closed source. There are many great and wonderful open source products, and we use many of them ourselves within Authorization Service or used by Authorization Service. Closed source companies are the traditional vendors of software applications and customers don't get to see the internal workings of the product.
Naked Software, LLC, wanted to go in a hybrid direction. We obviously want to make money from people using our products as we have a business that we want to grow, we want to provide for ourselves and our families, and we want to hire people in the future and provide for them and their families. But we also want to make our source code open and available to our customers to customize and use, and we can't really come up with a good reason why we should keep our source code hidden or secret.
Naked Software, LLC, also believes that there is value in the source code for students who are learning about software development, and other professionals who are looking to grow their skills or building products that we, ourselves, may use. Our architectural decisions may inspire others to follow our path (or not to, which is valid as well). They way that we implement, build, and deploy our software may inspire the development of future wonderful products and services by others.
It's also just as likely that we'll get hate mail and criticism for our software and our source code, but we're willing to take that. Our source code and the Authorization Service product is not set in stone and will constantly evolve and get better (or occasionally worse). What's important is that our best work is always going to come tomorrow, sometimes good features have shaky code behind them, but there's always another day to learn more and come back and make something better.
Another reason for making the source code available is that we believe that having the source code open and reviewable with others will open opportunities for collaboration and community building with other software developers and companies. By making the source code available for how Authorization Service works, other independent developers or companies can collaborate with us on building new feature or improving existing features. Other developers and businesses can also create complimentary products that integrate with Authorization Service, providing even more value for our customers.
It is our belief that this approach is in line with the principles of the Fair-Code movement and will be a successful business model moving forward.
Yes, you can use the Authorization Service source code for non-commercial, educational, research, or other non-production purposes. The use of Authorization Service source code for building commercial products or services is prohibited under the license agreement.
Yes, to use Authorization Service for any commercial purposes, including in production environments, you must purchase a commercial license from Naked Software, LLC.
Yes. You are free to build and host your own Authorization Service service and build the client applications for web, mobile, or desktop for your own use. But to use Authorization Service as a user in any production setting on your devices requires that you purchase a commercial license from Naked Software, LLC.
Yes, you can create derivative works of the Authorization Service source code for your own use. However, if you intend to use these modifications in production or for commercial purposes, you must have a valid commercial license.
Yes, you can share your changes or bug fixes with others as long as they are made freely available and not sold. You are also encouraged to contribute your bug fixes back to Naked Software, LLC, for inclusion in the official software.
No, you cannot sell, sublicense, or distribute the Authorization Service software or any derivative works without a valid commercial license. Even with a commercial license, you may not sell the software or derivative works to others.
No, you cannot use the Authorization Service source code in a commercial product without a valid commercial license. Additionally, you cannot sell or distribute derivative works based on Authorization Service.
If you violate the terms of the license agreement, Naked Software, LLC, may terminate the agreement. Upon termination, you must cease all use of the software and destroy all copies in your possession.
No, the Authorization Service software is provided "as is" without warranty of any kind, express or implied. Naked Software, LLC, is not liable for any claims, damages, or other liabilities arising from the use of the software.
If you want to use Authorization Service for commercial purposes, you should contact Naked Software, LLC, to purchase a commercial license. Commercial licenses for individual use may also be purchased from the Apple App Store or Google Play Store.
You can contribute your bug fixes by submitting them to Naked Software, LLC, through the appropriate channels, such as a pull request on the official GitHub repository. This helps to improve the software for all users. For more information, please review the Contribution Guidelines.
I developed a new feature for Authorization Service using the source code. How can I contribute it back to the product?
Naked Software encourages individual software developers or business customers to customize the Authorization Service product to fit their needs. While we will accept bug fixes that have gone through a code review process, we are unable to accept feature contributions at this time. Instead, we encourage you to submit new feature ideas to us either using the Discussions forum on GitHub or creating a feature request as an issue on the Authorization Service repository.
We appreciate your willingness to build and contribute a new feature. Given that Authorization Service is not an open source product and not licensed under an compatible open source license, Naked Software, LLC, is unable to accept new feature contributions from customers or third-parties due to intellectual property, licensing, and ownership concerns. However, we would be extremely happy to receive your feedback and collaborate with you on the implementation of the new feature if we feel that it fits into our scope and vision for the Authorization Service product.
If you have additional questions about the Authorization Service Source Code License Agreement and how you may use the source code, please post your question to the Discussions forum or email your question to Naked Software Support at support@naked.software.