Home / Projects

Production systems I built and run myself.

Every project here started as an operational bottleneck in my own work. A demand signal buried across public forums, a broken CRM handoff, or an API key almost pasted into an AI chat window. Agents handle the repetitive work and surface the exceptions. Humans make the judgment calls.

4Production systems in active operation
189K+Market signals processed monthly by Gapfeed
64Local secret and PII patterns in API Key Leak Intercept
52AI chat hostnames watched directly in the browser
01

The projects

Four tools and platforms covering market intelligence, local agent execution, workflow diagnostics, and browser secret protection.

02

The operating loop

How these four systems connect across the full cycle from market signal to protected daily execution.

STEP 01 · FIND

Gapfeed

Scans 7 public data sources around the clock and groups repeated operational complaints into documented market gaps with source receipts.

STEP 02 · DIAGNOSE

Workflow Repair

Takes a broken automation or intake pipeline, classifies where data drops or stalls, and maps the exact repair before any code is written.

STEP 03 · EXECUTE

Elitza

Runs the agent layer on local infrastructure, keeping memory across sessions and pausing at human approval gates for sensitive actions.

STEP 04 · PROTECT

Leak Intercept

Watches 52 AI chat hostnames in the browser so API keys, tokens, and personal data are caught locally before a prompt is ever sent.

03

Shared guardrails and client work

Every system on this page obeys the same operational rules I enforce when shipping for client teams.

Rule 01
Control

Approval gates and full audit logs

Destructive actions wait for a human sign-off. Every tool call, payload, and routing decision writes to an audit trail so your team can inspect or override any step.

Rule 02
Ownership

Your infrastructure and your keys

These systems run on infrastructure you control without locking your operations inside a black-box subscription. When an agent hits an unhandled state, it stops cleanly and alerts the operator.

Rule 03
Client work

From internal builds to client deployments

The production versions of these patterns ship as fixed-scope client engagements. You can study the technical breakdowns in the system blueprints, see the numbers in the case studies, or pick up the self-serve playbooks in the store.

04

Frequently asked

Direct answers on availability, custom builds, and infrastructure ownership.

Are these projects available to use?

Gapfeed is live and free to explore. API Key Leak Intercept is live on the Chrome Web Store with full source on GitHub. Elitza is in public alpha under an MIT license, and the workflow repair intake runs on the diagnostic page.

Can you build something like this for my business?

Yes. The production versions of these ideas ship as client work through the services page. Start with the free diagnostic to find out which architecture fits your bottleneck.

Do these depend on recurring SaaS subscriptions?

No. They run on infrastructure and API keys you control. There is no black-box SaaS dependency required to keep them running.

Want this applied to your workflows?

The same architecture patterns power the systems I ship for clients. Start with a free diagnostic and get a clear read on what is broken and what to fix first.

Stay in the loop.

Technical breakdowns, new system builds, and lessons from deploying autonomous AI. One email a week, direct to your inbox.

One email a week. Leave with one click.