Self-host Gydmation AI
Gydmation runs entirely on your own machine, in Docker. Your prompts, workflows, and n8n credentials never leave it.
Overview
Gydmation ships as a single Docker image. There's no separate database to configure, no cloud account required to run it — Docker Compose handles the whole setup with two commands.
Requirements
- Docker Desktop, installed and running — get it here if you don't have it
- About 4GB of free disk space for the image
- Windows, macOS, or Linux — anywhere Docker Desktop runs
Installing Gydmation
Get the files from GitHub, then start it with Docker Compose.
View on GitHub- Open the GitHub repository above, click the green Code button, then Download ZIP
- Extract the ZIP somewhere you'll remember — for example
C:\Gydmationon Windows, or~/Gydmationon macOS/Linux. (AvoidC:\Program Files— Windows locks that folder down to admin-only access, which can make Docker Compose fail with a permissions error.) - Open a terminal inside that extracted folder
Then run:
docker compose pull
docker compose up -d
The first run also sets up an AI model in the background — this takes a few minutes, and happens again briefly on every restart. That's expected.
Opening it
Once it's running, open:
You'll land on the sign-up screen the first time. Signing in again later just uses that same address.
Changing the port
Already using port 8080 for something else? Set it before starting:
docker compose up -d
Then open http://localhost:3000 instead.
Updating
Same two commands as installing:
docker compose up -d
Docker only downloads what's changed. Your account, history, and settings are untouched by an update.
Your data
Everything — your account, chat history, connected n8n credentials — lives in a Docker volume, separate from the application image. Stopping or updating Gydmation never touches it.
This stops the app without removing your data. It's exactly where you left it next time you run docker compose up -d.
Uninstalling
To remove Gydmation and its data completely:
docker volume rm gydmation-data
The second command deletes your data permanently — only run it if you actually want everything gone.
Troubleshooting
"docker" isn't recognized
Docker Desktop isn't running, or isn't installed. Open the Docker Desktop application and wait for it to say "Running," then try again.
Port already in use
Something else is using 8080. See Changing the port above.
Still stuck?
This almost always shows exactly what's wrong. If you're stuck, email us that output: support@hacroo.com