Products

Ship faster. Sell smarter. Break less.

The playbooks, books, and templates I use to run production systems at Lockstep and to ship the WorkIQ family of edge apps. Some are free to read online. Some are paid because they took a long time to compile and are worth what they cost.

Playbooks

2
Waitlist

The WorkIQ Playbook

Ship internal edge apps on Bun · Hono · Astro · Cloudflare in a weekend.

The house-stack scaffolder, the base/overlay model, the flock harness, and the whole opinionated toolkit I use to ship WorkIQ apps at Lockstep. Includes the create-workiq generator, a starter monorepo, and eight canonical patterns from the shop floor.

12 chapters 180 pages
BunHonoAstroCloudflareDurable Objects
Who it's for: Engineers running MSP tooling, internal tools, or edge-native SaaS side-projects.
In draft

MSP Security Runbook

The 100 checks that separate a graded MSP from an audited one.

A field guide to Microsoft 365, Entra ID, and Azure security posture assessments — pulled from real Storm-Hunter, Entra Sentinel, and DSPM engagements. Every check has why, how, and the fix.

Entra IDM365DSPMRapid7
Who it's for: MSP engineers, IT managers, and vCISOs.
In draft

Books

1
Pre-order

Agent Systems on Cloudflare

Build an autonomous agent loop that develops features end-to-end, with human supervision.

The full architecture behind LTG OS: Cloudflare Workers as the orchestrator, GitHub as the gatekeeper, NoteIQ as the backlog. Covers the branch-creation / file-write / PR-creation loop, cost accounting, safety rails, and how to keep humans meaningfully in the loop.

14 chapters 220 pages
AI AgentsCloudflareMCPLLMOps
Who it's for: Practitioners building agentic systems in production.

Templates

1
Available

WorkIQ Starter Repo

The canonical WorkIQ scaffold — free.

Everything the `create-workiq` generator emits, in a public repo. Bun runtime, Hono API with a synchronous driver-blind repo, Astro house console, Cloudflare wrangler config, a flock harness, and CI wired for canary deploys.

BunHonoAstro
Who it's for: Developers who want to see the stack before committing to the book.

Why free-to-read + paid PDF?

Because the writing exists to be read. If a chapter helps you at 2am and you don't have $29 lying around, that's still a win for me — you'll remember it. The paid PDF is for the people who want a portable copy, want to support the work, or want a signal that the whole thing has been proofed for print.