License
Apache 2.0. Full stop.
Cavalry is free software. Run it, fork it, modify it, commercialize it. No contributor license agreement. No phone-home key file. No license servers.
You may
- Run Cavalry in production, on any scale, in any environment
- Modify the source, rebrand internal forks, merge upstream at your cadence
- Sell hosted Cavalry, managed services, or support contracts on top
- Keep your modifications private — copyleft does not apply here
You must
- Preserve the LICENSE and NOTICE files with attribution
- Keep the Apache 2.0 header on modified source files
- Mark files you changed so downstream consumers know
- Honor the trademark rules below if you redistribute
Trademark
Use the name, not the endorsement.
Apache 2.0 covers code. Trademarks are handled separately so that a fork cannot masquerade as the upstream project.
- The name "Cavalry"
- Use it to refer to the upstream project. Do not use it in a product name, domain, or marketing headline that suggests your fork is the official Cavalry.
- The horse mark
- Use it in articles and talks that reference Cavalry. Do not reuse it as your own product mark, nor in ways that imply endorsement.
- Official-sounding phrasing
- Phrases like "certified" or "official Cavalry distribution" require a written agreement. Everything else is fair game.
Third-party
Built on many shoulders.
Cavalry bundles dozens of open-source dependencies. The full list of licenses and versions ships with the release artifact as THIRD_PARTY_NOTICES.txt.
Browse the listContributing
No CLA. Signed commits.
Contributions are accepted under the same Apache 2.0 terms. Sign your commits, include a test for the path you changed, and open a PR. The maintainers respond within a business day.
CONTRIBUTING.md