| title | Licensing Model |
|---|---|
| description | How Grounds licenses core code, libraries, tooling, documentation, and assets |
Use this page when you need a quick overview of how Grounds licenses code, tooling, documentation, and assets.
Grounds uses different licenses for different parts of the ecosystem so you can understand what you may reuse, modify, or redistribute.
| Area | License | What it covers |
|---|---|---|
| Core platform | AGPL-3.0 | Backend services, gameplay logic, proxies, and other production platform code |
| Libraries, APIs, and protocols | Apache-2.0 | Reusable libraries, shared utilities, APIs, and protocol definitions |
| Developer tooling | Apache-2.0 | CLI tools, Gradle plugins, development helpers, and similar infrastructure |
| Documentation | MIT | Documentation content and written guidance |
| Assets | CC BY-NC-SA 4.0 or custom | Logos, textures, lore, music, and other creative assets |
- AGPL-3.0 keeps the core platform open, including hosted-service modifications.
- Apache-2.0 makes reusable libraries and tooling easier to adopt in other projects.
- MIT lets you copy and reuse the documentation without extra restrictions.
- Asset licenses stay separate so Grounds can protect its visual identity and other creative work.