Theo
Okafor.

Real-time fleet dispatch dashboard · Full-stack lead

A mid-size courier company was running dispatch off a whiteboard and a shared spreadsheet — drivers got assignments by phone call, and the office had no idea where any of the 140 vans actually were. Driftline replaced all of that with a live map, drag-to-reassign routing, and per-driver mobile views. The decision that mattered most was choosing WebSockets over polling for position updates: at 140 vehicles pinging every 3 seconds, polling would have meant ~47 requests/second of mostly-redundant traffic, so we built a single WS gateway backed by Redis pub/sub, with Postgres as the durable store and a reconciliation job that replays missed frames on reconnect. Dispatch latency dropped from "whenever someone called" to under 400ms end-to-end.

• React
• TypeScript
• Node.js
• PostgreSQL
• WebSockets
• Redis

Fast static-site build service · Creator / maintainer

Kiln is a build-and-deploy service for static sites and docs — push a repo, get a URL in seconds instead of minutes. It exists because the free tiers of the big CI platforms queue small builds behind enterprise jobs, and a 40-page docs site should not wait eight minutes to ship. The key technical decision was writing the build orchestrator in Go with a warm pool of pre-started Docker executors instead of cold-booting containers per job: cold starts dominated everything else, so keeping 20 warm sandboxes in rotation cut median build time from 96s to 11s. Output is shipped straight to Cloudflare Workers assets, and a Redis-backed job queue keeps the whole thing to a single $40/mo VPS for the first 400 users.

• Go
• Redis
• Docker
• Cloudflare Workers
• esbuild

Double-entry accounting API for SaaS · Backend architect

Ledgerlite gives subscription businesses a hosted double-entry ledger — every invoice, refund, and payout lands as balanced journal entries instead of mutable balance columns, so you can always answer "why is this number what it is." Two SaaS teams I'd worked with had both hand-rolled (and both broken) their own revenue tracking, and the API is the extraction of that lesson. The decision that mattered most was refusing to store balances at all: balances are computed on read from an append-only entries table with covering indexes, which makes drift between "the number" and "the history" structurally impossible. It costs a few milliseconds per read and buys an audit trail that reconciles to the cent — the right trade for money data.

• Node.js
• Fastify
• PostgreSQL
• Prisma
• Docker

Offline-first hiking companion PWA · Solo build

Trailhead is a progressive web app for day hikers: save a trail at home, and the map tiles, elevation profile, and gear checklist all work at the trailhead with zero bars of signal. It came out of losing a downloaded PDF map on a phone that had frozen in the cold — a native app would have solved it, but the pitch was that a web page could do the same job without an app store. The critical decision was treating IndexedDB as the source of truth rather than a cache: map tiles and GPX routes are versioned and pinned per-saved-trail, so a sync failure can never evict data you're relying on in the backcountry. Service worker updates are deferred until the app is closed, which keeps a mid-hike refresh from swapping the shell out under you.

• React
• Vite
• Workbox
• IndexedDB
• MapLibre GL
• Tailwind CSS