Self-Hosting

Agorio Cloud can run on your own infrastructure — useful when data residency or air-gapped deployment rules out the hosted version. There are two supported paths.

Docker Compose

The repository’s docker/ directory contains a Compose stack and a cloud.Dockerfile that build and run the Cloud app alongside its dependencies. The Cloud app emits a Next.js standalone build (gated on the DOCKER_BUILD env var) so the image stays small.

# from the repository root
docker compose -f docker/docker-compose.yml up --build

See docs/guides/self-hosted.md in the repository for the full environment-variable list and first-run steps.

Helm chart

For Kubernetes, the charts/agorio-cloud/ directory contains a Helm chart:

helm install agorio-cloud ./charts/agorio-cloud

Migrations

Self-hosted deployments own their own database migrations. Cloud carries its own drizzle.config.ts, so you apply the schema (including the RBAC and audit-log tables) against your Postgres instance with:

cd cloud && npm run db:push

Hosted customers get migrations applied automatically; only self-hosted operators run this step.