Getting Started — Overview

OpenWit is container-first. Every role is shipped as an OCI or Docker image so you can run a single monolith container on a laptop or a set of role-specific containers in production. The standard workflow is simple. You pull images locally for testing and node deployment. Your CI pushes built images to a registry as the canonical release artifacts. Your orchestrator, which is Docker Compose or Kubernetes with Helm, uses those images as the primary deployment unit.

Why Containers

• Reproducible binaries and a consistent runtime environment across dev, test and prod
• A stable dependency surface that avoids machine drift
• Easy security posture with scanning and signing, simple distribution via registries
• Straightforward local runs with docker run or docker-compose, simple scale out on Kubernetes

What you will do in this section

• Get images from a trusted registry with versioned and immutable tags
• Verify images with simple checks, security scans and optional signing
• Run Standalone Mode for local development with realistic dataflow and actor behavior
• Understand Distributed Mode so you can plan a production rollout that scales by role