Documentation
Installation, configuration and operations guides for the self-hosted Menelaus Orchestrator — built for secure on-premise and fully offline deployments.
Everything to run Menelaus yourself
Installation & setup
Deploy the Orchestrator with Docker on Linux or Windows — online, or fully offline from local image files.
Configuration
Every environment variable that drives the Orchestrator — generated by profile, then tuned by hand.
Updates & maintenance
Move between releases safely, keeping your media and database volumes intact through every upgrade.
Security & hardening
Encryption keys, HTTPS, session binding and the browser headers that keep the console locked down.
Orchestrator distribution
What ships inside the on-premise package and how the services fit together behind nginx.
Support & community
Get unblocked fast — official support channels, the community Discord, and the Python RPA team.
AI Agents
Architecture, tool calling, memory and escalation rules for autonomous agents.
IDP & Documents
Extract, classify and validate data from any document type at scale.
Install the Orchestrator with Docker
The distribution is self-contained — load the images, generate your environment file, and bring the stack up. No internet access required.
Never delete or replace the original .env or docker-compose-deploy.yaml after installation.
# 1. Verify Docker is installed docker --version docker-compose --version # 2. Load the distribution images (offline-friendly) sudo chmod 666 /var/run/docker.sock docker load -i orchestrator.tar docker images # expect 6 images # 3. Generate environment variables ./cloudorc_create_env_vars.sh domain # or: ip # 4. Launch the Orchestrator docker-compose -f docker-compose-deploy.yaml up -d
Environment variables
New installs generate the .env from the domain or ip profile. For existing servers, add only the missing variables — never regenerate the file or change keys and credentials unless support asks you to.
Core settings
- SECRET_KEY
- ALLOWED_HOSTS_LIST
- TIME_ZONE
- ON_PREMISE
- LOG_LEVEL
HTTPS & proxy
- SSL redirect
- Proxy headers
- Secure cookies
- HSTS
Database & Redis
- DB name / user / password
- DB host / port
- Redis URL
- Celery results
Email (SMTP)
- SMTP host
- SMTP port
- SMTP user
- SMTP password
Encryption & licensing
- AES_KEY
- CRYPTO_KEY
- HARDWARE_ID
- API key
Sessions & headers
- Idle timeout
- Active sessions / user
- IP & user-agent binding
- CSP / XSS headers
Do not change SECRET_KEY, AES_KEY, CRYPTO_KEY, HARDWARE_ID or database credentials on a running install. Restart services after any change.
Two upgrade paths
Standard update
A rolling update: stop the stack, swap in the new images, drop non-essential volumes (keeping media and postgres), then restart.
- Stop containers
- Swap images
- Preserve media + postgres volumes
- Restart & verify
Major upgrade update
Crosses major dependency bumps (Django 5, Python 3.11, PostgreSQL 15, Redis 7.2) — a full backup is required before you start.
- Back up DB (db_backup.sh)
- Back up media (media_backup.sh)
- Load new images
- Restore & verify
The complete guides
This page is a quick orientation. For exact commands, every environment variable and the full step-by-step procedures, open the detailed guides.
Administration Guide
Complete installation for Linux & Windows, online and offline, plus update procedures and technical requirements.
Open guideEnvironment Variables Guide
Every variable the Orchestrator reads — core, HTTPS/proxy, sessions, database, email, encryption and licensing.
Open guideDocker Distribution Overview
What ships in the on-premise package and how to deploy it in restricted or fully offline environments.
Open guideRunning Menelaus on your own infrastructure?
The on-premise package ships with everything for a secure, offline install. Our team and the community Discord are here when you need a hand.