Self-Hosting

Host your own instance of Alita Robot.

This guide covers everything you need to deploy your own instance of Alita Robot.

Prerequisites

Before you begin, ensure you have:

For building from source:

• Go 1.26+

Deployment Options

git clone https://github.com/divkix/Alita_Robot.git
cd Alita_Robot
cp sample.env .env
# Edit .env with your configuration
docker compose up -d

git clone https://github.com/divkix/Alita_Robot.git
cd Alita_Robot
go build -o alita_robot .

Essential Configuration

At minimum, you need these environment variables:

BOT_TOKEN=your_bot_token_from_botfather
OWNER_ID=your_telegram_user_id
MESSAGE_DUMP=-100xxxxxxxxxx  # Log channel ID
DATABASE_URL=postgresql://alita:change-me@localhost:5432/alita

Redis itself is also required at runtime. No Redis endpoint variable is needed when it is available at the default localhost:6379; otherwise set either REDIS_ADDRESS=host:port or a full REDIS_URL.

Webhook vs Polling

Database Setup

Alita uses PostgreSQL with automatic migrations:

# Enable auto-migration
AUTO_MIGRATE=true

# Or run manually (requires PSQL_DB_* env vars to be set)
make psql-migrate

Monitoring

Built-in observability endpoints:

• GET /health - Health check with DB/Redis status
• GET /metrics - Prometheus metrics
• GET /db_metrics - Database performance metrics

Next Steps