Runway
Runway is where the developer/operator separation becomes concrete. Teams write a RunwayKubernetesService definition declaring what their service is and what it needs. Runway’s binding engine resolves those abstract needs against concrete infrastructure and generates static, auditable deployment artifacts: per-service Helm charts, orchestration references, and wiring configurations.
Primary contribution to Theseus: One system generates all artifacts for all environments. Self-Managed customers receive the same charts GitLab uses internally. New services plug into the existing model without bespoke distribution packaging. Operators choose their own orchestration tooling (Helm, ArgoCD, Flux) because the generated charts are self-contained and infrastructure-agnostic.