Commercial CI/CD
Designed for customer code and deployment credentials
Hosted jobs run in per-job Linux containers, stored secrets are encrypted at rest, self-hosted pull-request work withholds scoped secrets, and audit/export controls support customer reviews. Hosted scoped-secret parity remains incomplete.
Runner isolation
Hosted jobs use per-job containers and an optional per-job Docker daemon sidecar; the host Docker socket is not mounted into the customer job container. The trusted hosted-worker container itself has root-equivalent host Docker authority and must run on dedicated infrastructure.
Secret controls
Stored secrets are encrypted at rest. Self-hosted and hosted pull-request work receive no checkout or privileged credential environment. Trusted non-pull-request hosted jobs receive checkout plus organization/pipeline/step/deployment and Shipline credentials through ephemeral step files.
Auditability
Audits capture sensitive actions with IP and user agent. Known stored pipeline secrets are masked from run logs, while token-shaped values and support details receive additional best-effort redaction.
Security review checklist
Code: source checkout uses provider apps or scoped tokens; review the documented self-hosted and hosted credential differences before allowing pull-request workloads.
Build: hosted jobs do not receive the host Docker socket; dedicated worker-host and isolation claims still require production evidence.
Release: approvals, recorded environment state, deployment credentials, and rollback records support audit review.
Customer trust controls
Workspace/compliance file generation, support diagnostics, public status, and log masking support customer reviews. Redaction is defense in depth, not permission to print credentials.