Install
One Compose stack on a machine you own
Glion is in private preview. Its image goes to people given early access, so there is nothing to download here yet. This page says what it needs and what installing it looks like, so you can judge whether it fits.
Private preview No public image or download yet
What it needs
Docker with Compose
Glion ships as a Compose stack that orders its start on a one-shot setup step and a database health check. Use a current Docker Compose, v2.
A machine you control
The image is Alpine Linux and runs as an unprivileged user. It is meant for hardware you own, on your own network, where it can reach the services you want agents to work on.
An API key for one model provider
Anthropic, OpenAI, Google, or any OpenAI-compatible endpoint, including a local Ollama, vLLM or LM Studio. Scanning and connecting need no key; running an agent does.
CPU, memory and disk
Not yet measured. Figures will be published with the first release.
To be published
What installing looks like
For people given early access, with the Compose file and image they receive.
Step 1
Bring the stack up
docker compose up, run in the directory that holds the compose file people given early access receive, starts three things: a one-shot step that generates the database password and the encryption key into a volume, a pinned Postgres, and Glion, which applies its database migrations as it starts.Step 2
Read the password from the log
Unless you set one yourself, Glion generates a console password on its first run and prints it once, in the log. Keep it. You can choose your own instead by setting it in the environment before the first start.
Step 3
Open the console
The console is published on loopback only, at http://127.0.0.1:4100 on the host. Sign in with the password.
Step 4
Follow the setup
Six steps, and the first two need no credentials: confirm a subnet and scan it, then keep what is yours. Then connect services with one scoped token each, add a model key, shape a team of agents from what was found, and give it a first task. Every step can be skipped and come back to.
Before you rely on it
The encryption key is the only copy. It is generated on the first run and never overwritten, because changing it makes every stored credential unreadable. Stopping the stack keeps your data. Removing its volumes deletes the key, and every credential stored under it, with the database.
Opening it to other machines is a decision. The console listens on loopback until you change the published port. Put TLS in front of it first. If it must be reachable from outside your network, reach it over a VPN or an overlay network rather than the open internet: an agent can reach whatever the host can, and that is worth guarding.
It runs agents, not only a dashboard. The container can reach your network and, by default, the internet. Security says what holds a risky call and what does not.
Getting access
Write to [email protected] with a line about what you would run it on and what you would have it do. Community, the free plan, is everything Glion does today; pricing has the rest.
Request early access