Use case · CI/CD
A CI/CD host with a clear runner-to-production boundary
Sysaro treats GitLab Runner and Docker/OCI as infrastructure services while production deployment remains a separate typed workflow.
Verified against public version: 0.20.02026-09-15Factual boundary · roadmap is not presented as shipped
GitLab Runner and Docker/OCI appear in Service Fleet and use constrained lifecycle operations. Production deployment is not reduced to “docker exec”: releases have SHA-256 verification, safe extraction, structured hooks, health checks and rollback.
Responsibility boundaries
| Area | Current boundary |
|---|---|
| Runner host | Inventory, service state and constrained lifecycle |
| OCI runtime | Backend visibility and canonical workload operations |
| Artifact | Stored with exact size and SHA-256 |
| Production release | Immutable extraction + structured hooks + healthcheck + rollback |
Why CI and deploy stay separate
A runner executes pipelines, but that does not make its shell a production control API.
Sysaro keeps a separate auditable deployment model so production rollback does not depend on the history of a specific CI job.