Skip to content

Walter On-Prem

Bring up a local Walter stack in one command.

Download a tiny self-host bundle, pull your licensed image, and land straight in Walter's browser setup flow.

Quick install Upgrade guide

Fast first boot

The installer writes .env.deploy, checks registry access, pulls the image, and starts the stack with Docker Compose.

Browser-first setup

Walter handles bootstrap secrets automatically and lets you finish license and LLM setup in the browser after the stack comes up.

Versioned releases

Operators pull pinned image tags such as ghcr.io/matchylabs/walter:YOUR_WALTER_VERSION. Customer credentials are shared out-of-band.

Quick path

WALTER_IMAGE=ghcr.io/matchylabs/walter:YOUR_WALTER_VERSION
curl -fsSL https://onprem.walterops.com/install/install-walter.sh | \
  bash -s -- --host 192.168.1.50 --image "$WALTER_IMAGE"

That command:

  • downloads the Walter self-host bundle to ~/walter-selfhost
  • verifies the bundle checksum before unpacking it
  • prompts for registry credentials if your image pull needs them
  • writes .env.deploy
  • pulls the configured Walter image
  • starts the stack in internal-tls mode

After it finishes, open https://192.168.1.50 and complete the in-browser setup flow.

Note

Registry credentials, license keys, and any customer-specific image tags are communicated separately. This site only covers the generic operator workflow.

Choose a deployment mode

Mode Best for URL
internal-tls Private networks that still want TLS https://<host>
public-tls Internet-facing deployments with Let's Encrypt https://<host>

Start with internal-tls for private deployments, then move to public-tls once your hostname and certificate path are ready.