01
Ordinary infrastructure
Linux, Docker, and Compose are the production contract. Kubernetes is not a prerequisite or a hidden destination.
About ReaperCI
Delivery infrastructure for ordinary servers and accountable automation.
ReaperCI is an Apache-2.0 delivery and operations control plane for Docker applications on Linux VPSes. It connects Git, BuildKit CI, an OCI registry, protected deployments, rollback, and live server operations without requiring Kubernetes.
Why it exists
Small teams should not need a platform department to ship safely.
Running a few Docker applications often creates an awkward choice: assemble source hosting, CI, a registry, approval workflows, deployment scripts, monitoring, and rollback from separate systems, or adopt a platform that changes the operating model completely.
ReaperCI focuses on the missing loop between a commit and a healthy server. The same evidence is available to the dashboard, CLI, API, MCP clients, human operators, and constrained automation.
Operating principles
The boundaries are part of the product.
02
One evidence chain
Commits, builds, images, approvals, health, observed state, and rollback targets stay connected.
03
Human authority
Agents may prepare, diagnose, and request. Protected environments decide who can approve production.
04
Constrained operations
The outbound connector exposes typed operations instead of an unrestricted shell from a managed cloud.
05
Own the exit
The complete core can be self-hosted, and repositories, state, registry data, artifacts, and configuration remain exportable.
06
Claims follow evidence
Implemented controls, release validation, managed-service plans, and open assurance gates are reported separately.
Project shape
Open core first. Managed service only after the gates close.
The self-hosted core is licensed under Apache-2.0. A managed offering is being validated for operators and small teams that want the control plane hosted while keeping their servers and runtime under their control.
Managed pricing, capacity, support terms, and public availability are not final and are not currently offered for purchase.
See what is implemented and what remainsStart with the product
Review the installation path and security model.
The packaged documentation covers installation, upgrades, backups, connectors, pipelines, CLI and MCP use, and operational recovery.