Draw a pipeline, push code, and watch it build, deploy, and roll back on its own: Pipewright is a self-hosted CI/CD platform delivered as one static binary. Pipelines are drawn on a two-level canvas of stages and jobs, then run with matrix builds, sidecar databases for tests, manual approval gates, and typed parameters validated at trigger time. The pipeline can also live in the repository as a per-branch .pipewright.yml file, and triggers cover webhooks, schedules, branch to environment mapping, and chained pipelines. Builds run isolated inside containers with cached dependencies and a content-addressed artifact store, and JUnit and Cobertura reports feed quality gates that stop bad code before deployment. Deployment is agentless over SSH: health checks gate a zero-downtime cutover, failures roll back on their own, and environments track their active version with one-click rollback and promotion toward production. Deployed services receive HTTPS domains through a managed Caddy proxy with automatic certificates, path routing, and load balancing, and each pull request gets a throwaway preview address with its own certificate. The operations side watches host CPU, memory, and disk, manages containers and networks across servers, and opens terminals in the browser. Notifications route by event to Slack, email, WeCom, DingTalk, Lark, or a webhook, approvals arrive as signed links, and the four DORA metrics are computed out of the box. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

GoCD treats delivery as a pipeline you can see: every commit enters a sequence of stages, passes or fails in the open, and travels from first build to production deployment along one visible, traceable path. Stages split work into jobs that run in parallel on a fleet of agents, so unit tests, integration suites, packaging, and security scans finish together instead of queueing behind each other. Pipelines connect with fan-in and fan-out dependencies, meaning a release pipeline waits for every upstream component to pass before it assembles them, and one library build can feed a dozen services. The value stream map draws that whole web on one screen, from the triggering commit through every stage to deployment, and any run can be compared with another to spot exactly what changed. Materials watch Git, Subversion, or Mercurial repositories and start pipelines on new commits, while artifacts produced by one stage are fetched, versioned, and promoted by the stages after it. Environments group pipelines and agents so test and production stay isolated, resources tag agents by capability, and elastic agents appear on Docker, Kubernetes, or cloud hosts only while work exists. Pipeline definitions can live in YAML or JSON inside a repository, changing through code review like the software they deliver, and templates keep repeated release patterns consistent across teams. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

With 7,300+ GitHub stars and active releases through version 3.17, Woodpecker CI is the community-driven fork of Drone CI that kept the entire platform open source under Apache 2.0 — delivering a lightweight, container-native CI/CD engine that runs on minimal resources while providing enterprise-grade pipeline automation. Every pipeline step executes in an isolated Docker container, ensuring reproducible builds with zero host contamination and clean teardown after each run. Define workflows in simple YAML configuration files with step dependencies, conditional execution via when filters, service containers for databases and caches, and matrix builds that test across multiple language versions, platforms, or database engines simultaneously. Deep forge integration connects to GitHub, GitLab, Gitea, Forgejo, and Bitbucket via OAuth and webhooks, triggering pipelines on push, pull request, tag, deployment, and cron events. The plugin ecosystem inherits compatibility with the Drone plugin library — over 100 plugins for Docker builds, S3 uploads, SSH deployment, Slack and Telegram notifications, Helm deployments, and more. The server-agent architecture separates the web UI, API, and scheduler from pipeline execution, enabling horizontal scaling by adding agents across multiple machines or architectures including ARM. Secrets management supports global, organization, and repository-level scopes with approval workflows for forked repository pipelines. The admin web UI provides user management, agent monitoring, and queue control. Docker Compose deployment provisions the complete stack in under five minutes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

When a commit lands, a timer fires, or a pull request opens, Concourse runs the matching jobs in fresh containers and draws the entire CI/CD pipeline as a live graph you can read at a glance. Pipelines are plain YAML files that tie resources such as git repositories, registries, and buckets to jobs made of get, put, and task steps, so the same file behaves the same on every installation. Resources are checked continuously for new versions, webhooks can request an immediate check, and a version can be pinned when something needs to stay put. The dashboard lists every pipeline by team with status colors, a filter box, favorites, and a high-density view, while build pages stream colored logs and let you rerun a build with the exact same inputs. The fly command line sets pipelines, runs one-off tasks against local files from your laptop, and opens a shell inside the container of a failed step. A set_pipeline step lets pipelines configure other pipelines, and instance vars create a family of related pipelines, such as one per pull request. Teams keep projects separate and can be tied to a GitHub organization, credentials arrive at run time from Vault, CredHub, AWS, or Kubernetes, and policy rules can block disallowed images. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.