Update README.md
This commit is contained in:
82
README.md
82
README.md
@@ -1,3 +1,81 @@
|
|||||||
# .profile
|
# GitCaddy Suite — Licensing Overview
|
||||||
|
|
||||||
Organization profile
|
The GitCaddy Suite is licensed under a deliberate open-core model designed to
|
||||||
|
maximize developer adoption while sustaining long-term development.
|
||||||
|
|
||||||
|
Different components of the suite are licensed under different terms, as
|
||||||
|
outlined below.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Licensing Summary
|
||||||
|
|
||||||
|
| Component | License | Notes |
|
||||||
|
|------------------------|---------|-------|
|
||||||
|
| GitCaddy Desktop | MIT | Fully open-source client |
|
||||||
|
| GitCaddy Server (Core) | MIT | Fork of Gitea; core hosting only |
|
||||||
|
| GitCaddy Runner | MIT | CI runner |
|
||||||
|
| Addon Framework | MIT | SDK and templates |
|
||||||
|
| MCP Server | MIT | AI integration bridge |
|
||||||
|
| GitCaddy Vault | BSL 1.1 | Secrets management |
|
||||||
|
| AI Context APIs | BSL 1.1 | Repo analysis, navigation, hints |
|
||||||
|
| Enterprise Features | BSL 1.1 | SSO, audit logs, compliance |
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## MIT-Licensed Components
|
||||||
|
|
||||||
|
MIT-licensed components are free to use, modify, and redistribute for any
|
||||||
|
purpose, including commercial use, subject only to the terms of the MIT License.
|
||||||
|
|
||||||
|
These components are intended to encourage adoption, ecosystem growth, and
|
||||||
|
self-hosted deployment.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Business Source License (BSL 1.1) Components
|
||||||
|
|
||||||
|
Certain components are licensed under the Business Source License 1.1 (BSL):
|
||||||
|
|
||||||
|
- GitCaddy Vault
|
||||||
|
- AI Context APIs
|
||||||
|
- Enterprise administration features
|
||||||
|
|
||||||
|
### Additional Use Grant
|
||||||
|
|
||||||
|
You may use BSL-licensed components:
|
||||||
|
- For non-production purposes without restriction
|
||||||
|
- In production with up to **5 users** without charge
|
||||||
|
|
||||||
|
Use beyond this grant requires a commercial license.
|
||||||
|
|
||||||
|
### Change License
|
||||||
|
|
||||||
|
Each BSL-licensed component will automatically convert to:
|
||||||
|
|
||||||
|
**Apache License, Version 2.0**
|
||||||
|
|
||||||
|
On the applicable Change Date defined in its LICENSE file.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Commercial Use & Hosting
|
||||||
|
|
||||||
|
Operating GitCaddy BSL-licensed components as part of a hosted or managed
|
||||||
|
service, or beyond the Additional Use Grant, requires a commercial license.
|
||||||
|
|
||||||
|
Commercial licenses unlock additional features and remove usage limits.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Contributions
|
||||||
|
|
||||||
|
- MIT components accept contributions under the MIT License.
|
||||||
|
- BSL components require acceptance of a Contributor License Agreement (CLA).
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Questions
|
||||||
|
|
||||||
|
For licensing inquiries, commercial terms, or compliance questions:
|
||||||
|
licensing@gitcaddy.com
|
||||||
|
|||||||
Reference in New Issue
Block a user