latchkey.dev

The problem

CI/CD is where modern engineering teams actually feel pain. GitHub Actions is powerful but opaque: pipelines fail for reasons buried in logs, cloud spend creeps with no attribution, and security regressions slip through because nobody has time to audit every workflow. Teams either over-invest in a platform team or quietly accept the waste.

We kept watching the same story play out, at startups and at enterprises. Nobody owned the pipeline, so the pipeline owned everyone.

What we built

latchkey sits on top of your GitHub Actions and gives the pipeline a brain. An agentic AI backend watches every run and answers three questions a platform engineer would otherwise answer by hand:

• Cost, where is cloud spend going, and which jobs are wasteful?
• Security, what vulnerabilities and misconfigurations just entered the pipeline?
• Performance, which steps are slow, flaky, or redundant?

The goal isn’t another dashboard. It’s self-healing, surfacing the fix, not just the finding, and opening the PR when you let it.

See it live

Embed not loading? Some browsers block cross-site frames, open latchkey.dev in a new tab ↗.

Architecture

A static landing page and onboarding flow (which I designed and built end-to-end) sits in front of an agentic backend that ingests workflow telemetry, reasons over it, and proposes concrete changes. The product is wired the way my resume reads: secure by default, observable, and built to scale without a platform team babysitting it.

My role

I co-founded latchkey and lead it as COO. I led customer acquisition end-to-end: the outreach, the demos, and the conversations that turned early users into paying customers. I also owned the public landing page and onboarding flow, the first thing every user touches, while collaborating with engineering on the AI agent backend integration that does the heavy lifting, plus the go-to-market: pricing and the LAUNCH raise.

Results

• Scaled to $5K MRR.
• Secured $25,000 in pre-seed funding from LAUNCH at a $1M valuation, validating that the product measurably reduces cloud waste and accelerates deployment speed.

Why it matters here

latchkey is the founder half of the story: I don’t just architect secure infrastructure for enterprises, I ship a product that sells, on my own. The same instincts (secure, observable, fast) show up whether the customer is a federal agency or a startup’s CI pipeline.