GPL obligations when you distribute a bundle
This page is for bundlers and their legal and product teams. It summarizes what the license of Exponential's code asks when you hand copies to others. It is not legal advice. The license texts decide, and your counsel decides how they apply to your bundle.
Contents
- The license of the code
- What you may do
- What you must do when you distribute
- How it applies to each kind of bundle
- Your own code in the bundle
- Checklist
The license of the code
| Item | Statement | Where |
|---|---|---|
| License | GNU General Public License, version 2, "or (at your option) any later version" | COPYRIGHT.md, LICENSE.md (the GPL v2 text) |
| Composer license field | "license": "GPL-2.0-or-later" | composer.json |
| Copyright | "Copyright (C) 1998 - 2026 Exponential Foundation and 7x. All rights reserved." and "Copyright (C) 1999 - 2014 eZ Systems AS" | COPYRIGHT.md, LICENSE |
| Contributions | "By contributing, you agree that your contributions will be licensed under the GNU General Public License, version 2.0 or later" | CONTRIBUTING.md, quoted on Licensing for partners |
| Extensions | each its own; the project's are GPL | each extension's extension.xml, ezinfo.php and license file |
What you may do
- Run, study, change and combine Exponential for any purpose.
- Distribute copies, changed or not, as part of a bundle.
- Charge for the bundle, for distribution, for installation, support, hosting and your own work. "Using Exponential under the terms of the GNU GPL is free of charge" (README); what your customers pay you for is the work and the service, never a license to the software (Licensing for partners).
What you must do when you distribute
From Licensing for partners and Distribution partners:
- Pass on the license and the notices. Include the license texts (
LICENSE,LICENSE.md,COPYRIGHT.md) and keep every copyright notice in the files. - Provide the source code, including your modifications, as the GPL requires. For GPL version 2, section 3 describes the ways: the source with the binaries, or a written offer, valid for at least three years, to provide it. Read the section itself before you choose.
- Add no restrictions that the GPL forbids: no clause in your terms that takes away the recipients' right to copy, change and share the GPL parts.
- Keep the documentation's notices when you ship the documentation (GFDL; see Documentation to ship).
How it applies to each kind of bundle
| Bundle | Practical way to meet the source duty | Notes |
|---|---|---|
| Container image | publish the build files and the exact sources (tag, lock file, your extensions) next to the image | an image is a distribution of every GPL component inside it |
| Server or VM image | the same; also the sources of GPL operating system parts, as their own licenses require | your OS vendor's terms apply to the OS |
| Panel installer that downloads Exponential | the recipient gets the code from the project; your installer scripts are your own code | ask counsel who distributes what |
| Distribution package | the source package of your distribution | follow the distribution's policy |
| Starter kit repository | the repository is the source | add your license file |
| Appliance | source for the GPL software on the box, and no locks that stop recipients from exercising their rights | ask counsel; appliances are where most mistakes happen |
Your own code in the bundle
| Your part | Question to answer with counsel |
|---|---|
| An extension that uses Exponential's APIs | Must it be GPL-compatible when distributed with Exponential? The partner pages advise: "If they are distributed with or as part of GPL code, they must be GPL compatible; ask your counsel" (Distribution partners) |
| A theme or site package | Which license for templates, styles, images and content? See License fields in your packages |
| Separate programs in the image (a monitoring agent, a panel) | They keep their own licenses; list them (Third-party components) |
Checklist
- To do:
LICENSE,LICENSE.mdandCOPYRIGHT.mdare in the bundle, unchanged. - To do: Copyright headers in the files are intact.
- To do: The corresponding source (kernel tag,
composer.lock, your extensions, your changes, build files) is published or offered, and the release notes say where. - To do: Every third-party component and its license is listed.
- To do: Your terms add no restriction on the GPL parts.
- To do: The documentation you ship keeps its GFDL notices and license text.
- To do: Counsel has reviewed the bundle's licensing once, and again when its shape changes.
Related pages
- License texts and notices to ship
- Licensing for partners, Distribution partners and resellers
- Licensing for hosts, Licensing questions
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.
Copyright and copyleft
Since 29 October 2026 the copyright of Exponential is held by the Exponential Foundation and 7x together, the Foundation named first: "Exponential Copyright © 1998-2026 Exponential Foundation and 7x", in files "Copyright (C) 1998 - 2026 Exponential Foundation and 7x. All rights reserved." Who holds it and why, what the GPL lets you do, the third-party notices that stay and how to write the notice in new files and extensions: Copyright and copyleft.