Deployment

Run it your way

Select customer-hosted packaging and an operating plan for the accepted release. A disconnected installation also needs a local model, all dependencies and offline acceptance tests.

Start free trial

Get the bundle, then install

Obtain the agreed release bundle and its installation guide from the delivery team. Verify its manifest, licence, image provenance and requirements. The commands below are a versioned reference example; use the filenames and procedures supplied for your accepted release.

cd compose
cp .env.example .env        # set ACT_HOSTNAME
docker compose up -d --wait
docker compose logs control-plane | grep -A4 "FIRST-BOOT ADMIN"

Customer-hosted deployments use packaged deployment configuration. An offline deployment requires an accepted bundle, local model and disconnected installation tests.

Day 2 operations

Agree who owns upgrades, backups and restore tests. Back up the pgdata, secrets and state volumes together; the secrets volume holds the encryption keys, so protect backups as credentials.

# Upgrade: set the new image tags in .env, then
docker compose pull && docker compose up -d --wait
# Backup: the database (keep the pgdata, secrets and state volumes with it)
docker compose exec postgres pg_dumpall -U actree > actree-backup.sql

No registry access

Where the server cannot reach the image registry, the release comes with an image archive and its SHA-256 checksum. Verify it, load it, then start the stack the same way.

sha256sum -c actree-selfhost-<version>-images.tar.sha256
docker load -i actree-selfhost-<version>-images.tar
docker compose up -d --wait

A self-hosted deployment brings its own model the same way a hosted one does.

Bring your own model — OpenAI-compatible endpoints, Ollama, Anthropic, or Cloudflare AI Gateway / Workers AI — with keys envelope-encrypted at rest.

Runtime-editable URLs

The public URLs the control plane hands to agents, and the ones it uses for the identity-provider callback, are changed from the console's Settings page — not by redeploying.

Enrollment wizard and the data-boundary view

A guided enrollment wizard, and a site view that shows exactly where data is allowed to cross the boundary, are part of the hosted control plane rather than of a self-hosted install.

Agree the deployment and operating boundary

Hosted service

Separate the hosted platform from commands executed on customer-enrolled hosts. Review the model endpoint, external processing routes and agreed support access.

Customer-hosted deployment

Assign responsibility for compute, storage, DNS, TLS, identity, model serving, backups and upgrades. A hosted model endpoint still sends its supplied context outside the local platform.

Disconnected environment

Agree the offline release, licence procedure, local inference and identity, controlled import and recovery tests before acceptance. An image bundle alone does not establish a complete disconnected service.

Host and network requirements

Confirm Linux x86_64, macOS (Intel or Apple silicon) or Windows x86_64 package availability for the selected release. Agree outbound secure host connections, administrative access and model routes; size the platform and local inference separately.

Run it your way

Start free trial