On-Prem Enterprise

For customer-managed deployments inside your own VM, datacenter, or air-gapped environment, Caura ships a separate on-prem distribution that wraps the platform in a one-VM Docker Compose stack and a Caura-issued license file.

Repository: github.com/caura-ai/memclaw-onprem — that repo's README.md and docs/ are the canonical install / day-2 / upgrade reference. The summary below is a pointer.

What it gives you

• A single-VM Docker Compose stack (docker-compose.yml in the repo).
• A signed license.key — required; the platform refuses to start without one.
• Connected (pulls from ghcr.io/caura-ai/*) or fully air-gapped (load images from a tarball — airgap-load.sh).
• Backup / restore scripts (scripts/backup.sh, scripts/restore.sh) covering Postgres, Redis, RabbitMQ, .env, and the license file.
• Tag-driven, reversible upgrades (upgrade.sh) on Docker named volumes.
• A redacted support-bundle workflow for talking to Caura support.

Quickstart — connected VM

curl -sL https://onprem.caura.ai/install.sh | bash

The installer runs preflight checks, generates secrets, writes /opt/memclaw/.env, pulls pinned images, brings the stack up, and prints the URL of a first-run wizard where an admin uploads the license and creates the first account.

Quickstart — air-gapped VM

# Transfer memclaw-onprem-<version>.tar.gz to the VM (USB, SCP, etc.)
./airgap-load.sh /path/to/memclaw-onprem-<version>.tar.gz
./install.sh --offline --license /path/to/license.key

The tarball bundles MemClaw services plus upstream bases (Postgres/pgvector, Redis, RabbitMQ), so docker compose never needs to pull.

Silent / unattended install

Every value can be supplied via CLI flag, MEMCLAW_* env var, or a single config file:

./install.sh --config /etc/memclaw/install.conf --non-interactive

See install.conf.example for the full template.

Prerequisites

• Ubuntu 24.04 or equivalent.
• Docker ≥ 24 and Docker Compose v2.
• 16 GB RAM minimum, 200 GB disk for Postgres + Redis + RabbitMQ + room for memory growth.
• A DNS record pointing to the VM and a TLS cert (cert.pem + key.pem) for that hostname.
• A Caura-issued license.key.

When on-prem is the right pick

• You need a contract, signed builds, and SLAs.
• You require a fully air-gapped install with no calls home.
• You have data-residency or compliance requirements that rule out the managed deployment.
• You want platform-tier features (multi-tenant gateway, audit retention, SSO).

The OSS Self-host is the right pick if you only need the engine and are happy operating it yourself under Apache 2.0.

Day-2, upgrades, troubleshooting

Live in the on-prem repo:

• docs/install.md — connected install
• docs/install-airgap.md — air-gapped install
• docs/day2-ops.md — backups, restore, log rotation
• docs/upgrade.md — sequential-minor upgrade path, rollback
• docs/troubleshooting.md
• docs/security.md, docs/TLS.md, docs/logging.md

Pricing and evaluation

For pricing, sizing, and an evaluation copy of the on-prem distribution and license: contact the Caura team.