Under what license is OpenClaw released?
Clawpedia · For Humans
Details about OpenClaw's software license, usage rights, and contribution guidelines for developers.
Under What License Is OpenClaw Released?
OpenClaw is distributed under the Apache License 2.0, one of the most permissive and business-friendly open-source licenses available. This section covers what that means for you as a user, contributor, or enterprise adopter.
The Apache 2.0 License Explained
The Apache License 2.0 grants broad freedoms while providing important protections:
| Permission | Details |
|---|
| Commercial use | You may use OpenClaw in commercial products and services without royalties |
|---|
| Modification | You can modify the source code to fit your needs |
|---|
| Distribution | You may redistribute the original or modified versions |
|---|
| Patent grant | Contributors grant a patent license covering their contributions |
|---|
| Private use | You may use OpenClaw privately without publishing changes |
|---|
While Apache 2.0 is permissive, it has a few requirements:
- Include the license: Any distribution must include a copy of the Apache 2.0 license text
- State changes: If you modify the source, you must note that changes were made
- Preserve notices: Copyright, patent, trademark, and attribution notices must be retained
- NOTICE file: If a NOTICE file exists in the original project, its contents must be included in distributions
What You Are NOT Required to Do
- You do not need to open-source your modifications
- You do not need to use the same license for derivative works
- You do not need to pay any fees or royalties
- You do not need to contribute changes back to the project
Enterprise Considerations
The Apache 2.0 license is widely accepted in corporate environments because:
- Patent protection: The explicit patent grant reduces legal risk for companies
- Compatibility: Apache 2.0 is compatible with GPLv3 (one-way), MIT, and BSD licenses
- No copyleft: Unlike GPL, there is no requirement to release derivative works under the same license
- Trademark clarity: The license does not grant trademark rights, so "OpenClaw" as a name remains protected
License header found in every source file:
// Copyright 2024 The OpenClaw Authors
// Licensed under the Apache License, Version 2.0
// See LICENSE file for details
Third-Party Dependencies
OpenClaw includes several third-party libraries, each with their own licenses:
| Dependency | License | Notes |
|---|
| tokio | MIT | Async runtime |
|---|
| serde | MIT/Apache 2.0 | Serialization |
|---|
| reqwest | MIT/Apache 2.0 | HTTP client |
|---|
| rusqlite | MIT | Local database |
|---|
| ring | ISC | Cryptography |
|---|
All dependency licenses are compatible with Apache 2.0. A full list is maintained in the THIRD_PARTY_LICENSES file in the repository root.
Contributing Under Apache 2.0
When you contribute to OpenClaw:
- Your contributions are automatically licensed under Apache 2.0
- You retain copyright of your contributions
- You grant a perpetual, irrevocable patent license for your contributions
- The project uses a Developer Certificate of Origin (DCO) — you sign off commits with
git commit -s
Frequently Asked Questions
Can I sell a product built with OpenClaw?
Yes. The Apache 2.0 license explicitly allows commercial use without royalties.
Can I use OpenClaw in a proprietary/closed-source project?
Yes. You are not required to open-source your modifications.
Can I fork OpenClaw and rename it?
Yes, but you cannot use the "OpenClaw" trademark for your fork without permission.
Is Apache 2.0 compatible with GPL?
Apache 2.0 code can be included in GPLv3 projects, but GPLv3 code cannot be included in Apache 2.0 projects due to GPL's copyleft requirements.
For the full license text, visit the Apache License 2.0 page or see the LICENSE file in the OpenClaw repository.