Cloudflare

What I build on Cloudflare Workers

I’m Ibrahem Hasaki, and I build backends, relays and static sites on Cloudflare Workers. It’s also where I’ve made mistakes I can show you.

  • Nujoom, an Arabic-first children’s learning platform, runs on Hono and TypeScript on Workers with its data in D1. I ported it there from Express and SQLite on 2026-08-17.
  • The model API Nujoom needed was refused from Syria at the network level. A small Worker forwarded the requests from Cloudflare’s edge, which is reachable, and held the API key so the client never had it. The relay went away once the backend moved to Workers.
  • nemo curly, an Arabic catalog and routine quiz for a curly-hair shop in Syria, is a static Astro site served as assets on Workers. The owner edits it from /admin, and if a build fails, Cloudflare keeps serving the previous deploy.
  • I added an 86-line Worker that served markdown to agents. It worked, and I deleted it in under three days, because it was the first code to run on a page request on my site, and a script that throws would have been an error on the home page.
  • With Encrypted Client Hello on, my site timed out in the browser on my connection in Syria and loaded through a VPN. curl still returned 200. I turned ECH off for the zone.
  • My rule was that only main reaches production. Until 2026-10-31, a Workers Builds trigger sent every branch push to production too.
refused from Syriaclientmodel APIWorker at the edgeholds the API key

I build websites for businesses, remotely, at UTC+3. Email: ibrah5em.hasaki@gmail.com.