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.

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.

With 16,100 GitHub stars and created by Solomon Hykes (co-founder of Docker), Dagger eliminates proprietary YAML DSLs from CI/CD by letting developers write pipelines as real programs in their preferred language — then executing them identically on a laptop, in GitHub Actions, in GitLab CI, or on any machine with a container runtime. The BuildKit-based Dagger Engine runs every pipeline operation inside OCI containers, constructing a directed acyclic graph where each node is cached by default, parallelized automatically, and produces bit-for-bit reproducible outputs regardless of execution environment. Native SDKs generated from the GraphQL API schema provide Go, Python, TypeScript, PHP, Java, .NET, Elixir, and Rust developers with full type safety, IDE autocomplete, and the ability to unit-test CI pipelines using the same testing frameworks as application code. The module ecosystem enables cross-language composition where a Python team can invoke a Go team's build functions without learning Go, while filesystems, secrets, git repositories, and network tunnels are passed between functions as strongly-typed objects. Pipeline operations cache at container-layer granularity with content-addressed deduplication, and the interactive REPL enables step-by-step pipeline debugging with live container inspection. Host dependencies are explicit and strictly typed, eliminating implicit environment coupling that causes "works on my machine" failures. 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.

Used by over 100,000 organizations and ranked first in the Gartner Magic Quadrant for DevOps Platforms, GitLab is the open-core DevSecOps platform that delivers the complete software development lifecycle — from planning and source code management through CI/CD, security scanning, and monitoring — in a single self-managed application. The built-in CI/CD engine executes pipelines defined in YAML with parallel jobs, directed acyclic graph scheduling, multi-project pipelines, and auto-scaling runners on Docker, Kubernetes, or bare metal. Merge requests provide inline code review with approval rules, code owners, merge trains for serialized merging, and five merge strategies including fast-forward and semi-linear history. The integrated container registry stores Docker images alongside code, while the package registry supports npm, Maven, NuGet, PyPI, Conan, Go, and generic packages. Issue boards with epics, milestones, and labels enable agile planning, while the built-in wiki and GitLab Pages provide documentation hosting and static site publishing. Security scanning in the Community Edition includes basic SAST, secret detection, and container scanning running as pipeline jobs. The Omnibus installer bundles Rails, Puma, Gitaly, Workhorse, Nginx, PostgreSQL, Redis, Sidekiq, and Prometheus into a single package installable in minutes, while Docker and Helm chart options support containerized and Kubernetes deployments. GitLab Duo AI assists with code suggestions, merge request summaries, and vulnerability resolution. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With over 15,100 GitHub stars and seven years of battle-tested production use, OneDev replaces entire DevOps toolchains — GitLab, Jenkins, Jira, Artifactory — with a single Java application that runs comfortably on a 1-core 2GB server for medium-sized projects. The platform unifies Git hosting with ANTLR-powered language-aware code search and symbol navigation, pull request workflows with configurable branch protection rules and required reviewers, and customizable issue tracking with scripted state transitions that automatically advance issues when code is committed, builds pass, or deployments complete. The GUI-based CI/CD editor creates pipelines without writing YAML, supporting typed parameters, matrix builds, job templates, cache management, and artifact publishing in a single visual interface. Jobs execute via Docker containers, bare metal shell, Kubernetes pods, or distributed agent pools, with web terminal access for live debugging and the ability to pause running jobs for inspection. Built-in package registries handle Docker images, npm packages, Maven artifacts, NuGet libraries, PyPI wheels, and RubyGems without external infrastructure. AI users can be assigned to issues and pull requests to autonomously implement features, review code, fix CI/CD failures, and resolve merge conflicts. The automated Kanban board supports rule-based card movement, time tracking, timesheets, and service desk ticket creation via email. Cluster deployment enables project replication across servers for high availability and horizontal distribution for scalability. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With 37,400+ GitHub stars and active daily development by the Harness engineering team, Gitness is the open-source developer platform that ships Git hosting, container-native CI/CD pipelines, a Docker-compatible artifact registry, and cloud developer environments in a single Go binary consuming approximately 100 MB of RAM — compared to GitLab's 4+ GB minimum footprint. Born as the next generation of Drone CI, Gitness inherits Drone's battle-tested pipeline engine while adding complete source code management with pull requests featuring threaded code review comments, suggested changes, required reviewer approvals, and merge strategies including squash and rebase. Branch protection rules enforce mandatory pull requests, minimum peer reviews, passing status checks, and force-push blocking. Pipelines use Drone-compatible YAML syntax with stages, steps, and service containers, triggered automatically on code changes with results displayed directly in pull request checks. The built-in container registry eliminates the need for separate Harbor or Docker Registry deployments, supporting Docker image push and pull plus Helm chart storage. Gitspaces provide on-demand remote development environments configured via industry-standard devcontainer.json files. Encrypted secrets management with Gitleaks-powered secret scanning blocks commits containing hardcoded credentials. One-click migration imports existing GitHub Organizations and GitLab Groups, automatically converting GitHub Actions and GitLab CI pipelines to Gitness YAML. The REST API with OpenAPI specification enables programmatic management of all resources. 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.

Pipedash unifies pipelines from twelve CI/CD providers into one self-hosted dashboard for watching statuses, reading job logs, and triggering, rerunning, or cancelling runs without opening each provider's site. Connect GitHub Actions, Gitea Actions, GitLab CI, Azure DevOps, Bitbucket, Buildkite, Jenkins, Tekton, ArgoCD, FluxCD, Komodo, or Prow, and every workflow lands in one list grouped by repository. Filters narrow by status, provider, organization, or time range, and saved views with rules, sub views, and pins give each team its own shortlist. Run history records each attempt with its commit, branch, actor, and duration, and opening a run reveals its jobs and a searchable log viewer that streams live output. Trigger forms load the workflow's own inputs, pipeline variables, or job parameters from the provider, so parameterized runs start with real values. Reruns reuse the original inputs, GitHub runs can restart only failed jobs, and stuck builds can be cancelled singly, in bulk, or by repository. Metrics charts track duration, success rate, and run counts per pipeline by hour, day, week, or month with P95 and P99 values. A notifications inbox gathers failures, degraded workloads, long running builds, and provider outages, while health panels place status pages beside the pipelines they describe. Every dashboard action is a REST API route under /api/v1 with bearer authentication, provider tokens stay encrypted at rest, and the server sends no telemetry. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Stop hoping your AI coding assistant remembers to plan before it codes, test after it implements, and review before it ships. Archon wraps Claude Code, OpenAI Codex, and other AI agents inside structured YAML workflows that enforce the same development process every single time. Define your pipeline as a directed acyclic graph of nodes (AI tasks, shell scripts, approval gates, loops) and Archon handles the orchestration: resolving dependencies, running independent nodes in parallel, passing artifacts between steps, and isolating every run in its own git worktree so five bug fixes can proceed simultaneously without conflicts. Ship with 17 pre-built workflows covering everything from "idea to merged PR" to automated conflict resolution, or author your own by committing YAML files to your repository's .archon/workflows/ directory. The web dashboard, launched with archon serve, provides a conversation interface with real-time streaming, a visual drag-and-drop workflow builder for creating DAG pipelines, step-by-step progress monitoring for every run, and a unified sidebar aggregating conversations from CLI, Slack, Telegram, and GitHub into one view. An NLP router parses natural language requests and automatically selects the right workflow. Structured JSON output schemas let you enforce typed responses from AI nodes, with validation and auto-repair for providers that lack native schema support. Every workflow file is version-controlled, portable, and reviewable in pull requests, so your entire team runs identical processes from day one. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With over 3,700 GitHub stars and growing adoption among teams tired of managing complex orchestration platforms, Dagu delivers a complete workflow engine as a single Go binary that requires no external database, message broker, or framework installation. Define directed acyclic graphs in declarative YAML — specifying dependencies, schedules, retries, timeouts, approvals, and notifications — while keeping existing shell scripts, containers, and tools completely unchanged. The built-in Web UI provides live pipeline visualization, per-step log streaming, run history browsing, artifact previewing, manual retry controls, and workflow YAML editing without SSHing into servers. Execute steps as shell commands, Docker containers, Kubernetes Jobs, SSH remote commands, SQL queries, or HTTP requests, with conditional branching and parallel execution handled natively. The integrated Model Context Protocol server exposes dagu_read, dagu_change, and dagu_execute tools, enabling AI agents like Claude, Codex, and Cursor to inspect workflow state, preview YAML modifications, and control runs through authenticated endpoints. The harness.run executor lets external coding-agent CLIs operate inside DAG steps with full scheduling and approval gate support. Scale beyond a single machine with the distributed worker mode, which dispatches tasks to remote nodes via gRPC with automatic label-based routing and worker selection. Deploy with Docker, the official Helm chart for Kubernetes, or a simple binary download requiring only a Linux, macOS, or Windows host. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPLv3 licensed.

Zeabur is a self-hosted web platform that deploys and runs your services on your own Kubernetes cluster, presenting the cluster as simple projects and services instead of raw manifests. Every change starts as a readable plan listing the exact fields it will write and who owns them today, and nothing is applied until you confirm it. When something breaks, Zeabur says so in plain words and points at the fix: a worker that restarted fourteen times gets a button straight to the logs from the run before the restart. You deploy from Git repositories, from an uploaded folder or ZIP archive, or directly in the dashboard, then follow live logs, open a terminal inside a container, and watch CPU and memory move over time. Projects are namespaces and all state lives in Kubernetes objects, so there is no Zeabur database to back up, and uninstalling the platform leaves your Deployments, Services, and Ingresses running untouched. Companion pieces add passkey sign-in for kubectl with tokens that expire in minutes, image builds from Git through a BuildKit operator, and a catalog of cluster components and app templates. 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.

The open-source PaaS with 55,000+ GitHub stars and the largest one-click service catalog in its class — Coolify gives you the Vercel push-to-deploy workflow on a dedicated server you control. Connect a GitHub, GitLab, Bitbucket, or Gitea repository and every push builds and deploys automatically via Nixpacks, a Dockerfile, or Docker Compose, with Traefik or Caddy reverse proxying, automatic Let's Encrypt certificates, and per-branch preview deployments with their own URLs. Databases — PostgreSQL, MySQL, MariaDB, MongoDB, Redis — provision in a few clicks, and a catalog of 280+ one-click service templates covers WordPress, n8n, Grafana, MinIO, Plausible, Ollama, and more. One dashboard manages the entire server, with Docker Swarm available for clustering multiple nodes. Backups go to any S3-compatible storage with one-click restore, and a full API supports CI/CD integration. All configuration lives on your own server, so resources keep running even if you stop using Coolify — no vendor lock-in by design. Running on a dedicated VPS with guaranteed CPU, RAM, and SSD, full root access via SSH and browser console. Apache 2.0 licensed.

Artifact Keeper serves as a self-hosted universal software artifact repository that consolidates container images, application libraries, and infrastructure bundles under a unified management control plane. Software development teams can publish and resolve dependencies using their existing build tools, including Docker, Helm, npm, PyPI, Maven, Cargo, NuGet, and Terraform without installing proprietary client plugins. Remote repositories act as transparent pull-through caching proxies for public upstreams like Docker Hub and PyPI, accelerating internal CI/CD build speeds while insulating production pipelines from external registry outages. Virtual repositories combine multiple local, remote, and third-party endpoints into single URLs, resolving packages across prioritized internal teams and public registries automatically. Automated security scanners evaluate incoming packages for Common Vulnerabilities and Exposures using Trivy and Grype engines, assigning letter grades and enforcing quarantine policies to block vulnerable binaries before production release. Administrators can sign package metadata with cryptographic GPG keys, configure peer mesh replication across geographic regions, and manage team permissions using OpenID Connect, SAML, and granular access tokens. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Think of Zot as the registry equivalent of a well-run warehouse: OCI images and artifacts come in, get cataloged, checked, and shipped back out to any compliant client. The bundled web interface lets you browse repositories and tags, inspect image details, and copy ready-made pull commands for Docker, Podman, and Skopeo instead of memorizing registry URLs. Sync extensions mirror upstream registries such as Docker Hub on a schedule or on demand, which keeps air-gapped and rate-limited environments supplied without manual image ferrying. Scrubbing walks the storage in the background comparing blocks against their SHA-256 checksums, so silent bit-rot gets caught by the registry instead of by a failed production deploy. Signature verification with Cosign and Notation checks that images came from who they claim, search answers queries across the catalog, and CVE scanning flags vulnerable images before they spread. Prometheus metrics, a management API, and webhook events cover the operations side, while the minimal image strips everything but the distribution spec for embedded or high-security deployments. 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.

The first container registry to reach CNCF graduated status with over 29,000 GitHub stars since VMware open-sourced it in 2016, Harbor transforms the basic Docker Distribution into a hardened enterprise registry with vulnerability scanning, supply chain signing, multi-datacenter replication, and project-level access control out of the box. Trivy scans every pushed image against the NVD, GitHub Advisory Database, and distribution-specific vulnerability feeds, with scan-on-push policies that block deployment of images exceeding configurable severity thresholds. Artifact signing through Cosign keyless signatures and Notation enforces content trust policies ensuring only cryptographically verified images reach production clusters. Policy-based replication synchronizes images and Helm charts between Harbor instances across multiple datacenters using repository, tag, and label filters with automatic retry and bandwidth throttling — enabling hybrid-cloud and disaster-recovery topologies. The RBAC model isolates projects with per-project quotas, robot accounts for CI/CD automation, webhook notifications, and audit logging that tracks every pull, push, delete, and configuration change. LDAP, Active Directory, and OIDC authentication integrate with existing identity providers, while the proxy cache transparently caches images from Docker Hub, Quay, and other upstream registries to reduce pull latency and rate-limit exposure. The RESTful API with embedded Swagger UI, tag retention policies, garbage collection scheduling, and immutable artifact rules complete the lifecycle management. Deploy via Docker Compose or Helm Chart on Kubernetes. 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.