The problem
The operating problem behind the interface.
Building an image is only one part of delivering software. Operators also need a clear approval point, a healthy target service, release history, and a way to recover when a deployment fails.
ReaperCI
A self-hosted beta for Docker delivery on Linux VPSes, with image promotion, health checks and release history. The managed service remains in private validation.
Interface captured . The live site may have changed since.
- Role
- Delivery workflow design, full-stack engineering, and infrastructure
- Delivery
- Self-hosted VPS + Docker
- Availability
- Preview / private access
- Target
- Linux VPS · Docker + Compose
How it works
The system, drawn end to end.
Swipe to see the whole system
Make promotion deliberate
The release workflow keeps approval visible between a successful build and a production change.
Check the running service
Health checks connect the delivery result to the application that actually starts.
Keep recovery close
Release history and rollback belong alongside deployment rather than in a separate runbook.
The approach
A product model designed around the decision.
ReaperCI organizes Docker delivery around building, approval, deployment, and health checks on Linux VPSes. The self-hosted beta keeps humans in control of promotion and rollback, while the managed service remains in private validation.
Engineering scope
The system behind the surface.
- Go services with a Svelte and TypeScript control surface
- Docker and Compose application delivery on Linux VPSes
- Image promotion, health checks, release history, and rollback workflows
