> For the complete documentation index, see [llms.txt](https://docs.hedge.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.video/general/licenses/network-requirements.md).

# Network Requirements

Most Hedge apps use and connect to [LimeLM](https://wyday.com) ([wyday.com](https://wyday.com)) for license management, which also serves as the backbone of the [Hedge License Manager](https://docs.hedge.video/general/licenses/the-license-manager.md).

When something unexpected happens, we use [Sentry](https://sentry.io/) for anonymized crash reporting. You'll be given the option to `Send` your report, we don't assume you will.

When you contact support via an in-app form, we bundle the relevant logs for investigative and diagnostic purposes. These are delivered to our team by Google's mail servers.\
\
If you have a firewall in place, to activate your license and use other services around our apps, make sure to allow these domains to be accessed through port 443:

* \*.wyday.com
* \*.sentry.io
* \*.hedge.video
* \*.hedge.co

If you can't do wildcards in your firewall, specify...

* account.hedge.video
* updates.hedge.video
* connect.hedge.video

and...

* account.hedge.co
* updates.hedge.co
* connect.hedge.co

IPs change all the time, so we can't specify those.


---

# 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.hedge.video/general/licenses/network-requirements.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.
