Case studies · production work

The systems behind the résumé.

Four client systems I lead or led, written for engineers and hiring teams: what the business needed, what I built, the decisions behind it, and where my part ends. Below them, projects that have their own public architecture pages.
Private repositories are described, never linked. Every number is counted from code, Terraform or git history; a client's business metrics stay with the client.Senior Platform Engineer · Backend, DevOps & AWS infrastructure
  1. 01

    Commerce + last-mile logistics · Mexico

    Logistika Urbana

    One platform for the stores, the warehouse, the drivers and the books.

    Principal Full-Stack Engineer (contract) · Mar 2024 — present

    of 2,372 commits on the core backend
    ~2,300
    domain modules · ~535 API routes
    26
    Terraform modules · AWS Mexico region
    11
    Read the case study
  2. 02

    K-beauty retail · vision LLM · Mexico

    Yoon Lab

    A skincare store where the AI only recommends what is on the shelf.

    Principal Full-Stack Engineer (contract), via Logistika Urbana · 2024 — present · AI skin analysis 2026

    products in the live catalogue
    371
    Korean brands
    30+
    of products tagged by skin concern
    81%
    Read the case study
  3. 03

    Logistika Urbana · native Android & iOS

    POS & driver apps

    A point of sale that keeps selling when the network does not.

    Principal Full-Stack Engineer (contract) · Dec 2024 — present

    of 171 commits on the Android POS
    144
    of 147 commits · Kotlin driver app
    147
    of 87 commits · SwiftUI driver app
    87
    Read the case study
  4. 04

    AI policy & compliance analysis · US SaaS

    LexGuard AI

    Turning a data-science team's GPU models into a multi-tenant product.

    Lead Backend Engineer, Platform & ML Integration · Oct 2025 — Apr 2026

    of 1,109 commits: top contributor in six months
    338
    of 281 commits on the main web app
    274
    GPU instances, async endpoint autoscaling
    0 → 5
    Read the case study
+Open source & public docs

Read the architecture, then the code.

Each of these has its own detail pages: architecture, docs and a live site. Open-source code links straight to GitHub; the client system links to its public docs only.

05Open source · MIT · delivery platform

Tasuki

Phase 1 of 7 done · proven locally

The delivery side of a business, as software you run in your own cloud. Your system creates a delivery over the API; Tasuki quotes a price and an ETA, dispatches the nearest courier on a real city road network, and streams the courier's position live to the customer's phone. It is sized for 1.5 million orders a month in one city and built to production standards: idempotent orders, a Kafka-backed location pipeline, written SLOs, load tests and game days.

orders/h at full design scale, on one laptop
18,144
GPS points/s, with 0 failed orders
641
p95 for POST /v1/orders under that load
20 ms
game-day plans; the first one run, with a postmortem
12
fig. 05orders · locations · operate
CLIENTSYour systemorders apiCouriergps · offersCustomertracking pageSimulatorplays the cityMONEY PATH · DJANGOordersidempotent · quotesPostgreSQLoutbox → relayLOCATION PATH · GOfleet-ingestgps → kafkatrackingsse · reads kafkadispatchoffers over sseKafka3 topics18,144 orders/hmeasured · one laptop641 gps/s · 0 failed ordersfleet-statenewest point / courierValkeycache · rebuilt from logOSRMtokyo roads · 23 wardsOPERATE · AP-NORTHEAST-1 · DASHED = WRITTEN, NOT YET APPLIEDEKS · KarpenterArgo CDKyvernoSLOs · burn raterollout gategame days
GoDjango + DRFPostgreSQLKafkaValkeyOSRMReact · MapLibreTerraformEKS · KarpenterArgo CDKyvernoOpenTelemetrySloth SLOs

The company is fictional and the merchants, couriers and customers are simulated. The AWS platform (Terraform, EKS) and the GitOps layer are written and statically checked, but not yet run on a cluster; that is deliberately the last phase.

06Fintech client · 2026 · docs public

Zero-retention AI KYC

Code private · architecture and API docs public

Identity verification an app can add with a few API calls: national ID card, selfie, proof of address and source of funds. Every document is quality-checked, read by open-weight vision models, cross-checked against the others, and passed to a compliance officer; the model never makes the decision, and nothing is kept.

two vision models: Qwen3-VL-8B and PaddleOCR-VL on one L40S
1 GPU
Terraform modules, content-addressed endpoint configs
12
API calls, each documented with a cURL example
11
GPU modes: always-on, scheduled, on-demand, off
4
fig. 06inference path · gpu lifecycle
ID documentimage · pdfFastAPI router/ping · /invocationsterraform · 12 modulescontent-addressed endpoint configsS3 weightsoffline loadSAGEMAKER · ML.G6E.XLARGE · 1× L40S 48 GBQwen3-VL-8B · FP8vLLM · fields & reasoningPaddleOCR-VLvLLM · OCR~75% gpu memory~25%Fieldsjson · validatednothing retainedGPU LIFECYCLE CONTROLLERalways-onscheduledon-demandoffidle stop after 30 min · never mid-documentCOMPLIANCE GATESdata capture: off (asserted by test)pii-redaction invariants gate cinetwork-isolated endpoint
vLLMSageMakerQwen3-VLPaddleOCR-VLFastAPIDjangoTerraformGitHub Actions OIDC

Client system: the code is private and is not linked. The architecture page, API docs and the write-up are public.

07Open source · MIT · self-hosted LLMs

Private LLM Chat

Public · docs site with five guides

Your own ChatGPT-style app, on your own GPU. Open-weight models run with vLLM on Amazon SageMaker, several per GPU, with weights loaded from S3, an optional no-internet VPC, and a GPU that switches itself off when idle. The Django and React app streams chat and handles documents, images and voice.

open-weight model families: Qwen, Llama, Gemma, DeepSeek
4
GPUs running when idle: the endpoint scales to zero
→ 0
guides, from a laptop to the full AWS stack
5
Terraform stack: ALB, CDN, ECS, SageMaker, database, CI/CD
1
fig. 07self-hosted stack
REACT APPstream · docs · images · voiceDjango APIstreaming rest · 2faWhisperOCRWeb searchSAGEMAKER · VLLMQwenLlamaGemmaDeepSeekGPUseveral models per gpuscale → 0 when idleweights from s3 · no-internet vpc optionS3 weightsofflinePrivate VPCoptionalModel Runnerlaptop · dockerTERRAFORM · ONE STACKalbcdnecssagemakerdatabasenetworkecremailcicddocs site · guides · gpu sizing · cost reference · MIT
vLLMSageMakerTerraformDjangoReactWhisperS3Cloud Run (port)

A public open-source project with a docs site. No production users or traffic are claimed; the Google Cloud Run port is early.

→For hiring teams

Platform, DevOps or AI-platform role? Let's talk.

I build and run production systems on AWS, and I deploy and operate models in them. I'm looking for a senior platform, DevOps or AI-platform role. A résumé and references are available on request.

Role
Senior Platform Engineer · Backend, DevOps & AWS infrastructure
Location
Lahore, Pakistan
Languages
English (professional) · Urdu (native) · Japanese (beginner, studying daily)
Email
contact@codewithmuh.com