A hybrid local/cloud platform connecting troubleshooting context, structured IT knowledge, runbooks, coding agents, and operational integrations.
Active engineering and integration work
LM Studio
Local LLMs
OpenAI Codex
OpenCode
Git
REST APIs
Useful AI assistance depends on structured context, repeatable workflows, and a clear path for review.
01Operational context
02Structured knowledge
03Local inference
04Cloud escalation
05Review
An engineering platform for IT work
Hermes brings troubleshooting assistance, documentation generation, runbooks, ticket context, and automation into a hybrid local/cloud workflow. Its purpose is to make real operational knowledge usable across repeated technical tasks.
How the pieces connect
Structured project knowledge and runbooks supply context. Local inference through LM Studio supports local model workflows, while cloud AI and coding agents provide an escalation path. Git branches and worktrees isolate engineering changes for review.
What I worked on
Organized IT and project knowledge for troubleshooting, documentation generation, and repeatable engineering workflows.
Used LM Studio, OpenAI Codex, OpenCode, Git branches/worktrees, and API integrations across local and cloud tasks.
Developed Make.com workflows that transform RepairDesk active-ticket data and enriched context into structured JSON inputs.
Investigated missing or malformed API responses and retained human review around consequential operational actions.
Current scope and boundaries
The platform includes real integration development alongside experiments. This does not mean every automation is deployed in production or that generated recommendations are authorized actions. Herdr is a separate project focused on the reliability of coding-agent execution and review.
What I worked through
Much of my work has been getting the pieces to communicate: preparing context, handling bad API responses, choosing a model, and keeping code changes separate until they’ve been reviewed.
Examples describe engineering methods. Client identities, endpoint identifiers, credentials, and ticket contents are omitted.
I use Qualys to identify systems that need patches, configure deployments, and investigate failed or unclear results. I check installed updates and follow-up scans before considering a finding resolved.
Auditing ESXi and network monitoring, correcting safe configuration issues, validating discovery, and documenting the exceptions that still need investigation.
Production monitoring review
PRTG Network Monitor
VMware ESXi
SSL/TLS
Auto Discovery
Need help with something similar?
Facing a similar technical problem?
This is an example of my experience, not an endorsement from an independent client. If you need similar help, take a look at my services or send me a description of the problem.