Self-Hosting

About

Future AGI is the complete platform to test, guard, and monitor AI agents. Build self-improving agents that ship smarter with every version. Self-hosting runs the entire platform on your infrastructure. The backend is built on Django, the frontend on React + Vite. All data stays on your machines.

When to self-host

• Data residency or compliance: Traces, datasets, and evaluation outputs never leave your network.
• Air-gapped environments: Run without outbound internet access (air-gapped support is coming; Docker Compose today assumes outbound access for pulling base images and LLM APIs).
• Cost control at scale: For high-volume workloads, run your own infrastructure instead of the hosted plan.
• Customization: Modify any part of the platform to fit internal systems.

If none of these apply, the hosted version at app.futureagi.com is easier to operate.

Deployment options

Prerequisites

Install Docker and Compose

brew install docker docker-compose colima
colima start --cpu 4 --memory 8 --disk 64

sudo apt-get update
sudo apt-get install -y docker.io docker-compose-v2
sudo systemctl start docker && sudo systemctl enable docker
sudo usermod -aG docker $USER

Verify:

docker --version          # 24.0+
docker compose version    # v2.20+

Clone the repository

1. Fork the repository on GitHub.
2. Clone your fork:

git clone https://github.com/YOUR_USERNAME/future-agi.git
cd future-agi
cp .env.example .env

Configure environment

Replace every CHANGEME value in .env:

openssl rand -hex 32    # for SECRET_KEY and AGENTCC_INTERNAL_API_KEY
openssl rand -base64 24 # for PG_PASSWORD

Run the Stack

docker compose up

To run in the background:

docker compose up -d
docker compose logs -f backend    # watch startup progress

Once all services are up, open the frontend and backend:

• Frontend: http://localhost:3031
• Backend API: http://localhost:8000

Verify all services are healthy:

docker compose ps

Create your account

The email registration flow requires Mailgun credentials (MAILGUN_API_KEY and MAILGUN_SENDER_DOMAIN in .env). Without Mailgun, create a user via the Django shell:

docker compose exec backend python manage.py shell -c "
from django.contrib.auth.hashers import make_password
from accounts.models import User
User.objects.create(email='you@example.com', password=make_password('your-password'))
"

Log in with those credentials.

Stop, reset, and upgrade

# Stop (data persists in Docker volumes)
docker compose down

# Stop and wipe all data (fresh start)
docker compose down -v

# Upgrade to latest
git pull
docker compose build
docker compose up -d

Development mode

Use the dev overlay for hot reload and per-queue workers:

docker compose -f docker-compose.yml -f docker-compose.dev.yml up

This adds hot reload for backend code, per-queue Temporal workers, exposed database ports, and a Temporal UI.

Production checklist

Before exposing to users:

• Replace every CHANGEME value in .env
• Set ENV_TYPE=prod and FAST_STARTUP=false
• Put a reverse proxy (Caddy, Nginx, or Traefik) in front for TLS
• Replace Compose databases with managed equivalents (RDS, ClickHouse Cloud, ElastiCache, S3)
• Increase backend workers (GRANIAN_WORKERS in .env) to match your CPU count
• Set up backups for PostgreSQL (pg_dump) and ClickHouse (BACKUP)
• Use a secrets manager instead of a plain .env file

Troubleshooting

For anything not listed, open an issue at github.com/future-agi/future-agi/issues with the output of docker compose logs.

Next Steps