Hussein Al-Saadi

03Opmore · 2026

An AI agent platform, and the servers under it.

Co-founder & founding engineer

I owned it from the database to the deploy: the product, the agents behind it, and the machine it runs on.

1. A Next.js and TypeScript platform with client portals and a chat assistant running a tool-use loop on Claude.
2. An MCP server with a typed tool registry, shared by the assistant and a fleet of agents.
3. The agent fleet as a stateless Hono service, each agent pulling from third-party APIs over HMAC-signed REST.
4. Data in Drizzle across Turso and Postgres, with pgvector for semantic search.
5. Moved off Vercel onto a hardened Ubuntu server with Coolify, Docker and Traefik; CI, end-to-end tests, an agent eval harness, nightly backups.

Next.js · TypeScript · Claude API · MCP · Hono · Postgres · Coolify · Docker

04A personal project, on real money · 2026

A trading bot that learned to do less.

It started as an AI picking crypto trades every thirty minutes. It traded live, and it lost to simply holding Bitcoin. So instead of tuning it until it looked good, I built a replay of the exact live rules over years of real exchange history, and let the numbers decide.

1. Four fast strategies failed their replays. The research said why: at fifteen-minute horizons crypto mostly reverses.
2. Rebuilt it slow: hold Bitcoin and Ethereum while they close above their 50-day average, cash when they don't. It may not trade a rule set that hasn't passed on history.
3. Safety runs apart from strategy: stops checked every five seconds, and a panel that shows when each part last actually ran.

05Independent · 2019 to now

Multiplayer systems, played 30M+ times.

Server-authoritative engineering in Lua, on the Roblox platform

Commissioned work inside a 500k+ member community. I was the only point of contact for every client: requirements, scope, deadlines and revisions, thirty-odd times over.

1. A modular service architecture with server and client bootstrappers, and ordered, prioritised start-up so nothing races.
2. State-machine NPCs, quest frameworks, persistence layers, and currency, inventory and permission systems.
3. Found live exploit abuse in production and shut it down with custom monitoring and server-side validation.

Lua · client-server · state machines · anti-exploit

06Freelance · 2025 to 2026

A client build, shipped and in use.

A full application for a paying client: the architecture, backend logic, API design and a structured handover. It went live and into active use.

I ran the requirements and planning myself, kept feature creep out, and moved the work from favours to formal invoices under my own company.