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

# Integration with Remnawave

> How Axottle works on top of the Remnawave panel: connections, sync and backups.

Axottle is the **control layer above the Remnawave** external panel. It does not replace the Remnawave panel: Axottle connects to an already running instance via its HTTP API and takes on higher-level management scenarios.

\[!NOTE] For whom: Axottle Administrator Required Rights: Axottle Panel Administrative Session; Remnawave Panel API Token. is required to connect

## What does integration do?

* **Stores the local data model (snapshots) of** users, nodes, hosts and config profiles of the Remnawave panel. Snapshots are updated during synchronization and are read-only.
* **Manages the** panel: within the framework of high-level scenarios, Axottle creates and updates nodes, hosts, config profiles, internal squads and subscription templates on the panel.
* **Creates a service team for health checks**: after successful synchronization, Axottle automatically prepares the system team `axottle-health` for internal health tests.
* **Generates change events**: each time Axottle synchronizes the new state of the panel with the previous one and publishes normalized events – change of node status, appearance or deletion of the host and config profile.
* **Works with runtime Remnawave**: finds Compose project and PostgreSQL, shows metrics and logs of containers, runs base backups and check or restore operations.

To one Axottle panel you can connect **several instances of Remnawave at the same time**: each connection is a separate record, in the administrator interface they are shown by tabs.

## How basic entities are related

| Essence | Where | Lives Who is the Source of Truth | |
| - | - | - | - |
| Users, nodes, hosts, config profiles | Remnawave | Remnawave panel; Axottle stores snapshots | |
| Connections, snapshots, events | Axottle | Axottle | |
| Runtime, metrics, logs and backups of the Remnawave | Axottle database, next to the | Axottle connection, performs operations on the selected Remnawave | host |

## Where operations are performed

Each connection has one runtime performer, which collects metrics and logs, detects Compose and PostgreSQL, and then performs backups, archive checks and recovery.

\| Topology | When to choose | How | works
\|---|---|---|
\| **Axottle server** | Remnawave runs on the same server as the Axottle panel | The panel itself accesses Docker and performs operations locally. |
\| **A separate server** | Remnawave is located on another host | In the panel, a one-time Axottle Agent installation command is created. Once connected, this agent serves only the selected Remnawave connection. |
\| **Together with RemnaNode** | Remnawave and RemnaNode work on the same server | Select an existing node with an installed agent. The second agent on this server is not needed: one agent serves both roles and transmits common host metrics. |

When you change the topology, Axottle changes the binding of the artist. The tasks of the old artist are no longer given to him, but before you start a backup or read the logs, you need to rediscover the stack.

> [!NOTE]
>
> The panel updates the image itself: bypasses the connections once every 10 minutes and synchronizes the attached connection before applying the circuit. Manual start remains when the result is needed immediately, see. [Synchronization](https://docs.axottle.com/en/remnawave/synchronization.md).

## Remnawave versions

Axottle works with both 2.x and 3.x branches: the version of the panel is determined by its response, and the client adjusts itself. The installer puts a third major, moving from someone else's panel carries the version of the original. You can update the Remnawave panel from Axottle, see [Update Remnawave](https://docs.axottle.com/en/remnawave/updates.md).

## Sections

New management scenarios: [External PostgreSQL](https://docs.axottle.com/en/remnawave/external-database.md),
[moves the](https://docs.axottle.com/en/remnawave/migration.md) panel and
[Import an existing route to Flow](https://docs.axottle.com/en/connection-units/remnawave-import.md).
Preparing a database or schema does not switch traffic: data transfer and Apply
separate actions after the inspection.

> [card] [Connections](https://docs.axottle.com/en/remnawave/connections.md)
>
> Remnawave panel connection: URL, token, artist selection, stack detection and statuses.

> [card] [Synchronization](https://docs.axottle.com/en/remnawave/synchronization.md)
>
> What and how is synchronized, snapshot approach, results and events of changes.

> [card] [Back-up copies](https://docs.axottle.com/en/remnawave/backups.md)
>
> PostgreSQL backup profiles, access verification, integrity, and confirmation recovery.

> [card] [Remnawave Update](https://docs.axottle.com/en/remnawave/updates.md)
>
> Update of the panel from Axottle: working backup requirement, version selection and rollback.

> [card] [Troubleshooting](https://docs.axottle.com/en/remnawave/troubleshooting.md)
>
> Token Errors, Network/TLS, Partial Synchronization and Diagnostic Procedure.

## Related pages

* [The first](https://docs.axottle.com/en/getting-started/first-connection.md) connection is a quick start from scratch.

The availability of functions depends on the installed assembly.


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