DocsHow KHUB compares
CI/CD & deployment
Every forge ships native pipelines now. What separates them is orchestration depth, DORA visibility, and who owns the compute.
Every forge here now ships some form of native pipelines. What separates them is job-orchestration depth (DAGs, approvals, cross-repo triggers), whether deployment/DORA data is visible without upgrading, and whether compute is something you own or rent by the minute.
| Feature | KHUB | GitHub Actions | GitLab CI/CD | Gitea Actions | Forgejo Actions |
|---|---|---|---|---|---|
| Native CI/CD included | |||||
| Visual pipeline / job-graph editor | — YAML only | ||||
| DAG job dependencies with conditional run rules | Limitedbasic | Limitedbasic | |||
| Tag-based runner routing | ✓ (labels) | ✓ (tags) | |||
| Manual approval gates before a job runs | Limitedprivate repos need $ Team+ | Limitedfull protected envs are $ Premium | |||
| Cross-repository downstream pipeline triggers | Limitedmulti-project features are $ Premium | ||||
| Environments with one-click rollback | Limitedre-run previous run | ||||
| Built-in DORA metrics dashboard | ✓ every tier | — third-party needed | $Ultimate | ||
| Automatic secret redaction in job logs | ✓ masked variables | Limited | Limited | ||
| Vendor-hosted runners (no hardware of your own) | — self-hosted by design | ||||
| Monthly CI minutes cap | none — your hardware | Limited2,000–50,000 min, then billed | Limited400 min free, then billed | none (self-hosted) | none (self-hosted) |