> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/related-information/license.md).

# License

CrossWatch license text (MIT-based) with additional commercial use restrictions for paid and hosted offerings.

CrossWatch License (MIT-based with Commercial Restriction)

```
Copyright (c) 2025-2026 Cenodude
https://github.com/cenodude/CrossWatch

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, and sublicense, and to permit
persons to whom the Software is furnished to do so, subject to the conditions
below.

The above copyright notice and this permission notice (including the additional
terms below) shall be included in all copies or substantial portions of the
Software.

ADDITIONAL TERMS - COMMERCIAL USE RESTRICTION (INCLUDING HOSTED CONTAINERS)

1. Commercial use requires permission
   Notwithstanding the permission grant above, you may not use, distribute,
   sublicense, or make the Software available as part of any commercial product
   or service where end users are required to pay (including subscriptions,
   licenses, paywalls, or paid features) in order to access or use the Software,
   unless you have explicit permission from the copyright holder.

Permission requests: contact on Discord: cenodude#2185

2. Hosted containers / container images (cost-only allowance)
   If you provide the Software via a container image (such as Docker/OCI) and/or as a
   hosted container deployment running the Software, you may charge ONLY the direct,
   pass-through costs for hosting/infrastructure (such as compute, storage, bandwidth).

You may NOT charge for CrossWatch itself, bundle it into a paid plan, include it
as part of a subscription value proposition, add markup for the Software, or
otherwise price the service in a way that implies CrossWatch is included in the
price beyond hosting cost recovery.

This allowance does not remove the requirement to include the copyright notice
and this license text in all copies or substantial portions of the Software.

Rationale (informational; non-binding)
Life is expensive enough, and I built this application with love for the community.
CrossWatch will be free-for-ever.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
```


---

# 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://wiki.crosswatch.app/related-information/license.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.
