15+ years architecting production systems at scale: Fortune-500 data infrastructure to garage-lab innovations. Same rigor, both rooms.
Each engagement draws from one or more of these. Nothing is bolted on after the fact: security, observability, and a graceful retire path come standard.
Systems that move billions of records with high availability, fault tolerance, and a deploy script that fits on one screen.
Pipelines that ingest, transform, and serve: real-time and batch, without a cloud provider on the bill.
REST and WebSocket APIs with auth, rate limiting, and monitoring baked in from the first commit.
AI and data on resource-constrained devices. Custom protocols, mesh radios, salvaged hardware where it makes sense.
Production-grade ML: sub-100ms inference, multi-provider orchestration, the unglamorous plumbing that keeps it safe in prod.
Most engagements start as a short scoping call, then drop into one of the shapes below. Hybrid arrangements are fine. Say so up front.
Fixed scope, defined deliverables
Best for: Specific initiatives with clear requirements
Flexible, as-needed expertise
Best for: Technical guidance and architecture review
Dedicated monthly support
Best for: Ongoing partnership, continuous improvement
The same rhythm every time. Discovery is unbillable. If the work doesn't fit, I'll say so before we sign anything.
Understand the problem deeply before proposing solutions.
Architecture that balances elegance with practicality.
Iterative development with continuous feedback.
Documentation, handoff, knowledge transfer.
A short list, but each one is the reason somebody hired me, not a hypothetical advantage.
Systems processing billions of records at Fortune-500 scale, not prototypes.
Creative problem-solving sharpened on 60-node Pi clusters and salvaged hardware.
From low-level protocols to cloud architecture to ML pipelines. One head, one accountability.
Led classified government projects under the highest security standards.
Anti-cloud means host-local, and that goes for the practice too. I’m based in Forest Hills, Michigan and work with teams across Grand Rapids, Ada, Cascade, East Grand Rapids, Kentwood, and the wider Kent County: on-site when it helps, remote when it doesn’t. AI integration, edge computing, IoT, and data engineering for West Michigan businesses that want production systems without a cloud provider on the bill.
Yes. I'm based in Forest Hills, Michigan and work with teams across Grand Rapids and Kent County, on-site or remote, on AI integration, data pipelines, and production systems at scale.
Edge computing runs data processing on local hardware instead of a distant cloud, cutting latency and cloud bills. I design and build edge and IoT systems for businesses in Grand Rapids, Ada, Cascade, and the wider Kent County area.
Yes. As a Forest Hills-based technologist I can work on-site across Kent County when it helps, and remotely for everything else.
Bring the problem. I'll bring the questions. Worst case you walk away with a clearer picture of what to do next, and that's free.