Skip to main
Omar Nagy.
Menu
next: Receipts

One person.Whole systems.Live in production.

Product Engineer. I build full-stack software, from the interface and database to deployment. AI features, business tools and client-editable websites, built around the people using them.

Selected projectsEmail meExperience + CVLatest: Abokamar

5 of 5 systems answering. Read 21:02 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

Product engineering.

Products I have built and deployed. Each case explains the workflow, engineering decisions and limits. Client collaborations are below.

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: card checkout and recurring billing are integrated with account access. Signed webhooks and idempotent processing protect the payment-to-access workflow.

Behind a login: the bank itself. Six UI languages, right to left included. The case separates product capabilities from verified commercial results.

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

BlinkOS

Own product. Event deployment.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: a deployed point-of-sale and back-office system. The case documents tenant isolation, hardware integration and the engineering behind its workflows.

Deployment is evidence of the build. It is not a claim about current shop activity or commercial results.

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

Client work.

Websites and working tools for real businesses. Each case states the scope, collaborators and delivery stage.

Abokamar film portfolio: black canvas, restrained typography and an Enter frame. Public-page capture, October 2026.

Abokamar

Client build with WO! Studio. Public launch pending.abokamar.com ↗

A film portfolio with a private Studio for editing projects and press, saving drafts and publishing content releases.

Wael at WO! Studio led design and handoff. I built the CMS, backend and deployment. Deployed in October 2026; public launch remains pending.

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

Harmonia Salon POS

Client build. Deployed.harmoniacenter.com ↗

A salon operating system with barber management, payment settings and a back office. Owner feedback in Arabic shaped the delivered workflow. The case documents the build and handoff.

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. Deployed.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 →