← All work
Operating Releap
Engineering intelligence platform
Answers as-built questions from a connected codebase, and verifies that written acceptance criteria are actually satisfied by the code that claims to satisfy them.
The problem
Product plans and shipped code drift apart silently. Every planning tool in the category — including the two I know best, Aha! and Jira — treats the plan as the source of truth and has no idea what the code actually does.
My role
Founder, architect, and sole engineer. Product strategy, pricing model, information architecture, and every line of Go and Svelte.
Decisions worth defending
- Read-only by default against customer repositories. Write-back is a separate, admin-granted permission, and the constraint shapes what the product is allowed to be.
- Deterministic engine computes every figure; the model writes prose over figures it is handed and never calculates them. A plan with hallucinated numbers is worse than no plan, because a PM would commit it.
- Every claim in the interface carries a file-and-line receipt. If it cannot be cited, it is not shown.
Where it stands
Operating with paying customers. SOC 2 Type I attestation (Security) issued July 2026, clean opinion.