Self-hosted install

Detailed installation & settings

What is in the release package, how the installer works and what every setting means.

v1.0.0 CZ

What is in the release package

  • install-docker.sh, install-docker.ps1, install-docker.bat — the installer for Linux/macOS, PowerShell and Windows.
  • install-auto.bat — one-click automatic install on Windows.
  • install-docker-gitea.sh, .ps1, .bat — the same install with a bundled Gitea git server.
  • docker/aitm-release-v<version>.tar.gz — the Docker image.
  • docker/docker-compose.yml — the container definition (ports, volumes, health check).
  • docker/.env.example — the template for your docker/.env.
  • ABOUT-AITM.md, AI-CONNECT.md, AI-INSTALL.md — guides for you and for your AI assistant.

Always copy the whole extracted folder to the target machine, not only the image file.

Automatic and interactive install

The automatic install (--auto on Linux/macOS, install-auto.bat on Windows) makes every decision itself. The interactive install asks you for the values instead:

bash install-docker.sh
powershell -ExecutionPolicy Bypass -File install-docker.ps1

Both check the package signature, load the image, start the container and wait until it reports healthy. The installer writes a log file next to the scripts and prints its path.

Settings in docker/.env

The installer creates this file for you. You can change the values later and restart the container.

  • AITM_ADMIN_TOKEN — the administrator token for the admin API. The installer generates a strong one.
  • AITM_PORT — the port of the web interface. The default is 3333; the automatic installer picks a free one if it is taken.
  • AITM_MCP_TOKEN — the bearer token for the two MCP servers that your AI assistants connect to. The installer generates it.
  • MCP ports — the two MCP servers listen on ports 3335 and 3336.
  • AITM_SSH_PORT — the port of the SSH access into the container.

Variant with a bundled Gitea

If you want a local git server next to AITM, run install-docker-gitea.sh (Linux/macOS), install-docker-gitea.ps1 or install-docker-gitea.bat (Windows) instead of the standard installer.

A second, independent instance

The installer can set up a separate instance next to an existing one. The interactive installer offers this as a fresh side-by-side install; on Windows use install-docker.ps1 -SideBySide. The new instance gets its own project name, its own volumes and its own ports, and the existing one is left untouched. Run it from a new copy of the release folder.

Where your data lives

Your data is stored in Docker named volumes, so it survives restarts and updates:

  • docker_aitm-data — AITM state and databases.
  • docker_aitm-home — the home directory of the container user.
  • docker_aitm-worktrees — working copies of your projects.

Managing the service

Run these in the docker folder:

  • docker compose ps — show the container state.
  • docker compose logs -f — follow the logs.
  • docker compose stop / docker compose start — stop and start it.
  • docker compose restart — restart it.
  • docker compose down — remove the container (the data volumes stay).

Updating to a new release

Extract the new release and run the installer again. It backs up your volumes, starts the new version next to the old one and swaps them once the new one is healthy. As a safety feature it installs only the same or a newer version than the one that is running.

7-day trial

No license key is needed to start. AITM runs a free 7-day trial that you can start in Settings → License.

Security and isolation

The installer verifies the signature and checksum of the package before it loads the image. The tokens are generated per installation and stored only in docker/.env. AITM runs in its own container and only the ports listed above are exposed.