SOLO ENGINEERING STUDIO · RUNMODEL.DEV

Models and systems that actually run in production.

One engineer, end to end. I build ML and backend systems that hold up under real load, then hand over the repository, the runbook, and the dashboards you need to operate them without me.

01 / WHAT I DO

Six areas of work. One person accountable for all of them.

I take a problem from scope through to deployment. No handoffs between people, no one waiting on someone else's ticket.

01

Applied AI/ML

Fine-tuned, quantized models on hardware you control, instead of a growing API bill.

PyTorch · LoRA/QLoRA · llama.cpp
02

Computer Vision

Detection and tracking on live camera streams, tuned to the latency you need.

YOLO · OpenCV · FFmpeg
03

Backend & Frontend

Python backend and the frontend that ships with it, both built and maintained end to end.

FastAPI · PostgreSQL · Next.js
04

DevOps & Infrastructure

Containers, clusters, and CI/CD with tracing, so you see problems before your users do.

Kubernetes · Argo CD · OpenTelemetry
05

Embedded Systems

Software for hardware that runs unattended: sensors, controllers, edge inference included.

C / C++ · Linux · Edge Inference
06

Automation

Manual work turned into a scheduled job that reports success and alerts on failure.

Python · Bash · Docker

02 / STACK

Tools I use daily and would defend in review. Anything outside this list, I will tell you before the project starts.

Python logo
Python
PyTorch logo
PyTorch
FastAPI logo
FastAPI
Django logo
Django
Docker logo
Docker
Kubernetes logo
Kubernetes
PostgreSQL logo
PostgreSQL
Redis logo
Redis
Linux logo
Linux
AWS
OpenCV logo
OpenCV
Grafana logo
Grafana
Prometheus logo
Prometheus
CUDA logo
CUDA
Next.js logo
Next.js
MongoDB logo
MongoDB

03 / PROCESS

Durations are typical for a single well-scoped project, not a promise. Anything larger gets split into phases of this shape.

STEP 012–5 days

Scope

I agree with you what is being built, what it must do, and what is out of scope.

STEP 022–6 weeks

Build

Weekly working builds, so progress is something you can open rather than read about.

STEP 033–7 days

Test

Automated tests, load and edge cases, and a pass on the failure paths.

STEP 042–3 days

Handover

Repository, deployment, and runbook, plus a walkthrough of how to operate it.

04 / CONTACT

Tell me what needs to run.

Send a short description of the problem and any constraints you already know: deadline, budget range, hardware, existing code. If it is not something I can do well, I will say so.