Docker path

The self-hosted stack is intended to run as a small set of services: a web front end, a Worker-compatible transform service, and an async execution backend for formal models. Container images will later be published with a reference docker compose file.

Binary path

Teams that prefer direct binaries should be able to deploy the CLI, worker service, and VPS service separately. This mode is useful for controlled environments where container adoption is restricted.

Operational notes

Self-hosting guidance will later cover cache layers, persistence, endpoint routing, and provenance retention. The goal is to keep the public and private deployment models aligned at the contract level.