Skip to main content

Deployment Overview

Yardrail is a two-binary system — yardrail-frontend (web UI, API, gRPC server) and yardrail-worker (Temporal poller, CWL workflow execution). Both connect to shared infrastructure: PostgreSQL, Temporal, and S3-compatible storage.

The worker supports two container executors that determine how CWL tool containers are run. Your choice of executor determines which deployment path to follow.

Deployment paths​

Docker ComposeKubernetes (Helm)
Executordockerkubernetes
Best forLocal development, single-serverProduction, multi-tenant
How tools runDocker containers on the host daemonKubernetes Pods with S3 CSI volumes
InfrastructureDocker Engine, MinIO (bundled)K8s cluster, S3, CSI driver
Tool isolationDocker network mode noneCluster NetworkPolicy
Image pullingDocker daemon pulls and cachesKubelet pulls per-node
ScalingSingle worker processHPA on worker Deployment
Security modelDocker socket access (root-equivalent)RBAC-scoped ServiceAccount

Docker Compose​

The fastest way to get Yardrail running. The docker-compose.yml in the repository bundles PostgreSQL, MinIO, Temporal, and both Yardrail services. The worker runs CWL tools as sibling Docker containers on the host daemon.

Best for local development and small single-server deployments where simplicity matters more than isolation.

Get started with Docker Compose →

Kubernetes​

The production deployment path. Both services are packaged as a Helm chart. The worker runs CWL tools as Kubernetes Pods with S3 CSI inline volumes — no Docker socket needed, no root-equivalent access, and workflow Pods are first-class cluster citizens subject to RBAC, resource quotas, and network policies.

Best for production deployments where security, scalability, and operational visibility matter.

Get started with Kubernetes →

Shared dependencies​

Both paths require these external services. Docker Compose bundles them; Kubernetes deployments bring their own.

DependencyPurposeNotes
PostgreSQL v18+Frontend persistence, Temporal historyMigrations applied automatically on frontend startup
Temporal ServerDurable workflow executionSingle task queue, encrypted payloads
S3-compatible storageWorkflow artifacts, avatar uploadsMinIO for dev, AWS S3 / compatible for production

Architecture deep dives​

For details on how each executor works internally: