Harper Licensing FAQs

Why is Harper open sourcing its code?

Harper was built for the Node.js community and for JavaScript developers who value simplicity, flexibility, and speed. From day one our goal has been to create technology that helps developers do their best work without unnecessary complexity. Open sourcing Harper is our way of giving back to the community that has supported us. We believe innovation grows fastest when ideas are shared openly, and by opening our code, we’re inviting developers everywhere to learn from it, build on top of it, and help shape what comes next.

What is the Apache 2.0 License?

The Apache 2.0 License is one of the most widely adopted open source licenses. It gives developers a high degree of freedom. You can use the code in your personal projects, in commercial applications, or even as the foundation for a new product. You can modify it, share it, and redistribute it without needing to pay royalties. For Harper, Apache 2.0 is the way we ensure the core of the project is truly open, encouraging broad adoption and innovation.

Which parts of Harper are open source?

At launch, Harper open source projects include the Harper Core repo along with a number of related plugins, components, examples, and templates. These are licensed under Apache 2.0 and form the foundation of Harper. Additional plugins, components, and tooling will continue to be released over time.

In addition, some Harper technologies will be made available in the future under source available licenses. These allow developers to view and learn from the code, with different terms of use compared to Apache 2.0. Details about specific source available projects will be shared as they become available. To follow along with future open source and source available releases, stay tuned to our community space and social channels for updates. We aim to ensure that Harper is a useful product even without these elements, but applying limited licenses to these elements will help us fund further development of Harper.

What is permitted and required overall?

Permitted

• Use Harper open source projects (including the harper core repo on GitHub) in personal, commercial, or enterprise projects without royalties.
• Modify and redistribute the harper core repo and other open source projects freely, provided attribution and license text are included.
• Build derivative works, contribute improvements, and share them back with the community.
• Embed Harper open source code into larger products or services.

Conditions

• You must include proper attribution and preserve the Apache 2.0 license text.

Examples by user type

Individual developers

• Experiment and learn with Harper open source projects.
• Use them in personal or production apps, games, or tools.
• Modify the source to meet specific needs.
• Contribute bug fixes or enhancements back upstream.
• Distribute apps that embed or rely on Harper open source projects, including commercial apps.
  
  

Startups and companies

• Integrate Harper open source projects into commercial products, infrastructure, or services.
• Extend Harper without royalties or hidden obligations.
• Distribute applications that include Harper components, provided license terms are followed.
• Contribute improvements upstream and benefit from shared innovation.
  
  

Service providers

• May include Harper open source code in SaaS products.
• Must respect all attribution and licensing conditions.

If I want to contribute code, how are my contributions licensed?

Contributions to our open source code are welcome and licensed under the same license as the project they’re submitted to (for example, Apache 2.0 for our open source repos). Once accepted, contributions become part of the project and are distributed under that license.

How can I make the most of Harper?

• Derivative works: Open source code can be freely forked, modified, and commercialized, provided attribution and license text are included.
  
  
• Distribution: Harper repositories and documentation clearly include license information so developers know exactly what rights apply.
  
  
• Commercial use: Harper open source projects can be embedded in commercial products with no royalties.

Will other parts of Harper be made open source?

Yes. While our initial open source projects are licensed under Apache 2.0, we also plan to release other parts of Harper’s stack under source available licenses (for example, Elastic License 2.0). These projects will allow users to view and learn from the source code, with different terms of use compared to Apache 2.0.

How can I learn more about future licensing updates?

As new projects are released under open source or source available licenses, we’ll update this FAQ. In the meantime, if you have questions, reach out to us at opensource@harperdb.io.

Is this FAQ considered legal advice?

No. This FAQ is provided for general informational purposes only and is not legal advice. For guidance on how the licenses apply to specific situations, consult a qualified attorney.

Where can I read the full text of the Apache 2.0  License?

The complete license texts are available online: Apache License 2.0

It will also be included alongside respective Harper source code repositories and distributions.

Who do I contact for legal or enterprise licensing questions?

For legal or enterprise licensing questions, please contact Harper at opensource@harperdb.io

‍