Skip to main
Omar Nagy.
next: Receipts

One person.Whole systems.Live in production.

AI Product Engineer. I build the parts a company usually hires a team for, and then the thing runs without me.

Email me

5 of 5 systems answering. Read 04:14 UTC, re-read every ten minutes.

  1. MedPrüf: answering, status 200. card checkout + recurring billing, unattended.
  2. Blink: answering, status 200. loyalty, menu, NFC, events.
  3. RetailOS: answering, status 200. multi-tenant, Arabic-first.
  4. Harmonia: answering, status 200. a salon its owner runs himself.
  5. NeuraScale: answering, status 200. agent-readable: llms.txt, openapi, WebMCP.
  6. Crema: retired, switched off on purpose. retired, backend decommissioned.

Read from the systems themselves when this page rendered, not from a file. A row that did not answer within its four-second budget shows the last hand-verified reading, dated.

Production figures

The work.

Everything below is running right now. Where it is behind a login, I say so. Where it stopped, I say that too.

MedPrüf

Own product. Live.medpruf.com ↗

Exam prep for doctors trained outside Austria who have to pass the Austrian licensing exam. Most candidates do not even know which exam they are sitting. That confusion is the top of the market, not a support ticket.

In production: it sells to strangers while I am not there. Card checkout and recurring billing run unattended. Webhook signatures are verified on receipt, and idempotency was proven under a real duplicate: ten webhooks, nine grants, no second charge.

Behind a login: the bank itself. Six UI languages, right to left included. The referral programme has never fired; I built the mechanism before the traffic existed.

10,600+questions live
Case file →
MedPrüf: Austrian medical exam-prep platform, German UI, question bank with spaced repetition.

BlinkOS

Own product. Sold new.blinkstudio.cc ↗

A café or venue has no idea who its customers are. Loyalty is a paper card that gets lost, and the menu is a print run that is wrong the week it arrives.

So: loyalty on a member card that lives on the customer’s phone, a branded menu that updates live, an NFC and QR tap layer whose destination can change at any time, and event activations with a live board. All of it feeding one customer base the venue owns. Arabic first, right to left, built for cheap Android phones on bad networks.

In production: it ran live at a graduation event with VERA Specialty Coffee. Guests self-registered in seconds, staff collected at counter speed, and the prize draws came from real registrants.

One venue, one event. Built to run cafés, salons and retail; the track record so far is a single deployment. Breadth is the direction, not the history.

RetailOS: Arabic-first cloud POS landing page, dark UI, “run the whole shop from one screen”.

RetailOS

Own product. Installed base.retailos.one ↗

A multi-tenant point of sale, storefront and back office for independent shops. Arabic first, hardware ready, and real isolation between tenants, because a leak between two shops is unrecoverable.

In production: live tenants. Now maintenance rather than growth, which is a decision and not a failure: the customer-facing layer moved to BlinkOS. Two privilege-escalation holes closed and then verified by querying the live database, not by reading the migration file.

The migration ledger once reported a fix as missing while its objects were demonstrably live. Probe the objects, never the index of the objects.

48h12 pull requests, 12 migrations, zero data loss
Case file →

Also on file.

Harmonia, a men’s luxury salon: Arabic-first landing page, gold HARMONIA wordmark on near-black.

Harmonia Salon POS

Client build. Live.harmoniacenter.com ↗

A salon operating system built for one owner. He configured his own barbers and edited his own payment settings in production, and three rounds of his feedback in Arabic became shipped fixes within days. In his hands through July and August.

Case file →

Agent-readable surfaces

Own work. Live.neurascale.org/llms.txt ↗

Most sites are invisible to agents. NeuraScale and MedPrüf carry a real discovery layer a browsing agent can find and call.

  • robots Content-Signal
  • llms.txt
  • RFC 9727 API catalog
  • openapi.json
  • WebMCP tools
  • A2A endpoint
UTURN. Advertising: bilingual EN/AR creative-production studio site, heavy yellow wordmark on black with a U-turn arrow mark.

UTURN. Advertising

Client build. Live.uturn.ad ↗

Bilingual English and Arabic with full right to left, an admin CMS the owner runs himself, installable, first-party analytics and no third-party tracker. Live on its own country domain.

Case file →

Leyla Mozayen archive

Client build, live.leylamozayen.com ↗

A working archive for a twenty-year experimental practice, run by the artist from a private studio on her phone. Shown with her permission.

Case file →