---
title: "Security & Licensing"
id: "1718"
type: "page"
slug: "licensing"
published_at: "2026-09-20T20:36:26+00:00"
modified_at: "2026-11-18T17:59:48+00:00"
url: "https://xedant.com/agents/multiagent/docs/licensing/"
markdown_url: "https://xedant.com/agents/multiagent/docs/licensing.md"
excerpt: "MultiAgent holds the sensitive data of your whole infrastructure: servers’ SSH keys, agent passwords, registry…"
---

# Security & Licensing

[https://xedant.com/agents/multiagent/docs/licensing/.md](https://xedant.com/agents/multiagent/docs/licensing/.md)

MultiAgent holds the sensitive data of your whole infrastructure: servers’ SSH keys, agent passwords, registry tokens and API keys. This page explains how all of it is protected, how backups are set up, and how licensing works.

## Secret encryption

Every secret is encrypted at rest with AES-256-GCM symmetric encryption. The 32-byte key lives in `/data/keys/management-secret.key` — inside the MultiAgent volume, outside the database. What is protected:

- servers’ SSH passwords and private keys (including proxy jump credentials);
- Postgres and Forgejo passwords on factories;
- image registry tokens (Registry Auth);
- agent managers’ passwords and the secret variables of models and tools;
- API keys and factory service passwords (Postgres, Forgejo, central login, backup).

The connection to a machine — address, port, login, password or key, jump host — is stored on the **server record**, not on each factory: several factories on one machine share one connection. Fix the address or the password and it takes effect for every factory of that machine at once. Secrets are write-only: the answers carry only a “set” or “not set” hint, and the password or key itself is never given back.

User sign-ins are checked with JWT tokens valid for 90 days, signed by a separate key from `/data/keys`. Every API action requires a key check; only the login page is anonymous, and the machine interface `/api/agent/*` opens with its own `X-API-Key`.

## Agent API — the machine interface

The `/api/agent/*` interface is meant for automatic calls — from agents and external systems. Every request is checked against the `X-API-Key` header: the `MULTIAGENT_HASH` environment variable stores only the key’s fingerprint (a SHA-256 hash), and the key itself is set once at install. Without the variable, the interface answers 503 and does not work at all.

Security details: `GET /api/agent` returns a catalog of every operation with descriptions; secrets can only be written — they are never given back, only “has a value” hints; there is no remote code execution — only pre-defined operations; long operations follow the “start it, then poll” pattern at `operations/{id}`. Details — [Agent API](/agents/multiagent/docs/agent-api)
.

## Publicness of ports

Agents, apps and tools are invisible from the internet by default: their ports are published only on the server itself (at the `127.0.0.1` address) and reachable by its apps and nginx. Opening a port to the world is your choice — the **“Public port”** switch on the binding you need. It is there both in the creation wizard and later on the **“Ports”** tab of an agent or app: every binding has its own switch, and new rows appear closed. The change takes effect on the next recreation, while changing the main port updates the route right away. That way factories on one machine never see each other: a foreign container cannot reach a closed port.

Only nginx itself (the front door) and the backup service stay public always — they are the ones meant to be reachable from outside. Everything else is closed, and closed ports are managed over a protected tunnel, so a closed port never stops MultiAgent from checking an agent’s health and controlling it.

## Backups

On every factory MultiAgent runs a backup service — rsync with seven read-only sections: the docker, home page, data, projects and tools folders, plus two dump folders (Postgres and Forgejo). Your backup machines pull the data by rsync on a schedule — a typical nightly task:

```
# nightly backup of all server data
rsync -avz rsync://backup@server-host:873/data/    /backups/server-host/data/
rsync -avz rsync://backup@server-host:873/projects/ /backups/server-host/projects/
```

MultiAgent itself is backed up together with its `/data` volume: the database, the encryption keys and the license live there. More about the data layout — in the documentation.

The **“Test connection”** check looks at everything at once: whether the container runs, whether it serves all seven modules (the missing ones are named), whether the published host port is the stored one, and whether the port accepts a connection from the outside. Everything found is listed together — so a “green” check cannot hide a port nothing can reach from outside. Next to it stands the **“Reinstall rsync”** button: it redeploys the receiver and publishes the stored port when the deployment is stale.

Ready-made clients are also issued by the **“Backup”** page in the Assets section: it assembles the same client for every factory of the fleet chosen in the header at once — each factory lands in its own folder, and a factory without a server address is listed as skipped. More about the three clients — on the [Factories](/agents/multiagent/docs/factories)
 page.

## Agent licenses

The “Licenses” section is the central store for Agent license keys. A key is verified when added, encrypted at rest, and never returned by the API — the interface shows only the parsed metadata (type, owner, term, covered products) and never the key itself. The licenses page and the details dialog show a **“Products”** field: the list of products from the key, or “Universal” for a universal key. A correctly signed key that does not cover the product you need returns a coverage error instead of a term — the status tells you exactly what is wrong. One key can be assigned to any number of agents and lands automatically in their `AGENT_LICENSE` variable at deployment. A license assigned to at least one agent, or chosen as a factory’s default license, cannot be deleted until you detach it.

A key can not only be pasted — it can be issued right in the interface: when the signing key sits on the machine, the license dialog gains a “Generate license” item. There you fill in the type, who it is issued to, the email, a description and the term; the finished key goes straight into the encrypted store and becomes the factory’s default license — the key itself is never shown, just like a pasted one. Without the signing key on the machine, the item does not appear and nothing changes.

Where a license went is visible too: its details dialog lists the factories and agents that use it — by name, with links, not just a count. That way you can detach a license before deleting it without walking every factory by hand. A license is also picked on the factory’s “General” tab — it becomes the default for all new agents on it.

A license has an **“Extend”** action, and it opens from the same dialog as the assignments list — there is no separate window for extending. You set a term in days (31 by default) or an end date: the two fields are linked, change one and the other recalculates. The key is rebuilt with the new date, while its owner, type, covered products and all assignments stay as they are — there is no need to issue a new key and assign it to the agents again. Renaming and re-issuing remain one step deeper — a separate button inside the dialog.

Extending by hand is not required: every dated license carries an **“Auto-renew”** toggle, and a new license has it on right away (older ones read as on). While it is on, a check every six hours watches the term: as soon as less than the check interval remains — or the term has already passed — the key is rebuilt for another 31 days. An expired license counts from today, it never moves into the past. Nothing in the key changes but the date: the owner, the type, the products and the assignments stay where they are, and the key itself is never shown anywhere.

After the renewal, every agent and app holding that license — directly or as the factory’s default — gets the ordinary rolling update: an agent busy with a chat waits for silence, an idle one recreates at once, and a stopped one picks up the new key at its next start. A running chat is never interrupted. The toggle sits on every dated license — on its row in the list, in the add form and in the properties dialog; a manual Extend does not reset it. A perpetual license has no expiry, so it has no toggle. Renewal needs the signing private key on the machine — without it the renewal is skipped and retried on the next check.

## MultiAgent licensing

MultiAgent itself ships without a license: there is no built-in trial key in the product, keys are issued manually — the trial one is part of the [Trial](/agents/factory)
 tier. The license is a self-contained signed string: you load it through the `AGENT_LICENSE` variable (the same one every product in the family reads) or as an activation file in the data folder, and it is verified offline against a built-in key. A universal key (no product list) covers every product; an invalid license blocks only creating new things and sending messages. The license is included in the [Agent Factory](/agents/factory)
 subscription.

The license status loads right after sign-in: the license line in the interface shows its state as soon as you are signed in — including the first time you open the panel in a new browser, where the sign-in happens after the page has already loaded. No manual refresh is needed.

## Interface language and time zone

Each user picks the interface language in the “Appearance” window: English or Russian. English is simply the default of the English build; on the Russian build the interface opens in Russian — but everyone can switch it for themselves, and the choice is saved with the account. Dates and numbers keep the build’s format either way.

Right under the language you pick the **time zone** — one for the whole system. Every date, chart and report is shown in it, so the panel’s time matches yours. Storage keeps everything in UTC, so changing the zone shifts and breaks nothing — only the way the data is displayed changes.

## Login sessions

A sign-in into the panel is remembered for **90 days** — this is about the management panel itself, not about the agents. Nothing needs confirming again during that time: an ordinary profile update does not break the session. Devices that are already signed in keep working even when a login link is revoked: a revocation closes the door to new sign-ins but does not throw out those already in. When everyone has to be signed out at once, the **“Authorization”** tab has the **“Apply configuration”** button — it ends every central-login session, and signing in again will take the current password.

[← Back to documentation](/agents/multiagent/docs)
