For a self-hosted CI runner for GitHub Actions, the strongest matches are actions/runner (The GitHub Actions Runner is the official, self-hosted agent), myoung34/docker-github-actions-runner (This Docker image runs a self-hosted GitHub Actions runner) and getsops/sops (This is a secret-encryption tool for configuration files, not). gaia-pipeline/gaia and finsys/dockhand round out the shortlist. Each is ranked by relevance to your query, popularity and recent activity.
Tools and configurations for deploying private infrastructure to execute custom GitHub Actions workflow jobs securely.
The GitHub Actions Runner is the application that executes workflow steps in a GitHub Actions pipeline. It runs each step of a workflow automatically to build, test, and deploy software, serving as the execution engine for automation defined in GitHub repositories. The runner supports self-hosted deployment, allowing you to install and run the application in your own environment rather than relying on GitHub-hosted machines. This gives you control over the hardware, software, and network configuration where workflows execute.
The GitHub Actions Runner is the official, self-hosted agent that executes workflow steps on your own infrastructure, giving you full control over hardware, software, and networking for private builds — and it inherently supports multiple platforms, containers, and encrypted secrets via GitHub.
This project provides a containerized execution agent designed to host automated workflows for version control platforms. It functions as a self-hosted runner that automatically registers with a central service upon startup and terminates after completing a single job, ensuring that every task runs in a clean, isolated environment. The system distinguishes itself through its focus on ephemeral lifecycle management and security. By utilizing a non-root execution model, it enforces least-privilege principles during job processing. The runner supports dynamic configuration through environment va
This Docker image runs a self-hosted GitHub Actions runner in a container, which fits the core requirement, though it may need additional configuration for features like autoscaling or secret management.
This tool is a command-line utility designed to manage sensitive data by encrypting specific values within structured files such as YAML or JSON. By protecting only the sensitive portions of a file while leaving the structure intact, it ensures that configuration files remain readable for version control systems and automated workflows. The utility provides a secure development workflow by transparently decrypting files into memory for editing and automatically re-encrypting them upon saving, which prevents plaintext secrets from being written to the local disk. It supports a variety of encry
This is a secret-encryption tool for configuration files, not a self-hosted runner that connects to GitHub Actions to execute builds—it handles secrets but does not run CI/CD workflows itself.
Gaia is a polyglot pipeline orchestrator and continuous integration and delivery automation platform. It functions as a multi-language workflow engine that coordinates the movement and transformation of data by executing tasks written in different programming languages through a dependency graph. The platform distinguishes itself with a visual pipeline configurator for mapping function arguments via a management portal and a secure secret manager that uses ciphers to encrypt passwords and tokens. It further automates the software lifecycle by cloning repositories and recompiling applications
Gaia is a general-purpose CI/CD pipeline orchestrator, not a runner that connects specifically to GitHub Actions; it automates builds and deployments but lacks the acting-as-a-self-hosted-Actions-runner capability this search requires.
Dockhand is a multi-host Docker manager and container management interface used to control the lifecycle of containers, images, volumes, and networks. It functions as a Docker Compose orchestrator and GitOps deployment tool, enabling the synchronization of application stacks directly from remote Git repositories. The project distinguishes itself as an enterprise Docker access controller, providing role-based access control and identity verification through OIDC, LDAP, and multi-factor authentication. It secures sensitive data using AES-256-GCM encryption for credentials at rest and handles na
Dockhand is a multi-host Docker manager and deployment orchestrator, not a GitHub Actions runner—it manages container lifecycles and GitOps deployments but does not connect to GitHub Actions as a self-hosted runner for executing CI/CD jobs.
Kubernetes controller for GitHub Actions self-hosted runners
actions-runner-controller is a Kubernetes operator that manages and auto-scales self-hosted GitHub Actions runner pods, so it helps you run runners on Kubernetes rather than being the runner itself—you still need the official runner agent—making it a close enabler for your use case but not the direct runner software you asked for.
Sidekick is a command-line tool that provisions bare VPS servers, transfers Docker images, manages secrets, and orchestrates zero-downtime deployments across single or multiple server instances. It handles the full deployment pipeline from a local machine, building container images locally and transferring them directly to the server without requiring a remote container registry. The tool distinguishes itself through an integrated approach to security and automation. It encrypts environment variables locally using SOPS and Age keys, then decrypts them on the server at deploy time for runtime
Sidekick is a deployment orchestration tool that provisions servers and manages containers and secrets, but it does not act as a GitHub Actions runner—it has no integration with GitHub Actions to execute CI/CD jobs.
This tool is a command-line runner that executes automation workflows locally within isolated container environments. By parsing workflow definition files and translating them into executable shell scripts, it allows developers to validate pipeline logic and configuration changes directly on their machines before committing code to a remote repository. The runner distinguishes itself by providing a simulation engine that mimics remote CI triggers and event payloads, enabling the testing of complex conditional logic without requiring cloud infrastructure. It supports granular control over the
act is a CLI tool for locally simulating GitHub Actions workflows in containers, but it does not actually connect to GitHub Actions as a self-hosted runner to execute private or sensitive builds — it is designed for offline testing and validation rather than continuous delivery.
Buildbot is a Python-based continuous integration framework and distributed build orchestrator. It functions as a build automation engine that coordinates the retrieval of source code, the execution of build steps, and the reporting of results through a central controller and a network of remote worker agents. The system is distinguished by a plugin-based extensibility architecture and a master-worker distribution model. It allows for dynamic build modification at runtime and supports a pluggable database backend for persisting system state and historical build data. The project covers a bro
Buildbot is a general-purpose continuous integration framework with a master-worker model, but it is not designed as a self-hosted runner that connects specifically to GitHub Actions, so it does not squarely fit the intent.