Why Spree is Changing its Open-Source License to AGPL-3.0 and Introducing a Commercial License
Spree Commerce is a free, open-source eCommerce framework giving you full control and customizability. Starting with the new Spree version 4.10, we’ll be switching its license to AGPL-3.0. We’re also introducing a Commercial License as an alternative to AGPL-3.0 in a dual-licensing model. Here’s why.
What This Means for Most Users
The good news is that for most users, very little will change:
- Spree will remain free and open source for production use
- AGPL-3.0 is a standard license approved by the Free Software Foundation and the Open Source Initiative
- Many open source projects have switched to this license lately, including Shopware, Cal, Lago, ParadeDB, Plausible and many others
This change primarily affects businesses intending to use Spree as part of a SaaS offering or otherwise distribute (sell) Spree or Spree-derivative works over the network to their customers.
Why the Change?
1. Protecting the Open-Source Ecosystem: The AGPL-3.0 license ensures that modifications to Spree, when used to launch a SaaS or a cloud-based business, must be made available to the community. This fosters a more collaborative environment and prevents companies from benefiting from the open-source project without contributing back.
2. Ensuring Sustainability: By offering a commercial license option as an alternative to open-sourcing, we can generate revenue to support ongoing development and maintenance of the Spree project, ensuring its long-term viability. And we have very ambitious goals for Spree 5.0 and beyond.
3. Balancing Open-Source and Commercial Interests: The dual-licensing approach allows us to maintain the open-source nature of Spree while also providing an alternative for businesses that require more flexibility in their licensing terms.
Understanding the License Change
The Previous License: BSD-3-Clause
Up until version 4.9, Spree Commerce was licensed under the BSD-3-Clause license. This permissive license allowed users to modify and distribute the software with minimal restrictions, including for purposes such as starting their own SaaS business using Spree.
The New License: AGPL-3.0
First and foremost, it’s crucial to understand that under AGPL-3.0 production use of Spree for your own business or your customers’ businesses will remain free, just as it has been under the previous license.
This change does not affect the vast majority of Spree users who build and operate their own eCommerce sites or develop them for a client.
The GNU Affero General Public License version 3 (AGPL-3.0) is a copyleft license designed to ensure that the software remains free and open. Here are the key points:
- Free for Most Uses: You can freely use, modify, and distribute Spree for your own eCommerce sites or those you build for clients, without any new obligations.
- Source Code Availability: The AGPL-3.0 requires that the source code be made available to users who interact with the software over a network. However, this primarily affects SaaS (Software as a Service) or cloud service providers.
- SaaS Providers: If you’re using Spree as part of a SaaS offering where multiple clients interact with your modified version of Spree over a network, you are required to make your modifications available under the AGPL-3.0 license.
- Contributions Back to the Community: This license encourages SaaS providers who benefit from Spree open-source to contribute their improvements back to the community, fostering a more collaborative and robust ecosystem.
- Commercial License Option: For SaaS businesses that prefer not to share their modifications, we offer a commercial license option (more on this later).
- Compatibility: AGPL-3.0 is compatible with many other open-source licenses, allowing for integration with a wide range of other open-source software.
This license change aims to strike a balance between keeping Spree free and open for the majority of users while ensuring that large-scale commercial users contribute back to the project’s development, either through code contributions or by supporting the project financially through commercial licensing.
Which Spree Versions Have the New License
For Spree Commerce versions 4.10 and later in the spree/spree repository, two licenses apply simultaneously and users are required to comply with the terms of these two licenses at the same time:
- AGPL-3.0 – for all contributions in version 4.10 onwards
- BSD-3-Clause – for all other contributions predating version 4.10
Effectively, for Spree versions 4.10 and upwards, the AGPL-3.0 license applies as a more restrictive of the two but a compatible license.
Spree Commerce versions 4.9 and earlier in the spree/spree repository are available under the BSD-3-Clause license and users are required to comply with its terms. There is no licensing change.
Commercial License Option
If you’d like to use Spree Commerce without the AGPL-3.0 restrictions, e.g., for a SaaS or a cloud-based business, please talk to us about obtaining a Commercial License.
Should you decide to use Spree Commerce version 4.10 or later for commercial redistribution (e.g., SaaS) – also known as Commercial Distribution – you must do so in accordance with the terms and conditions contained in a separate written agreement between you and Vendo Connect Inc.
For more information about the Commercial License (CL), please contact us through the Spree website.
Upcoming Spree Commerce 5.0 version
There’s an unprecedented upcoming investment in new Spree open-source features, including a new admin dashboard UI, a new storefront, a drag & drop page builder and many more. Read that full announcement here.
These new features in Spree 5.0 and followup versions demonstrate our commitment to providing a powerful, flexible, and user-friendly eCommerce platform.
By open-sourcing these sophisticated features, previously only available in commercial projects, we’re ensuring that the entire Spree community can benefit from these advancements.
We’re excited about the possibilities these new features will unlock for Spree users, and we can’t wait to see how our community will leverage them to create even more impressive eCommerce experiences.
Spree Licensing FAQ
1. What can I do with Spree under the AGPLv3 license?
You are free to download, reuse, modify, and distribute any files hosted in the spree/spree Github repository under the terms of the AGPL version 3.
2. Can I combine Spree under the AGPLv3 with any code under other licenses?
Yes, AGPLv3 is compatible with the following licenses: GPLv3, GPLv2 (or any later version), LGPLv3, LGPLv2.1 (or any later version), BSD license (2-clause and 3-clause), MIT license and Apache License 2.0.
3. Does the license cover just Ruby, or everything?
We require that all files in this repository (Ruby, JavaScript, CSS, HTML) that are not part of a bundled 3rd party library are under the terms of the AGPLv3.
4. Can I contribute to Spree under AGPLv3?
All new contributors retain copyright on their code but agree to release it under AGPLv3. If you are unable or unwilling to contribute a patch under AGPLv3 and the Commercial License, do not submit a patch.
5. I want to release my code under a different license than AGPLv3, is that possible?
No. You can only release your work under AGPLv3 or a later compatible license.
6. The AGPLv3 requires that I distribute the “source code” of my files. What does that mean?
The “source code” of a file means the format that is intended for people to edit. For Ruby, JavaScripot, CSS, and HTML code, the file itself, without any compression or obfuscation, is its own source code.
7. If I write an extension for my Spree application, do I have to license it under the AGPLv3?
Yes. Spree extensions for your application are a derivative work of Spree. If you distribute them, you must do so under the terms of the AGPLv3 or later. You are not required to distribute or sell them at all, however. You can keep them private.
8. If I write an extension for my application, do I have to share it with everyone?
No. You are only required to provide the source code to those you distribute the extension to. If you do not distribute the code but use it only within your organization, you are not required to distribute it to anyone. You can keep it private.
9. Am I allowed to sell Spree or a Spree extension?
Yes. However, you must distribute it under the AGPL version 3 or later, so those you sell it to must be allowed to modify and redistribute it as well.
10. Do I have to give the code for my website to anyone who visits it?
No. The AGPLv3 does not consider viewing a website to count as “distributing”, so you are not required to share the code.
If you have a question not answered here, please consult your lawyer as we cannot and will not offer legal advice.
For general questions about Spree licensing, please contact us through the Spree website.
Summary
Spree Commerce is transitioning to the AGPL-3.0 license starting from version 4.10, while maintaining BSD-3-Clause for pre-existing contributions. This change ensures that Spree remains free and open-source for most users while protecting the community’s interests.
The new license requires that modifications, whenever used to start a SaaS business or otherwise distributed (sold) over a network, be shared back. A commercial license alternative is also available for businesses not willing to share their SaaS source code.
This dual-licensing approach aims to balance open-source principles with project sustainability, fostering a collaborative ecosystem while providing options for various business needs.
We’d love to hear from you through Spree slack: https://slack.spreecommerce.org/
