Run Armalo inside your own boundary.

The on-prem install runs the same five planes as pooled SaaS — Experience, Collaboration, Control, Agent Runtime, Observability. The platform is deployment-shape-agnostic; the only difference between pooled and on-prem is the network boundary and the operator who owns it.

See /security for the full isolation, residency, and compliance posture against this runtime.

Bring your own cloud — Kubernetes, object storage, DNS, TLS, Postgres, secrets manager. The install does not require any specific hyperscaler; the substrate is the cluster you already operate. Provision the following:

1. A Kubernetes cluster. Any conformant distribution — managed or self-hosted. The Helm chart targets the upstream Kubernetes API; no cloud-specific CRDs.
2. Postgres 16. A managed instance or a self-managed cluster. The control plane requires the standard Postgres feature set (RLS, GUC, PITR); point the deploy scripts at the connection string.
3. Object storage with a CDN in front. For artifact, attachment, and snapshot storage. The deploy script resolves the bucket from the same env file as the database.
4. A public DNS zone + ACME. Custom domains and TLS certificates are minted and rotated by the platform once the zone is delegated to it.

Production deploys run through three deterministic scripts in scripts/. Each script builds a fresh timestamped image tag (no mutable :latest), restarts the target container, and verifies the boot posture before returning.

• scripts/deploy-server.sh

  Deploys the @armalo/server image — realtime composition root, HTTP API, room credential broker, audit trail. Resolves secrets from the control-plane vault, builds a fresh timestamped tag, restarts the container, verifies /healthz before returning.

• scripts/deploy-web.sh

  Deploys the @armalo/web image — Next.js marketing + workspace UI. Shares the server.env file (same box, different port), builds the bundle locally on the box, restarts armalo-app-web, verifies the home route before returning.

• scripts/deploy-sandbox-reaper.sh

  Deploys the sandbox reaper — terminates orphaned or budget-exhausted microVMs. Required for the per-tenant cost control story; without it, stale sandboxes keep running and the bill keeps growing.

# Canonical deploy command sequence
corepack pnpm install --frozen-lockfile
corepack pnpm type-check
corepack pnpm test
corepack pnpm guards
bash scripts/deploy-server.sh
bash scripts/deploy-web.sh
bash scripts/deploy-sandbox-reaper.sh

For fully airgap-capable cluster installs, use the chart at infra/helm/:

• values.yaml

  Default installation. Public DNS, ACME certificates, default tenant policy EU.

• values-airgap.yaml

  Airgap-capable: external dependencies pinned to local registries; telemetry fully offline; chart distribution as a tarball.

• templates/

  Kubernetes manifests for control plane, agent runtime, observability, ingress, secrets, and policy engine.

helm upgrade --install armalo ./infra/helm \
  -f infra/helm/values.yaml \
  --set global.region=eu-fsn1 \
  --set global.airgap=false \
  --namespace armalo --create-namespace