> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Architecture

> How the Axottle panel, nodes, Flow, CDN, health, and Remnawave work together.

Axottle consists of the panel, agents on nodes, and an integration with Remnawave. The panel is the control center: you use it to define connection schemes, and the agents apply them on nodes. This page explains how the components interact.

> [!NOTE]
>
> For administrators and SREs who need to understand control and data flows.

## Components

| Component | Role |
| - | - |
| **Panel** | Web interface and REST API. Stores configurations, schedules checks, manages nodes, and connects to Remnawave. |
| **Agent** | Service on a node. Sends metrics and heartbeats and performs a fixed set of panel operations, including component installation, configuration application, and checks. |
| **Remnawave** | External panel and source of truth for users, nodes, hosts, and profiles. Axottle manages it as a control layer. |
| **Reverse proxy** | Publishes the panel under a domain with TLS. Deployed by the installer. |

## Control flow

**1. The operator defines a scheme**

Build a Flow in the panel: entry points, routes, and, if needed, CDN and masking.

**2. The panel compiles and validates it**

The scheme is compiled and passes linting and preflight checks. Critical findings block application.

**3. Apply to nodes**

The panel assigns tasks to agents on the target nodes. A change is considered applied only after the agent confirms it.

**4. Verification and monitoring**

The health system continuously checks nodes and routes and combines signals into statuses.

## Data flows

* **Panel ↔ agents.** Agents connect to the panel's public address and authenticate with node tokens. The reverse proxy protects the connection with TLS. Agents regularly send heartbeats and metrics, fetch tasks, and report results.
* **Panel ↔ Remnawave.** The panel connects to the Remnawave API, synchronizes local snapshots of users, nodes, hosts, and profiles, and makes changes in Remnawave. Synchronization is started manually; Remnawave remains the source of truth.

## Feature areas

> [card] [Flow](https://docs.axottle.com/en/connection-units/overview.md)
>
> Flow Studio: configurations, transit pools, and traffic routing.

> [card] [CDN and DNS](https://docs.axottle.com/en/cdn/overview.md)
>
> Automatic allocation of a domain, DNS, TLS, and CDN resource for entry nodes.

> [card] [Health and self-healing](https://docs.axottle.com/en/health/overview.md)
>
> Monitoring, manual plans, and authorized automatic recovery with Flow Guard.

> [card] [Security](https://docs.axottle.com/en/security/overview.md)
>
> Node hardening, port checks, masking, and audit.

> [card] [AbuseProtect](https://docs.axottle.com/en/abuse/overview.md)
>
> Detection of abnormal subscription use and temporary restrictions.

> [card] [Axosun](https://docs.axottle.com/en/axosun/overview.md)
>
> An operations assistant spanning the subsystems.

## Deployment

The panel is a single server component with a built-in web interface. It runs as a system service and stores data in PostgreSQL. It is published under a domain through a reverse proxy with TLS. Nodes are separate Linux servers with the agent installed. See [Requirements](https://docs.axottle.com/en/getting-started/requirements.md) and [Agent installation](https://docs.axottle.com/en/nodes/installation.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.