Install AiOS
The AiOS platform, on a server of your own
One command, run as a regular user, and the registry token we send you. Evaluate it on a VM, or install it for your own domain with its certificate and encrypted secrets.
$ curl -fsSL https://gitlab.mgt-platform.com/in-manas-public/aios-deployment/-/raw/main/install.sh | bash
Evaluation
defaultThe whole platform on one machine, reachable on the machine itself with a self-signed certificate. For trying it out; nothing to prepare but the server and the token.
Production
AIOS_MODE=productionYour own host name and TLS certificate (Let's Encrypt, Let's Encrypt through Cloudflare, or one you already have), every secret encrypted, checks before anything is installed, and optionally mail and your first organization.
Both modes
Before you start
- A fresh Debian 13 or Ubuntu 24.04 server or VM, with 8 CPUs, 16 GB of RAM and 300 GB of disk.
- A regular user who can use
sudo. The installer refuses to run as root. - Outbound HTTPS to
gitlab.mgt-platform.com(the installer and the container images), PyPI and Ansible Galaxy (the installer's tools), Docker's package repository and your distribution's mirrors. - The registry username and token we sent you, which let the server pull the platform's images.
Evaluation
Try it on a VM
The platform at https://aios-sample-setup.localhost, with a
self-signed certificate and generated secrets. Not for real data.
-
Run the installer
As the regular user, on the server:
curl -fsSL https://gitlab.mgt-platform.com/in-manas-public/aios-deployment/-/raw/main/install.sh | bashIt installs what it needs (Docker, git, Ansible in its own environment), asks for the registry username and token, deploys the platform and creates its first administrator. The first run downloads every image, so expect it to take a while.
-
Log in
It ends by printing the Portal's address and the administrator's login. The address only resolves on the server: from your own machine, forward port 443 to it, then browse
https://aios-sample-setup.localhost.sudo ssh -N -L 443:127.0.0.1:443 <user>@<server>
Without the token prompt: | REGISTRY_TOKEN_USER=im-<you> REGISTRY_TOKEN=<token> bash.
That puts the token in your shell history; clear it afterwards, or use the prompt.
Production
Install it for your domain
The same installer with AIOS_MODE=production: a real host name
and certificate, the secrets generated on the server and encrypted there,
and nothing installed until its checks pass.
-
Point a host name at the server
A DNS record, for example
aios.example.com, resolving to the server's public address. For Let's Encrypt over HTTP, ports 80 and 443 must be reachable from the internet. -
Choose where its certificate comes from
- Let's Encrypt (
letsencrypt, the default): issued and renewed automatically over port 80. - Let's Encrypt through Cloudflare (
cloudflare): for a domain on Cloudflare; needs an API token with Zone · DNS · Edit on that zone, and port 80 need not be open. - Your own certificate (
manual): a certificate file with its chain, and its key. You renew it yourself.
- Let's Encrypt (
-
Run the installer in production mode
As the regular user, on the server:
curl -fsSL https://gitlab.mgt-platform.com/in-manas-public/aios-deployment/-/raw/main/install.sh | AIOS_MODE=production bashIt asks for the host name, the certificate's source, the administrator's email, an outgoing mail server and a first organization (both optional), the registry token, and a password to encrypt the server's secrets with (or generates one). Then it checks the server: operating system, resources, ports, DNS, the certificate or Cloudflare token, and that the registry token pulls every image. If a check fails, it says what to fix and changes nothing.
-
Keep the vault password safe
The secrets are encrypted with it, and it is kept in
~/.config/aios/vault-passwordso upgrades run unattended. Back it up with the server's data: without it the configuration cannot be decrypted.
Unattended
Every answer can come from the environment instead, for a scripted install. For example, with Let's Encrypt and no mail:
export AIOS_HOST=aios.example.com AIOS_TLS=letsencrypt
export AIOS_ADMIN_EMAIL=you@example.com AIOS_ORG_NAME="Example"
export REGISTRY_TOKEN_USER=im-<you> REGISTRY_TOKEN=<token>
# Cloudflare: AIOS_TLS=cloudflare CF_DNS_API_TOKEN=<token>
# your own: AIOS_TLS=manual AIOS_CERT_FILE=/path/fullchain.pem AIOS_KEY_FILE=/path/key.pem
# mail: AIOS_SMTP_HOST, AIOS_SMTP_PORT, AIOS_SMTP_USER, AIOS_SMTP_PASSWORD, AIOS_SMTP_FROM
curl -fsSL https://gitlab.mgt-platform.com/in-manas-public/aios-deployment/-/raw/main/install.sh | AIOS_MODE=production bash
With mail set, the install ends by sending a test mail to the administrator; without it, what the Portal would send goes to its log.
Afterwards
Running it
Everything lives in ~/aios-deployment, a checkout of the public
aios-deployment
repository. Its guides cover the rest.
- OPERATIONS.md:
checking the install, the administrator, upgrading, backups, renewing the
registry token. Use
TARGET=productionfor a production install. - SAMPLE_DEPLOY.md: what the evaluation install does, step by step, and troubleshooting.
- MONITORING.md: optional. Ship logs to your Graylog and container metrics to your Grafana.
- Guides: step by step, in the Portal and on the server. Organizations and runner capacity, invitations without outgoing mail, connecting your own models and data, and moving existing agents onto AiOS.
Your registry token has an expiry date. Before it, we send you a new one; putting it in place is one file and one command.