Files
dsh_shenxian/COMMERCIAL-LICENSE.md
T
admin 5ec99ce227
build / build-and-scan (push) Canceled after 0s
chore: 文档库全量重新入库(2026-10-20)
2026-10-20 15:05:55 +08:00

33 lines
1.7 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
> **English (primary, this file)** | **[中文文档](COMMERCIAL-LICENSE.zh-CN.md)**
[← Back to README](README.md)
# Commercial license
This project is **dual-licensed**: [GNU AGPL-3.0](LICENSE) is the default track, and the commercial track described here is an alternative to it. The two are **parallel choices** — buying the commercial track is not a requirement imposed on anyone using the AGPL track.
## Which track applies
| Your use | Track |
|---|---|
| Personal use, study, research, evaluation | 1 — AGPL-3.0 |
| Internal deployment of an unmodified build | 1 — AGPL-3.0 |
| Modified build, deployed or distributed with its source disclosed | 1 — AGPL-3.0 |
| Closed-source hosted service offered to others | 2 — commercial |
| Embedded in a proprietary product that you ship | 2 — commercial |
Commercial use itself is allowed under **both** tracks. What distinguishes them is the source-disclosure obligation: AGPL-3.0 §13 requires that users of your modified build — including users of a network service — receive the corresponding source.
## What the commercial track provides
- The same rights AGPL-3.0 grants you, **without** the §13 source-disclosure obligation.
- Scope, term, deployment model and fee are set in the agreement both sides sign. **This document is an invitation to negotiate; it is not itself a license grant.**
## How to obtain one
Write to **[email protected]** stating the intended use, the deployment model and the expected scale.
## Third-party components
Upstream DeepSeek Harness is licensed under the MIT License. This project does **not** include or distribute it — it is invoked at runtime as a separate process — so its terms are unaffected by either track above.