Compare
Carbon Forge and AEGIS vs CI/CD platforms
Classic CI checks out a repository and runs a script. With AEGIS, a pipeline is a durable workflow whose states are agents, container steps and human approvals, reading Carbon's record without a clone.
Carbon Forge and AEGIS, one platform, row by row. Every row cites a public page.
Side by side
| Topic | Carbon Forge + AEGIS | CI/CD platforms |
|---|---|---|
| Definition | Carbon Forge + AEGISAEGIS workflows are durable state machines whose states are agents, container steps and human approval gates. AEGIS docs | CI/CD platformsGitHub Actions automates build, test and deployment pipelines from workflows in the repository. GitHub Docs |
| Configuration | Carbon Forge + AEGISAEGIS container steps run any Docker image as a deterministic, isolated step inside a workflow. AEGIS docs | CI/CD platformsGitLab CI/CD is defined by a .gitlab-ci.yml file at the project root. GitLab Docs |
| Getting the code | Carbon Forge + AEGISA step fetches a lane's composed tree with trees.materialize, each entry by a signed URL, or downloads a perspective as one deterministic archive. Carbon Forge docs | CI/CD platformsA Jenkins Pipeline is a suite of plugins that runs continuous delivery pipelines from a Jenkinsfile. Jenkins User Handbook |
| Approval | Carbon Forge + AEGISAn AEGIS human approval state pauses the run; the approver reads lanes.diff and approves with lanes.approve, bound to the lane's exact state. Carbon Forge docs | CI/CD platformsMerge request approvals gate merging in GitLab. GitLab Docs |
| Events | Carbon Forge + AEGISSigned webhooks report a landing, a merge, a cut, a push and a revert, written in the same transaction as the change. Carbon Forge docs | CI/CD platformsGitHub Actions workflows build and test every pull request. GitHub Docs |
| Steps | Carbon Forge + AEGISA container step runs any Docker image as a deterministic, isolated step, so any existing build or test tool is a step. AEGIS docs | CI/CD platformsGitHub Actions workflows are built from reusable actions. GitHub Docs |
Try it on your own work.
Sources, all read on 2026-10-22: AEGIS docs, “What are Workflows?” · GitHub Docs, “Understanding GitHub Actions” · AEGIS docs, “Building CI/CD Pipelines” · GitLab Docs, “Get started with GitLab CI/CD” · Carbon Forge docs, “The full workflow with AEGIS and Zaru” · Jenkins User Handbook, “Pipeline” · GitLab Docs, “Merge request approvals” · Carbon Forge docs, “Source control on the substrate”