SOD Licensing Terms for Open Source and Commercial Use
Understand how SOD can be used in open-source and closed-source products, including GPLv3 requirements, redistribution rules, and commercial licensing for shipped applications.
General Licensing Terms
SOD is an open-source product. The complete source code ↗, the official documentation ↗, and related utilities are available from the PixLab download page.
Symisc Systems ↗, the developer of SOD, uses a dual-licensing model that gives you a choice between an open-source license and a non-exclusive commercial license. Under the GPLv3 ↗, SOD can be used in open-source projects or in applications that are not distributed to third parties. The commercial license covers closed-source distribution to third parties. The GPLv3 ↗ allows use of the SOD library at no charge as long as any host application using the library makes its complete source code available under reasonable redistribution terms.
If you want to keep your application closed source instead of releasing it under the GPLv3 or another compatible open-source license, you must purchase a non-exclusive commercial SOD license. With a commercial license, you no longer need to release your application's source code.
Non-exclusive Commercial License
The non-exclusive commercial license allows customers to develop, use, and distribute applications that embed the SOD library under standard commercial terms. This license is sold "per host product," regardless of the number of copies sold or the number of releases. For example, if a company has three distinct products that each embed SOD and does not want to comply with the open-source terms, it must purchase three commercial licenses.
The non-exclusive commercial license is offered for a fixed, non-refundable annual fee. Pricing is tailored to the licensee’s legal entity, including individuals, micro ISVs, startups, and enterprise customers. You can purchase a non-exclusive commercial SOD license from the download page.
Frequently Asked Licensing Questions
What does "redistribute" mean?
In the open-source world, "redistribution" means your application is provided to one or more third parties. Giving an application to customers, even in alpha or beta releases, counts as redistribution. Giving contractors, affiliates, parent organizations, subsidiaries, business partners, or support vendors a copy of the application also generally counts as redistribution. Whether or not you charge money does not matter. Internal-only use inside your organization is generally not redistribution. If you have questions about redistribution, contact [email protected].
What must I release as open source?
Under the open-source license, you must release the complete source code for the application that embeds the SOD library. You do not need to release components that are generally installed on the operating system where your application runs.
Does it matter if I charge money for my software?
Whether or not you charge money for your application does not matter. What matters is redistribution and source-code availability under the applicable open-source terms.
What open source license should I use in my project?
Any project that uses a license compatible with the GPLv3, such as GPL, Apache License 2, Boost License, Mozilla Public License, or the Expat License, can incorporate SOD under the open-source terms. Releasing an application that embeds SOD under another open-source license does not change the requirements of the SOD GPLv3 license. If your project uses a license not listed in the GPLv3 compatibility list and you believe it is compatible, email [email protected] with a copy of the license for review.
For legal, licensing, or other general inquiries, email [email protected] or [email protected]. For technical support, use the official support channels instead.