Jitterbit License FAQ
Jitterbit Community Edition is available under the open source Jitterbit Public License (JPL). Our supported product offerings, including Jitterbit Enterprise and Jitterbit Enterprise MX are available under separate commercial licenses. To learn more about our commercial licenses, please contact sales.
- Where can I view the Jitterbit Public License?
- What open source license does Jitterbit use?
- I am an end-user, what does this Open Source License mean to me?
- I am a developer, what am I allowed to do with code covered by the license?
- What am I not allowed to do with the code?
- Can I sell new Integration modules that I create?
- Do I own the copyright to code I write?
- What products are covered by the license?
Where can I view the Jitterbit Public License?
The license is included with the installation of Jitterbit. It can also be viewed online here.
What open source license does Jitterbit use?
Jitterbit uses an amended version of the Mozilla Public License (MPL) v1.1. Jitterbit has modified a few items and released our product under the Jitterbit Public License (JPL). The JPL covers all source code in the Jitterbit Open Source project.
I am an end-user, what does this Open Source License mean to me?
Open Source software provides you with a number of benefits, including:
- freely available source code
- supported software in “worst-case” scenarios – no escrow or costs to obtain the source code
- a large community familiar with the code
- the ability to more tightly integrate your infrastructure with the Jitterbit product.
I am a developer, what am I allowed to do with code covered by the license?
We want developers to use and adapt the Jitterbit product. The JPL allows you to:
- Run Jitterbit
- Fix bugs
- Build complementary programs leveraging our APIs
- Freely distribute the license-covered code
- Share contributions with the community
- Sell new modules that you create under a license if they are original, and not derived works.
What am I not allowed to do with the code?
- Restrict access to derived works – if you write code modifications they must be freely available to the community.
- Remove copyright notices from the source code
- Remove mentions of Jitterbit from the product/code
Can I sell new Integration modules that I create?
Only if your module contains no modified source code. In other words, your module must add new source files to the Jitterbit product without modifying any original file in the licensed-source code. This includes:
- Any code modifications
- Including bug fixes.
- Adding or removing fields.
- Modifying API's.
- Modifying existing code to add a new API.
Do I own the copyright to code I write?
Yes. You own the copyright to any code that you write, whether derived or original However, if you modify code covered
by the JPL (i.e. create a derived work), your code is subject to the same grants and restrictions of the JPL license. Despite your copyright, you can not sell derived code and must make it publicly available.
What products are covered by the license?
All Jitterbit Open Source products on the Jitterbit web site and as projects on our SourceForge web site are covered by the Jitterbit Public license.
