-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathLICENSE
More file actions
135 lines (108 loc) · 5.46 KB
/
Copy pathLICENSE
File metadata and controls
135 lines (108 loc) · 5.46 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
Cubecloud Agent Desktop �Dual License Notice
=============================================
Copyright (c) 2026 Cubecloud Contributors
This product is a Cubecloud-branded successor of the hermes-desktop
codebase. The original `hermes-desktop` framework code is the only
upstream source code in this repository; everything else was
rebuilt or rewritten by the Cubecloud Contributors. The licensing
posture reflects that two-tier provenance:
1. **Cubecloud-original work** (the rebuilt renderer, the
Cubecloud state layer, the V2.3 modules �see
`BRANDING_AND_LICENSE.md` §"V2.4 transitions landed" for
the per-path list) is dual-licensed under your choice of:
a. **GNU Affero General Public License, version 3 or later**
(AGPL-3.0-or-later) �primary. The full text is
vendored at `licenses/AGPL-3.0.txt` and is also
available at <https://www.gnu.org/licenses/agpl-3.0.html>.
AGPL-3.0 is the strong copyleft that ensures
network-server modifications remain open.
b. **Apache License, version 2.0** (Apache-2.0) �
supporting. The full text is vendored at
`licenses/Apache-2.0.txt` and is also available at
<https://www.apache.org/licenses/LICENSE-2.0>. Apache-2.0
is offered for compatibility with Apache-ecosystem
downstream consumers (notably enterprise Java /
Kotlin / Go / Rust stacks that have an Apache-2.0
house license).
c. **MIT License** (MIT) �supporting. The full text is
vendored at `licenses/MIT.txt` and is also available
at <https://opensource.org/licenses/MIT>. MIT is offered
for downstream consumers who need a maximally permissive
license (notably small plugins, examples, and forks
that rebrand �see `docs/legal/TRADEMARK_POLICY.md`).
You may apply any one of the three to Cubecloud-original
work at your option. The three licenses are alternatives,
not additive: you pick the one under which you receive the
work. If you modify the work and convey it on a network
server, AGPL-3.0 §13 (the "remote network interaction"
clause) requires you to provide the Corresponding Source
to the users of that server.
2. **Inherited `hermes-desktop` framework code** (the
Electron main / preload / renderer framework that hosts
the Cubecloud rebuilds) is hard-MIT and remains under the
upstream MIT terms. We cannot retroactively restrict MIT
code, and we have no plan to. See `licenses/MIT.txt` and
the original `hermes-desktop` repository for the upstream
copyright line. The full per-path breakdown of which
files fall into category 1 vs category 2 lives in
`BRANDING_AND_LICENSE.md`.
The full text of all three licenses is kept under `licenses/`
so that downstream redistributors can include them without
having to fetch them from the network.
---
Scope of this LICENSE file
--------------------------
This file grants rights in the source code in this repository.
It does NOT grant any rights to:
- The **Cubecloud name, logotype, wordmark, mark SVGs in
`build/branding/`, splash assets, app icon set, or any
other Cubecloud trademark**. See
`docs/legal/TRADEMARK_POLICY.md`. The trademarks are not
MIT, not Apache-2.0, not AGPL-3.0; they are reserved.
- **Hosted service tiers** offered by the Cubecloud
Contributors or their successors. See
`docs/legal/CUBECLOUD-EULA.md`.
- **Paid features, premium modules, and managed services**.
See `docs/legal/PAID_SERVICES_TERMS.md` and
`docs/legal/COMMERCIAL_LICENSE.md` (the latter describes
the commercial-relicensing path for AGPL-3.0 §13
network-clause compliance, where relevant).
- **Third-party dependencies** listed in `NOTICE`. Each
dependency is governed by its own license.
---
How to choose a license for downstream use
------------------------------------------
- **If you are a private, non-network-server end user**: any
of the three licenses works. AGPL-3.0 obligations only
trigger when you convey or run a modified version on a
network server (per §13).
- **If you run a hosted service using modified Cubecloud
code**: AGPL-3.0 §13 requires you to provide the
Corresponding Source to your users. Apache-2.0 or MIT do
not impose that requirement. If you cannot or will not
open-source your modifications, contact us about a
commercial license at the address in
`docs/legal/COMMERCIAL_LICENSE.md`.
- **If you distribute a fork or a plugin that incorporates
Cubecloud code**: pick the license that matches your
project's overall license posture. If you keep the
Cubecloud marks, see `docs/legal/TRADEMARK_POLICY.md`
for the brand-use rules.
---
Trademark and license interaction
---------------------------------
The MIT, Apache-2.0, and AGPL-3.0 licenses all include
language (MIT §, Apache-2.0 §6, AGPL-3.0 §7(e)) that
preserves trademark rights of the licensor. None of the
three licenses grants any right to the Cubecloud trademarks
by implication. See `docs/legal/TRADEMARK_POLICY.md` for the
complete brand-use rules.
---
No legal advice
---------------
This file is published in good faith to make the license
posture of `agent-desktop` explicit. It is not legal
advice. If you have questions about how the AGPL-3.0
network-clause applies to your specific deployment, or
about the Apache-2.0 patent-retaliation clause, or about
the MIT permission notice, consult counsel.