MAIA PlusDocumentation

MAIA Plus · Administrator guide

A confident start.
A smoother upgrade.

From your first installation to your next release. Clear steps, the right packages and a safe path for your ServiceDesk Plus environment.

New All-in-One installerWindows and LinuxNo manual file replacement

Install from scratch

Prepare your environment, run the installer and connect MAIA to ServiceDesk Plus. Follow the steps whether both systems share a server or run separately.

Start your installation →

Upgrade safely

Verify the package, review the upgrade plan and let the updater handle the backup and restart. Learn what to do if something goes wrong.

Follow the upgrade guide →

What’s new in 1.1.0

Easier workflow editing, better use of tickets and knowledge, and more control over AI automation.

Explore the changes →
Meet the new All-in-One Windows installer

MAIA, prerequisites and ServiceDesk Plus integration in one guided flow. Read the introduction →

Preparing components separately? Install PostgreSQL, pgvector and Python →

Choose the right package

Your goalRecommended package
New Windows deploymentAll-in-One Windows — the application, prerequisites and assistance with SDP integration.
Upgrade an existing MAIA installationWindows or Linux ZIP containing MAIA-MAINTENANCE. Do not reinstall the infrastructure.
Windows with a database and Python already preparedThe signed Windows ZIP with install.bat, or the installer’s app-only mode.
New Linux deploymentThe signed Linux ZIP, prepared dependencies and a systemd service.

Download only artifacts actually available on the downloads page. A version number used in an example does not mean that every package for that version has been published.

Three rules worth remembering

  • Installation and upgrade are different operations. A fresh installation requires an empty directory. Upgrade an existing installation with MAIA-MAINTENANCE.
  • Check first, confirm second. Preflight shows the plan and any blockers before changes are made.
  • Keep backups protected. Never publish database dumps, secrets, .env files or instructions containing passwords.
This documentation does not run commands

Copy buttons copy text only. Run commands yourself on the correct server after checking the paths and the scope of changes.