> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/kilo-mioty-service-center/license-and-trademarks.md).

# License And Trademarks

KiloCenter Community Edition license — AGPL-3.0-or-later with network-use clause — and trademark notices.

### License

KiloCenter Community Edition is licensed under the **GNU Affero General Public License v3.0 or later** (AGPL-3.0-or-later).

The full license text is available in the LICENSE file in the repository root, and at [gnu.org/licenses/agpl-3.0.html](https://www.gnu.org/licenses/agpl-3.0.html).

### What AGPL Means for Hosted Modifications

The AGPL extends GPL with a network-use clause:

* If you **distribute** KiloCenter binaries, you must provide the source under AGPL.
* If you **run a modified version as a network service**, you must make the complete corresponding source available to users of that service.
* You may link to the source or provide a direct download — the requirement is that users can obtain it.

Source code is always available at [github.com/Kiloiot/kilo-service-center](https://github.com/Kiloiot/kilo-service-center).

### Runtime Source Disclosure

The `GetReleaseInfo` gRPC RPC returns disclosure metadata at runtime, including:

* `edition` — build edition (e.g., "Community Edition")
* `license_id` — SPDX identifier (e.g., "AGPL-3.0-or-later")
* `license_url` — link to full license text
* `source_url` — link to source repository
* `documentation_url` — link to documentation
* `homepage_url` — project homepage
* `trademark_notice` — trademark statement

This information is also embedded in the web UI (login page, navigation drawer, and user menu) so users can always locate the source and license.

### Trademark Policy

KiloCenter and the KiloCenter logo are trademarks of Tim Kravchunovsky. See TRADEMARKS.md for the full trademark policy.

Community forks must not use the KiloCenter name or logo in a way that implies official affiliation or endorsement.

### Enterprise / Managed Cloud

The Enterprise edition of KiloCenter is built into Kilo Cloud and is also available as part of supported enterprise deployments under separate licensing terms. Kilo Cloud combines the MIOTY service center with the full Kilo IoT platform, including rules, dashboards, alarms, access control, and managed operations. See [KiloCenter Community vs Enterprise vs Kilo Cloud](/kilo-mioty-service-center.md#kilocenter-community-vs-enterprise-vs-kilo-cloud), or contact [Kilo IoT](https://kiloiot.io/contact/) for details.

### Legal Attribution

© 2024–2026 Tim Kravchunovsky and contributors. All rights reserved where applicable.

KiloCenter implements the MIOTY LPWAN protocol as specified by the MIOTY Alliance. MIOTY is a registered trademark of the MIOTY Alliance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kiloiot.io/kilo-mioty-service-center/license-and-trademarks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.