> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/functionality/highlight-architecture.md).

# Highlight Architecture

## Overview

This page provides a high level overview with graphics showing how Highlight uses agents to collect data from private, public and hybrid networks.

## Private networks

Pairs of Highlight agents are used to collect information from devices on a private network, then compress it, encrypt it and pass it back to the Highlight platform.

The Highlight Agent software is free and installed on your own hardware. Refer to the [Specifications for minimum server requirements](https://help.highlight.net/functionality/server-specifications.md).

## Public networks

Pairs of Highlight agents in the cloud are used to collect information from devices on the public network, then pass it back to the Highlight platform.

## Hybrid networks

A combination of the previous two approaches is used for gathering data from a hybrid network.

The Highlight Agent software is free and installed on your own hardware. Refer to the [Specifications for minimum server requirements](https://help.highlight.net/functionality/server-specifications.md).

## Related

* [How to install an agent](https://help.highlight.net/device-setup/agent-installation.md)


---

# 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://help.highlight.net/functionality/highlight-architecture.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.
