Skip to content
Inspired By Frustration
// selected projects · shipped · each one measurable
[ 03 / projects ]

Things that shipped. Each one measurable.

Visual proof first. The index is for scanning what shipped; each project page carries the fuller problem, build, and architecture story.

apphandoff.com · mcp-beast.ai · contextcapture.ai · ci fleet · leading momentum

[ workshop ledger ]

Shipped from the workshop.

productslive

AppHandoff — MCP bridge for AI-built apps

The layer that keeps humans in the loop.

apphandoff.comNext.jsReactTypeScriptSupabase
productslive

MCP Beast — governed MCP control plane

One proxy. Every MCP. Full control.

mcp-beast.aiReactTypeScriptSupabaseMCP
productslive

Context Capture — bug reports with the page included

Bug reported. AI understands. Fix ships.

contextcapture.aiNext.jsTypeScriptSupabaseShadow DOM
infralive

Infra GHA — self-hosted GitHub Actions on Fly.io

The runner fleet under the product work.

infra.inspiredbyfrustration.comFly.ioGitHub ActionsBunDocker
clientlive

Roeland — local service workflow and referral surface

A focused surface with measurable referrals.

roeland.inspiredbyfrustration.comLovableReactGA4UTM Attribution
[ 04 / how these get built ]

Architecture, sketched.

The coordination layers and pipelines behind the work — the same systems that run this studio.

System architecture of AppHandoff: agent clients and a tool catalogue feed one MCP server that routes projects, runs the ticket lifecycle, and delivers work to Supabase, GitHub, the portal dashboard, and Mailgun.
AppHandoff · MCP platform

AppHandoff: agent clients and a tool catalogue feed one MCP server that routes projects, runs the ticket lifecycle, and delivers the work.

Platform architecture of MCP Beast: one authenticated endpoint handling discover, schema, and invoke, backed by a server-side registry, credential injection, and full audit.
MCP Beast · gateway

MCP Beast: one governed endpoint — discover → schema → invoke — with a server-side registry, credential injection, and full audit.

CI/CD pipeline: a pull request runs on ephemeral Fly runners through a required CI gate, auto-merges on green, and deploys live, with fail-fast retries.
CI fleet · deploy

The self-hosted CI/CD fleet: pull request → ephemeral Fly runners → required gate → auto-merge → live.

// next / your build

The next entry on this page could be yours.

start a build