Not a list of technologies I have read about. All of this runs in production on servers I built and still maintain — which is why I can tell you when technology is genuinely the answer, and when it is an expensive way of avoiding the real problem.
The hands-on side — diagnosing and rebuilding real physical systems, from the wiring in the wall to the app that runs on top of it.
A live engagement: a 20-unit building whose 2014 entry system failed with no documentation. Fluke-tracing undocumented conduit, diagnosing the TekTone/Altronix hardware, and building an ESP32 controller plus a tenant app. Read the case study.
Designing small-business and residential networks and then installing them — cabling, terminations, right-sized IP plans, and mapping undocumented systems with a meter instead of a guess.
The systems everything else runs on — designed, deployed and operated end to end.
Managed virtual private servers joined to a private mesh network, with automated provisioning, identity integration, monitoring, backup and a documented exit path. Customers get their own environment without operating it themselves. Read the case study.
A control plane that takes a new node from bare host to a fully configured, TLS-terminated, SSO-integrated application stack without manual steps — including per-job tokens, health verification and rollback.
Centralized authentication across every hosted application using Authentik, with OIDC clients, federated login and per-service access policy.
Self-operated detection and vulnerability management — SIEM, host monitoring, intrusion prevention and scheduled scanning across the estate.
Off-grid and resilient communications devices.
Off-grid communication hardware for Meshtastic and MeshCore networks — solar nodes, repeaters and portable kits built for operation with no infrastructure, no subscription and no cell coverage.
A single mesh device combining LoRa messaging, local services and a self-contained power system — intended for deployment where conventional connectivity is unavailable or unreliable.
Applied AI systems, built and run on owned hardware rather than rented APIs.
An agent platform and orchestration backend running against local models on owned GPUs, with a tool-calling runtime, job scheduling and a web interface.
Retrieval-augmented knowledge infrastructure — a vector-backed document store and API used to ground AI systems in real organizational content instead of guesswork.
A queueing layer that shares a finite pool of GPUs across inference, image generation and training workloads without jobs trampling each other.
Production applications built for real customers and real transactions.
A full e-commerce storefront on a headless commerce backend, with print-on-demand fulfillment integration, custom React front end and automated order sync.
A federated social platform with on-device translation, multi-protocol follow adapters and a video pipeline — built to interoperate with existing networks rather than replace them.
An artist platform with provenance tracking, verification, commissions and federation services running as independent microservices.
A local barter and marketplace where the unit of exchange is not always money. People list what they have and what they want, and the system matches trades within a real geographic area, favoring nearby exchange over shipping across the country.
Self-hosted Mastodon, Pixelfed, PeerTube, Matrix and Bluesky PDS instances — operated as a single interconnected estate with shared identity and monitoring.
Communication for an audience that has no patience for jargon.
A published children’s picture book — a true story about a three-legged deer, written under the pen name Jeffrey Lebowski. Different audience, same discipline: take something real and make it land for the reader in front of you.
Clients hire me to work out what is actually wrong. This page is here so you know that when the answer turns out to be technical, I can build it rather than just recommend it.
