GitReaper

A local-first Git workflow tool for reviving branches as live Docker previews, comparing agent attempts side by side, and planning safe cleanup without uploading source code.

Role
Product design, full-stack engineering, and infrastructure
Delivery
Local daemon + cloud control plane
Status
Active showcase
GitReaper homepage introducing local previews of agent branches and its separate Cloud service.

01 / How it works

The system, drawn end to end.

LOCAL MACHINE · SOURCE NEVER LEAVESDOCKER PREVIEWSRepositorystale/…agent/attempt-1agent/attempt-2feature/…abandoned:3101:3102:3103Compareside by sideCleanup planreviewed, then appliedGITREAPER / BRANCH REVIVAL
  1. 01

    Local-first trust

    Source stays on the developer’s machine while the interface provides a coherent operational view.

  2. 02

    Compare the result

    Rendered previews and branch context make it easier to judge working software, not just commit messages.

  3. 03

    Safe by design

    Cleanup remains planned and reviewable, with destructive actions separated from discovery.

02 / The problem

The operating problem behind the interface.

Long-running repositories accumulate stale branches, abandoned agent attempts, and uncertain cleanup decisions. Existing Git tooling shows history, but rarely gives teams a safe way to revive and compare the actual applications behind that history.

03 / The approach

A product model designed around the decision.

GitReaper treats every branch as a reviewable product state. It can revive branches as isolated Docker previews, place competing attempts side by side, and keep cleanup as an explicit plan instead of an automatic destructive action.

04 / Engineering scope

The system behind the product surface.

  1. 01Next.js and React control surface backed by a Fastify service
  2. 02Prisma-backed state for repositories, attempts, previews, and cleanup plans
  3. 03Docker-based branch revival with a local daemon and cloud control plane boundary