Future AGI self-hosting requirements

The Requirements

Future AGI's self-hosting documentation gives three starting sizes:

Software: Docker Engine 24.0 or later, Docker Compose v2.24 or later, and Git 2.0 or later. It runs on Linux bare metal, EC2, GCE, Azure VMs, and GKE or EKS nodes with privileged mode enabled. The docs rule out managed container platforms that block privileged containers - Fargate, Cloud Run, Render, Railway and Fly.io.

On Kubernetes, the docs are direct: "There are no Helm charts or Kubernetes manifests: that support is on the roadmap, and Docker Compose is the only supported path today." The GitHub README lists official manifests and Helm charts as coming soon.

What You Are Running

The requirements page lists PostgreSQL, ClickHouse, Redis, Temporal, MinIO and a code-executor service; the README describes the data layer as PostgreSQL for metadata, ClickHouse for spans and time-series, Redis for state, and RabbitMQ plus Temporal for jobs. The Docker Compose guide starts "all 21 services" in full-stack mode. Published ports include the frontend on 3000, the backend API on 8000, the gateway on 8090, model serving on 8080, the code executor on 8060 and OTLP collectors on 4317 and 4318.

The documented install is short:

git clone https://github.com/future-agi/future-agi.git
cd future-agi
cp .env.example .env      # then replace every CHANGEME secret
docker compose up

Upgrades are git pull, docker compose pull, docker compose up -d, and migrations run on startup. The operational weight is in what the Compose file hides: two databases, a cache, a workflow engine and object storage, each of which needs backups, disk monitoring and upgrades once the install matters.

License and Telemetry

Future AGI opened the platform under Apache-2.0 in Q2 2026. The repository also carries a LICENSE-EE file covering any directory named ee/, and it says that code "requires an active paid subscription (an Enterprise license key or a Future AGI Cloud plan) to use in production." If a feature you plan to use lives under ee/, budget for it or confirm with Future AGI.

Self-hosted instances send telemetry by default. Per the README, a registration on first boot sends the instance ID, version, deployment type, and the email addresses and domains of active admin users; a periodic heartbeat sends anonymous aggregate usage counts. Set FUTURE_AGI_TELEMETRY_DISABLED=1 in .env, or in deploy/.env.production for production, to turn it off. For an air-gapped or regulated install, make that part of the first boot rather than something you remember later.

Before Production

Future AGI's production guide opens with a warning worth taking at face value: "The default stack is not safe to expose. It boots with development secrets that work out of the box, no TLS." The guide pairs that with a security checklist, TLS termination, and backup and restore procedures for Postgres, ClickHouse and MinIO.

1. Replace every CHANGEME secret and disable telemetry before first boot if you need to.
2. Put TLS in front of the frontend, API and gateway ports.
3. Schedule and test restores for Postgres, ClickHouse and MinIO, not only backups.
4. Pin the image version and upgrade deliberately, since migrations run on startup.

What to Test During the Pilot

The repository's issue history points to the parts of a self-hosted deployment that deserve an explicit test before production:

• Fresh installation and upgrade: start from the published Compose file, ingest test data, then upgrade one release and confirm database migrations complete cleanly.
• End-to-end ingestion: send gateway requests and malformed spans, then verify valid traces still reach the dashboard and failed batches are visible.
• Authentication without public services: test signup and login with reCAPTCHA and other external dependencies disabled.
• Evaluator consistency: run the same deterministic check through the SDK and platform, then compare the stored results.
• Air-gapped operation: block outbound internet access and check the UI, model assets and document viewers for CDN dependencies.

Run these checks on the exact version you plan to deploy. A passing demo on a connected laptop does not prove that upgrades, ingestion and authentication will work in a restricted production network.

How Other Self-Hosted Options Compare

If the footprint is the obstacle, compare the services and support model of each option. Langfuse self-hosts with Docker Compose, Helm or Terraform templates and uses Postgres, ClickHouse, Redis and object storage. Latitude offers Docker Compose, Swarm, Helm and Railway deployments under MIT. Failproof AI separates its local policy runtime from its Cloud platform: the CLI runs policies without a server, while Enterprise self-hosting provides tracing, querying, evaluations, automated failure analysis and alerts on Kubernetes with ClickHouse and PostgreSQL. See self-hosted agent evaluation platforms for the full comparison.

When Not to Self-Host

If the reason for self-hosting is data residency rather than cost, Future AGI's enterprise page lists deployment into your own AWS, GCP or Azure account and a full air-gapped option, run with them. If the reason is cost, compare the machine and the on-call time against the managed plan, which starts free with 50 GB of storage and unlimited seats. A 16-core production box and the people to look after it are not free either.