I build platforms that run real businesses.

Wappify is the multi-tenant commerce platform behind every store above. One PostgreSQL database on Supabase serves all of them: row-level security keeps each tenant's data isolated, one schema keeps migrations sane, and per-tenant configuration drives each storefront's branding, catalog, and checkout. Custom domains route through Cloudflare's edge with wildcard routing — kimopack.wappify.store and wakoode.com resolve to the same codebase, which reads the hostname and serves the right store.

Onboarding a new tenant is a row in a database, not a new deployment. When I ship a feature or fix a bug, every store gets it at once. Nothing above is a demo: these are real businesses taking real orders on infrastructure I designed, built, and operate.

ToTalkTo is a 3D AI companion you speak to out loud. I built the entire real-time pipeline: your voice is transcribed, the transcript goes to an LLM grounded with retrieval over the companion's knowledge, and the answer streams to text-to-speech while a Unity-rendered avatar speaks it with synchronized lip movement.

No single stage is exotic — the engineering is in the loop: keeping transcription, retrieval, inference, synthesis, and rendering inside a latency budget that still feels like conversation, and degrading gracefully when any stage runs slow. I own every layer, from API orchestration to the C# animation code. Full-stack usually stops at the browser. Here it ends at a character's mouth.

Before my own platforms, I shipped software with no tolerance for failure. At Everteam I built mobile apps for the Lebanese government — used by real citizens, in production. For a Ministry of Defense I built secure messaging: encrypted messages, files, and audio, reviewed to a standard where "mostly secure" does not exist. I delivered systems for Saudi governmental entities under strict compliance and formal acceptance processes.

Government work teaches habits startups rarely do: requirements you cannot negotiate away, security reviews that assume a capable adversary, releases that go through committees instead of CI. That discipline is why the platforms I run today hold up — and why I'm comfortable being the engineer of record.