Luke Clossman · available for Linux / infrastructure roles

Linux-first systems, self-hosting, troubleshooting, automation

Luke Clossman builds
practical systems.

I build and maintain Linux systems, backend services, self-hosted tooling, and AI-assisted workflows that need to work in real life.

View the work Start a conversation

Selected work unfolds below.

Linux-first systems thinkingSelf-hosted deployment pathsTroubleshooting across layersPractical local AI toolingBackend and web implementationOperational clarity over noiseLinux-first systems thinkingSelf-hosted deployment pathsTroubleshooting across layersPractical local AI toolingBackend and web implementationOperational clarity over noise

Selected work

A guided look at the work

One active case study, with the rest kept in the background until you pull them forward.

Production web system

The First Medicine

Production ecommerce work for a live wellness brand, handled with a bias toward safe change and operational clarity.

Pricing, checkout behavior, backend/frontend changes, and production-safe updates all had to be made without creating fragile fixes or breaking the storefront.

I worked across application behavior, pricing and payment-related changes, backend/frontend implementation, and operational fixes that needed to stay safe in a live environment.

A more stable and maintainable business-facing system, built around real use instead of portfolio-style demo work.

Node.jsExpressPostgreSQLDockerfrontend web stack

Applied AI infrastructure

Local AI Workbench

A Linux-based local LLM environment tuned to stay usable, reproducible, and practical on AMD hardware.

Local AI stacks often look clean in demos and messy in practice, especially when hardware limits, serving choices, and UI layers all interact.

I set up and iterated on local model-serving workflows using tools like llama.cpp, Ollama, and web UI layers, with attention to compatibility, routing ideas, and day-to-day usability.

A local AI environment that is useful for real experimentation without turning into a pile of disconnected tools.

UbuntuDockerllama.cppOllamaOpen-WebUIAMD GPU tooling

Automation and orchestration

Dogbot Personal AI Systems

A self-hosted assistant stack exploring orchestration, memory, automation, and chat-based workflows.

An assistant becomes useful only when hosting, orchestration, memory, workflow logic, and interface design all work together.

I have been designing a stack involving VPS hosting, Docker, n8n, PostgreSQL, reverse-proxy style deployment, and bot-oriented workflows while testing orchestration patterns for more persistent behavior.

An evolving assistant architecture grounded in control, iteration, and practical deployment instead of AI hype.

DockerVPSn8nPostgreSQLreverse proxybot integrations

Core capability

Linux Troubleshooting and Systems Work

Hands-on debugging across service failures, deployment breakage, device weirdness, and runtime bugs.

A lot of technical value comes from diagnosing the weird failure that blocks progress and figuring out what layer is actually broken.

I regularly troubleshoot Linux environments, USB/device issues, Docker failures, dependency conflicts, service startup problems, access issues, and runtime bugs across hardware, software, and infrastructure.

This is one of my strongest differentiators: I can stay calm in ambiguity, isolate the problem, and move a system back toward reliability.

LinuxDockerSSHservicesruntime debuggingsystem diagnostics

Independent delivery

Self-Hosted Portfolio Stack

A lightweight self-hosted site built to stay inspectable, easy to update, and fully under my control.

I wanted a portfolio that reflected how I actually like to build: lightweight, understandable, and independent rather than hidden behind platform abstractions.

I designed and deployed the site myself, handled hosting, HTTPS, reproducible updates, and the deployment path so it stays easy to inspect and maintain.

A small but clear example of self-hosted delivery and operational taste.

AstroUbuntuCaddyHTTPSdeployment scripting
Visit site

Capabilities

Core strengths, revealed more selectively

Core strengths first. The details open only when you want them.

01
Infrastructure & Systems Linux-first environments, self-hosting, containerized services, access, networking basics, and reproducible deployment work.
open
LinuxUbuntuDockerNginxSSHDNSdeployment workflowsself-hosting
02
Backend & Data Business logic, web services, data-backed application work, and systems that need to stay maintainable after shipping.
open
Node.jsExpressPostgreSQLAPI integrationconfiguration-driven systemsproduction-safe changes
03
Automation & AI Tooling Applied AI infrastructure and workflow design with a bias toward local control and useful automation.
open
BashPythonn8nOllamallama.cppOpen-WebUIlocal LLM workflowsmodel-serving experiments
04
Troubleshooting & Operations Diagnosing service failures, dependency problems, device issues, runtime bugs, and weird edge cases.
open
service debuggingruntime issuesdependency failureshardware/software integrationaccess control conceptsdocumentation

About

How Luke Clossman works

Practical, systems-oriented, and calm in the messy middle.

reliabilityclaritydebuggabilityend-to-end ownership

I do my best work where Linux, deployment paths, debugging, and practical implementation all meet. A lot of that came from building for my own projects and business needs, which pushed me toward safer changes, clearer setups, and systems that stay understandable after shipping.

Professional direction

Strong fit for Linux and infrastructure support, systems administration, technical support engineering, backend-platform implementation, and technical operations.

What I value

  • I like owning the full implementation path when setup, reliability, and debugging all matter.
  • I am comfortable in the messy middle between “it should work” and “it actually works.”
  • I care about clear configs, sane deployment paths, and debuggable failures.
  • I am most useful on ambiguous technical problems that need end-to-end figuring out.

Contact

Open to practical technical work

I’m interested in Linux, infrastructure, support engineering, backend implementation, and technical operations roles. If your team needs someone practical and comfortable figuring things out end-to-end, I’d like to hear about it.

Email Luke

Best first contact: the role, team, or problem space.