> ## 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.

# Glossary

> Key terms Axottle: panel, Flow, node, agent, Axosun, self-heal and others.

Axottle's Uniform Dictionary of Terms. Use it as a reference when reading the rest of the sections.

## Product and components

| Term | Value |
| - | - |
| **Axottle** | Control layer over Remnawave infrastructure: panel, API and agents. Automates node operation, routing, CDN, monitoring and recovery. |
| **Panel** | Administrator Web interface Axottle. |
| **Server (panel-server)** | Axottle's core process: Serves APIs, dashboards, schedulers, and agent communication, and runs as a system service. |
| **Agent (axottle-agent)** | Service installed on the node. Sends metrics and heartbeat, performs a fixed set of panel operations. Voluntary commands are impossible. |
| **Axosun** | Built-in AI panel assistant: diagnostics, reports, incidents and actions from a fixed directory. Works with confirmation of actions and hiding sensitive data. |

## The infrastructure

| Term | Value |
| - | - |
| **Node (node)** | Server, which Axottle manages through an agent. Has a status life cycle and several independent state axes (traffic, control mode, source). |
| **Group Node** | User association of nodes for convenient work and appointments. |
| **Remnawave** | The outer panel to which Axottle connects as a control layer remains the source of truth for users, nodes and profiles. |
| **Provider** | Hosting provider whose account connects to view regions and tariffs. |

## Traffic configuration

| Term | Value |
| - | - |
| **Flow (config)** | Traffic Path configuration with draft, applied versions and independent health checks. Previously Connection Unit; `connection-units` technical paths and `connection_units.*` rights remain. |
| **Flow Studio** | Infrastructure → Configuration Workspace: review, configs, transit pools and REALITY targets. |
| **Transit pool** | Reused transit graph with participants, policies and output "Continue flow." |
| **Pool Node** | Transit block of regular Flow referring to the pool. Working Flow pins the pool snapshot to a new application. |
| **Flow Guard** | Flow Recovery Plans: Manual launch with confirmation or automatic actions on a pre-saved policy. |
| **Entry block** | Flow element describing the traffic entry point on the node. |
| **CDN-block** | An element of the input node Flow, which, when used, triggers automatic allocation of the domain, DNS, TLS and CDN resource. |
| **Self-steal** | Public storefront stub on the node, increasing the invisibility of infrastructure. Configured through templates and deployments. |
| **Geo-assets** | Version-by-checksum geodatasets assigned to nodes through profiles. |

## Operation and reliability

| Term | Value |
| - | - |
| **Health (health)** | Node, route and dependency monitoring system. Converts signals to status and severity. |
| **Self-heal (self-healing)** | Automatic failure recovery within specified constraints and with escalation to the operator. |
| **Node suppression (suppression)** | Temporary exclusion of the node from routing in case of problems, followed by recovery. |
| **Egress Guard** | Control of dangerous outbound ports on nodes (e.g. blocking of spam relay mail). |
| **AbuseProtect** | Detection of Abnormal Subscription Use and Time Band Restrictions (QoS) without Destructive Actions. |
| **QoS-override** | Temporary band restriction for a specific subscription. Automatically removed at expiry. |

## Access and security

| Term | Value |
| - | - |
| **Session** | The user experience in the panel after logging in. Ends on exit or re-authorization. |
| **Secret Storage** | Secure storage of keys and disk-encrypted panel tokens. |
| **Integration-token** | Token with the prefix `axt_` for internal integrations. Showed once when created. |
| **Enrollment-token** | One-time token with a limited lifespan for registration of a node / agent. |
| **Audit-log** | Secure log of administrator and system actions. |
| **Journal (journal)** | Ribbon of health events and nodes. Distinguished from audit log: shows incidents and events, not the actions of administrators. |


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