---
title: "Installation & Setup"
id: "2226"
type: "page"
slug: "install"
published_at: "2026-11-10T06:14:47+00:00"
modified_at: "2026-11-18T17:59:49+00:00"
url: "https://xedant.com/agents/multiagent/docs/install/"
markdown_url: "https://xedant.com/agents/multiagent/docs/install.md"
excerpt: "This page is for those who install MultiAgent themselves, on their own server or Windows…"
---

# Installation & Setup

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

This page is for those who install MultiAgent themselves, on their own server or Windows computer: from installation to the first working factory. From there MultiAgent manages the other servers on its own — nothing needs to be configured on them by hand.

If you are on the Expert tier, the server and its upkeep are on you, and help with installation and setup is part of the subscription: write in Telegram to [@max_pas](https://t.me/max_pas)
 if something doesn’t work.

## What you need

- **A machine for MultiAgent itself** — Linux with Docker, or Windows 10 and newer (64-bit). 1 GB of memory is enough; the database is built in by default, PostgreSQL can be connected optionally. The computing power is needed not by MultiAgent but by the agents — they run on the managed servers.
- **Managed servers** — Linux (Ubuntu/Debian) with SSH access and root or sudo rights. The connection is by password or private key. MultiAgent will install Docker and everything else on them itself.
- **A license** — there is no built-in trial key: without a key the application works, but does not let you create or change factories and agents. Keys are issued manually: the trial one — as part of the [Trial](/agents/factory) tier, the Expert tier key — after payment on the [Buy Agent Factory](/agents/factory/buy) page.

## Installation in Docker

Any server or computer with Docker will do for this method. Create a `compose.yml` file:

```
services:
  multiagent:
    image: xedant/multiagent:min-latest
    container_name: agents-multiagent
    ports:
      - "3990:80"
    volumes:
      - multiagent-data:/data
    environment:
      - ASPNETCORE_ENVIRONMENT=Production
      - ASPNETCORE_URLS=http://+:80
      - MULTIAGENT_DATA=/data
# license key: without it the application works, but does not let you change factories and agents
# - AGENT_LICENSE=your-key
    restart: unless-stopped

volumes:
  multiagent-data:
```

Run `docker compose up -d` and open `http://machine-address:3990`. The `/data` volume is mandatory: the database, keys, certificates and the license live in it, and without it all of that is lost at the very first `docker compose down`.

The full walkthrough — minimal requirements, every environment variable, the `.env` file, data storage and running without compose — is on the [Docker Installation](/agents/multiagent/docs/docker)
 page.

## Installation on Windows

The `XedantMultiAgent-Setup-<version>.exe` installer installs MultiAgent as a Windows service: it starts together with the system and keeps managing the servers even when nobody is signed in to the machine. The wizard asks for the port (3990 by default), the data folder, the login and password, the license and the service start mode. No .NET environment is needed — the installer already has everything inside. More detail on the [Windows Installation](/agents/multiagent/docs/windows)
 page.

## First sign-in

Open the web interface and click **Sign up**: the first user is created right on the login page and becomes the administrator. The login and password can also be set in advance — with the `MULTIAGENT_LOGIN` and `MULTIAGENT_PASSWORD` variables, where the password is stored as a SHA-256 fingerprint. You can get such a fingerprint on the login page or from the Linux and macOS command line:

```
printf '%s' 'your-password' | sha256sum | cut -d' ' -f1
```

The command returns a 64-character fingerprint — put that into `MULTIAGENT_PASSWORD`. In the browser your user data (cookies) is remembered for 90 days.

## License

There is no built-in trial key in the build: keys are issued manually, and the trial one comes as part of the [Trial](/agents/factory)
 tier. Your own key is added in one of two ways: the `AGENT_LICENSE` variable at startup, or the license dialog — the license status line in the settings window opens it. The license is a signed string: the server does not call anywhere to verify it, and its term and renewal are visible in the same place. More detail — [Security & Licensing](/agents/multiagent/docs/licensing)
.

## Setup after installation

1. **Add a server** — the machine where the factories will live: address, SSH port, user, password or private key. On Windows you can choose **Local WSL** instead of SSH — a distribution on the same computer. More detail — [Servers](/agents/multiagent/docs/servers) .
2. **Create a factory** — pick a server and set a name and a short deployment name (the slug, `agents` by default): it defines the network, the container-name prefix and the folders. More detail — [Factories](/agents/multiagent/docs/factories) .
3. **Walk through the factory checklist** — the check button on its page shows what is missing: connectivity, Docker, folders, Nginx, a certificate, Postgres, backups, the home page, central sign-in. Whatever is missing is fixed in one click.
4. **Install agents and products** — the “New agent” wizard: choose the type (standalone agent or product), and the name, factory, image and port are filled in for you. From there MultiAgent assembles the `compose.yml` and brings the containers up on the server. More detail — [Agents](/agents/multiagent/docs/agents) .

The remaining steps — routes in subfolders, the factory home page, single sign-in by QR code — are covered in [Getting Started](/agents/multiagent/docs/getting-started)
.

## Updates

- **Docker** — `docker compose pull`, then `docker compose up -d`: the data volume stays in place;
- **Windows** — run the new version’s installer again: the wizard offers “Reconfigure or update”, files are replaced and the data folder survives;
- **Agents and products** — are updated from the interface: “Update smoothly” waits for a pause in a chat, “Recreate” replaces the container at once. More detail — [Agents](/agents/multiagent/docs/agents) .

## Backups

On every factory MultiAgent runs a backup service: it exposes the docker folders, data, projects, tools, the home page and other sections — read-only, so a copy can be picked up on a schedule. MultiAgent itself is backed up together with the `/data` volume, so keep it on a persistent volume. More detail — the “Backup” section on the [Security & Licensing](/agents/multiagent/docs/licensing)
 page.

## Security

MultiAgent stores server SSH keys, agent passwords and license keys, so its port is better not exposed straight to the open internet: put a proxy with HTTPS in front of it (Nginx, for example), or set `MULTIAGENT_SSL=auto` — then MultiAgent brings up HTTPS on the neighboring port with a self-signed certificate (in Docker this port must be opened in `compose.yml`). All secrets on disk are encrypted. More detail — [Security & Licensing](/agents/multiagent/docs/licensing)
.

## If something doesn’t work

- **Docker** — the container log: `docker logs agents-multiagent`;
- **Windows** — the `<data folder>\service.log` log and the “MultiAgent (Xedant)” service in `services.msc`;
- **The page doesn’t open** — most often the port is already taken by another program: change it in `compose.yml` or in the installation wizard;
- **A setup question** — Telegram [@max_pas](https://t.me/max_pas) : help with installation and setup is part of the Expert subscription.

[← Documentation table of contents](/agents/multiagent/docs)
