Self-hosted beta · Managed service in private validation

From Git push to healthy production. Agents in the loop. Humans in control.

Build, approve, deploy, operate, and roll back Docker and Compose applications on Linux VPSes—with agents in the loop and humans in control.

Explore the self-hosted beta See the product
  • Apache-2.0 core
  • GitHub, Gitea, Forgejo, and GitLab
  • Linux amd64 + arm64
  • Docker and Compose

reaperci-demo / deployments

Live evidence
ReaperCI deployment view showing an approval gate, health state, drift status, and rollback controls
Actual ReaperCI interface · sample dataApproval, runtime evidence, and rollback stay attached to the release.
commit 8f3ca92build passedapproval recordedproduction healthy

One operating loop

Delivery stops being a pile of handoffs.

ReaperCI carries one evidence chain from a commit through build, approval, deployment, runtime health, drift, and rollback. People, agents, the UI, CLI, API, and MCP all work from the same state.

  • One release identity
  • One policy boundary
  • One operational record

Commit to production

Every transition is explicit. Every action leaves evidence.

Move quickly without turning production authority into an ambient permission.

  1. 01
    Commit

    Use native Git or connect GitHub, Gitea, Forgejo, or GitLab.

  2. 02
    Build

    Produce logs, artifacts, image digests, and provider status from one run.

  3. 03
    Approve

    Protected environments keep human authority separate from automation.

  4. 04
    Deploy

    Promote the reviewed image through direct SSH or a narrowly scoped connector.

  5. 05
    Operate

    Read health, events, metrics, logs, container state, and drift.

  6. 06
    Roll back

    Restore the exact healthy runtime image captured as evidence.

01 / Build evidence

Diagnose the failure without reconstructing the run.

See the failed step, retained logs, commit context, provider status, and last healthy evidence together. Agents can help triage while the underlying record stays inspectable.

  • Structured build steps and retained logs
  • Commit status across supported providers
  • Agent-assisted diagnosis with scoped identities

reaperci-demo / builds / 185

Failed build
ReaperCI failed build detail showing structured steps, logs, and diagnosis context
Actual ReaperCI interface · sample dataThe failed step and its evidence stay in one view.

02 / Governed deployment

Automation can prepare production. Policy decides who can approve it.

Environment rules, approval evidence, deployment comparison, health gates, and rollback state travel with the release instead of living in separate systems.

  • Protected environments and explicit approvers
  • Pre-deploy comparison and drift visibility
  • Exact-image rollback after health failure

reaperci-demo / deploys

Approval required
ReaperCI deployment view showing approval, health, comparison, drift, and rollback state
Actual ReaperCI interface · sample dataHuman approval remains an enforceable boundary.

03 / Live operations

Stay with the release after the deploy button disappears.

Inspect connected servers, container state, events, health, and resource signals without losing the commit and deployment context that created them.

  • Server and container health in one operating view
  • Typed operational actions instead of an unrestricted cloud shell
  • Runtime evidence agents and humans can share

demo-prod-1 / live operations

Healthy
ReaperCI server operations view showing health, resource metrics, events, and container state
Actual ReaperCI interface · sample dataOperations remain connected to delivery evidence.

Self-hosted first

Run the complete control plane on infrastructure you already understand.

Linux, Docker, and Compose are the production contract. Keep your forge or use ReaperCI’s native Git path, connect multiple VPSes, and retain a documented exit path.

Read the installation guide

Production contract

Runtime
Linux amd64 / arm64
Packaging
Docker and Compose
Git
Native or connected
Automation
UI, API, CLI, MCP
License
Apache-2.0 core

Managed direction

Hosted operations are in private validation.

The managed option is not available for purchase or public signup. Architecture, recovery, security-review, legal, and operational evidence must close before broader availability.

Self-hosted coreBeta releases and documentation

Available to explore

Managed serviceArchitecture and readiness validation

Private validation

Paid availabilityRequires external and operational evidence

Not open

Security by boundary

Automation gets a leash. Production gets a record.

Scoped identities, protected environments, encrypted secrets, typed connector operations, runtime evidence, and exact-image rollback reduce the authority any one actor needs.

Explore Security & TrustRead the threat model
People + agentsScoped identities
ReaperCI control planePolicy + evidence
ConnectorTyped operations
Linux VPSDocker runtime

Choose the right boundary

ReaperCI complements your forge and focuses on the governed path to a live VPS.

Compare the operating model, not a checklist frozen in time.

Forge

Gitea + Actions

Keep collaboration in Gitea; add governed delivery and runtime operations.

Compare Application platform

Coolify

Compare PaaS-style convenience with explicit approval and evidence.

Compare CI/CD suite

GitLab

Compare a broad DevSecOps suite with a focused VPS operating loop.

Compare Container management

Portainer

Compare runtime administration with Git-linked build and release evidence.

Compare
See all comparisons, including Dokploy

Start with the system you control

Take one commit all the way to healthy production.

Explore the self-hosted beta, its installation contract, and the evidence ReaperCI keeps along the way.

Open the installation guide See the roadmap