Download

Linux Public Beta 🇧🇷 Portuguese UI

Public installer

The Linux installer prepares the local runtime, verifies health, and opens the current Aion web UI.

First-time public installs should start with the installer below. You do not need to clone the aion-ctrl repository or fetch the runtime package manually unless you are doing recovery or an advanced operator flow.

Recommended

Checking your platform

The download recommendation uses the current browser platform only as a hint. Manual artifact links stay visible below.

Download installer

Current target: Linux x86_64 only. The installer writes runtime files under ~/.aion by default.

Release integrity

Current public beta release

Version: v0.0.3-beta.2
Channel: beta
Released at: 2026-04-22T16:22:32Z
Checksum: 9d238c8df45e16ff965961ddbd912dbca8a61b3fdc7e9327ee96249c3fc87c44

Manifest JSON checksums.txt Release notes

Installer

Manual installer download

Artifact	Support	Integrity	Action
aion-installer-linux-amd64	Linux x86_64	84cf017e0946f4b518294c0a98a0bf365011e0f6558711267e3ef01b780f1f3d	Download
linux-arm64	Deferred	Not published in the current beta	Coming later
windows	Deferred	Not published in the current beta	Coming later
macos	Deferred	Not published in the current beta	Coming later

Technical artifacts

Manual runtime package

The public installer is the only download most users need. The packaged aion-ctrl runtime exists for manual, troubleshooting, or advanced operational flows.

aion-ctrl-linux-amd64.tar.gz

Runtime engine package with bundled distribution assets, launcher binary, desktop entry, and icon for the Linux public installer flow.

93071e593c70196b7304fb64a6a3f4bf4d5b07ff1d40227dbe3c0af617c0c168

Download package

Use it when

Who this artifact is for

manual runtime recovery or inspection
advanced operator workflows
debugging installer/bootstrap behavior
local verification of the packaged distribution assets

Requirements

Before running the installer

Linux x86_64
Docker daemon running
Docker Compose v2
8 GB RAM recommended
12 GB free disk minimum
Internet access for image and manifest downloads
One remote provider key for the default path: OpenAI or Groq

Support matrix

Current support boundary

Supported: Ubuntu 24.04, Ubuntu 22.04, Debian 12
Default runtime home: ~/.aion
--home /path changes runtime files, not Docker container names or default ports
Default desktop open path: packaged Aion launcher when the runtime package provides it
Canonical product UI after open: aion-web
Not promised: native Linux installer

Official path

What most users should do

download aion-installer-linux-amd64
run the installer from a terminal after the download finishes
use a remote provider by default unless you intentionally want local Ollama
let the installer fetch the packaged aion-ctrl runtime automatically
use the manual runtime package only for recovery, verification, or advanced operator flows

Current limits

Important runtime notes

do not run the public installer with sudo
the current beta runtime is not intended for side-by-side installs on the same host
the current installer does not auto-install Docker or Docker Compose for you
the public installer remains terminal-first even though the installed open path is launcher-first

Quick checks

Confirm the machine is ready

Terminal

docker info
docker compose version
uname -m
df -h
free -h

If docker info or docker compose version fails, install Docker first. Only check ollama --version when you intentionally want the advanced local model path.

Get the missing pieces

Official setup links

Install Docker Engine on Linux
Install Docker Compose plugin on Linux
Docker Linux post-install steps
Create an OpenAI API key
Create a Groq API key
Install Ollama on Linux only if you want the advanced local model path

Terminal flow

How to run the installer after the download finishes

The current public installer is a Linux executable script. Open a terminal, go to your download folder, make the file executable, and run one of the supported install commands below.

Step 1

Open the terminal in your download folder

Terminal

cd ~/Downloads
chmod +x aion-installer-linux-amd64
./aion-installer-linux-amd64 --help

The installer can be executed from any folder. The runtime still defaults to ~/.aion unless you pass --home /path.

The file does not open as a graphical app in the current public beta. It is executed from the terminal.

Step 2

Choose one runtime profile

OpenAI: recommended default path for most installs
Groq: remote alternative when you prefer GroqCloud
Local Ollama: advanced local model profile on the same machine

Remote profiles are the default public path. Local Ollama is optional and intentionally more advanced.

No API key yet

Pick one provider path first

OpenAI: recommended default for the current public installer path
Groq: remote alternative when you already use GroqCloud
Ollama: install it only if you intentionally want local inference on this machine

OpenAI key guide Groq keys Ollama Linux guide

Provider notes

What each option changes

OpenAI and Groq are the default supported user path and require internet plus a valid API key
The installer now checks remote provider auth through the packaged runtime contract, so an invalid key should stop the first-run flow before the app claims success
Ollama keeps inference on the local machine and avoids provider API keys
Ollama also adds local model/runtime requirements and extra startup cost, so treat it as an advanced option
The installer does not create OpenAI or Groq accounts for you and does not install Docker automatically

OpenAI example

Install with OpenAI

Terminal

cd ~/Downloads
chmod +x aion-installer-linux-amd64
./aion-installer-linux-amd64 \
  --provider openai \
  --model gpt-4.1-mini \
  --openai-api-key YOUR_OPENAI_API_KEY

Groq example

Install with Groq

Terminal

cd ~/Downloads
chmod +x aion-installer-linux-amd64
./aion-installer-linux-amd64 \
  --provider groq \
  --model llama-3.3-70b-versatile \
  --groq-api-key YOUR_GROQ_API_KEY

Local example

Install with local Ollama

Terminal

cd ~/Downloads
chmod +x aion-installer-linux-amd64
./aion-installer-linux-amd64 --profile local-ollama

Use this profile only when the machine is intentionally prepared for local model execution and you do not want the default remote path.

What happens next

What the installer does for you

validates Linux, Docker, Compose, RAM, disk, and ports
downloads the public release manifest
downloads the packaged aion-ctrl runtime and launcher assets when they are published
prepares ~/.aion/distribution and writes local config
pulls the public runtime images from GHCR
starts the stack, runs doctor, and opens Aion through the desktop launcher when available
installs an app shortcut and a desktop shortcut with the Aion icon when the Linux desktop supports it

Need help

Troubleshooting

If the machine fails preflight or the runtime looks unhealthy, use the operational recovery path instead of guessing.

Open troubleshooting guide

Runtime truth

How you use Aion after the install

The product stays in the browser and the runtime stays on the local machine. In daily use, open Aion from the installed launcher or desktop shortcut. The launcher can then open the current web product UI and expose runtime actions without requiring terminal-only flows.

the installer can install the packaged launcher desktop entry and a desktop shortcut when the Linux desktop supports it
the runtime services use restart policies, so they usually come back with Docker after a reboot
if the runtime is stopped, start it again from the launcher or with aion-ctrl play

Installer behavior