Git and provider adoption
Native HTTP and SSH repositories plus connected-provider adoption, webhooks, commit status, and import workflows.
Product roadmap
A roadmap with gates, not launch theatre.
ReaperCI is in active beta hardening. Capabilities that work today, assurance work still in progress, and longer-term direction are kept distinct. Sequence may change as release evidence develops; no date on this page is a commercial commitment.
Available in the core beta
The operating loop exists end to end.
These capabilities are implemented in the current repository and remain subject to beta hardening.
BuildKit CI and registry
Dependency-aware pipeline steps, cache mounts, artifacts, resource controls, cancellation, visible queues, and an embedded OCI registry.
Governed deployment
Protected environments, scoped secrets, health policy, promotion history, drift inspection, and exact-image rollback.
Live VPS operations
Direct SSH or outbound connector transports with health, metrics, Docker state, logs, events, and typed operational actions.
Agent interfaces
CLI, MCP, OpenAPI, scoped service accounts, structured build triage, and attributed audit events.
Operational recovery
Install, upgrade, backup, restore, registry maintenance, and documented incident and migration paths.
Hardening now
The next milestones are evidence, not surface area.
Managed availability remains gated even when the underlying feature already works in the self-hosted core.
- 01Independent review
Close security, infrastructure, legal, and trademark gates without treating internal validation as external assurance.
- 02Live recovery evidence
Complete provider, backup, restore, disaster-recovery, connector-rotation, and rollback drills on production-like infrastructure.
- 03Capacity and isolation
Prove tenant isolation, hosted compute controls, quota behavior, storage lifecycle, and single-node capacity targets.
- 04Launch operations
Finish support, incident, release, onboarding, privacy, and billing operations before opening public managed-service access.
After the gates close
Managed convenience without surrendering the runtime.
Future managed work is aimed at hosting the control plane, isolated build capacity, storage, and operational coordination while customer servers remain connected through constrained outbound operations.
Plan names, capacity, pricing, support terms, and public availability remain unfinalized.
Deliberately outside the current scope
Focus is a product decision.
- Kubernetes orchestration
- Issue tracking and pull-request review
- White-labeling
- Enterprise SAML
- Multi-region high availability
- A general unrestricted remote shell
Follow the evidence
Use the core today. Treat managed service as planned.
The documentation is the source of truth for current installation and operating behavior. Managed-service statements remain product direction until deployability and approval are proven.