Tarek Morgene
CTO, NessFlow
Tarek Morgene is a CTO and a hands-on Laravel engineer, with more than twenty years of shipping industrial-scale platforms across banking, insurance, retail and B2B startups. He is currently building NessFlow, a SaaS for visibility in search and inside AI answer engines.
NessFlow is not a one-person job, and implying otherwise would be false. The platform is built with a strong devsecops, backend and front-end team: infrastructure, processing queues, screens and code review are held by several people. The notes published here describe decisions taken together, even when a single name signs them.
They follow one rule: a figure travels with its unit, its provenance and the date it was taken, because a measurement is a dated observation rather than a property of the system. When a decision turned out to be wrong in production, the note says so.
Published under this byline
-
Laravel SEO: one registry for every URL a crawler sees
A bilingual Laravel site usually keeps four lists of the same URLs: the routes, the sitemap, the hreflang tags and the language switcher. Nothing makes them agree, and when they drift nothing breaks, which is what turns URL drift into an SEO defect rather than a bug. Ours are one table of 31 page keys, projected into every SEO surface, with the parity held in both directions by tests.
· 13 min read
-
Measuring the agentic web without trusting the user agent
A user agent string is a claim, not an identity. We built forward confirmed reverse DNS and published range checking, ran it over 39,319,497 requests on three production sites, and counted two things separately: which machine readable paths agents actually ask for, and which of the agents asking are who they say they are.
· 18 min read
-
A modern marketing site without a modern front-end stack
Our public site ships 4,323 bytes of gzipped JavaScript. No CDN, no front-end framework, no flat-file CMS, no headless CMS and no second build pipeline. It runs inside the same Laravel application as the product it sells, and one of its perfect scores turned out to be wrong.
· 11 min read
-
Blade, Inertia and Filament, on purpose
Three rendering worlds share one Laravel application: Blade for the public site, Inertia and React for the product, Filament for the admin console. We chose all three up front and would choose them again. What follows is what the seams between them actually cost, in code.
· 10 min read
-
Millions of log lines in PHP, at constant memory
We parse server access logs at around 85,000 lines per second with a peak memory footprint of 44.5 MB. That footprint does not move when the file gets bigger, and it does not move when the data gets more varied either. This is how the pipeline is built, and why we did not use a log analyzer.
· 9 min read
The subjects these pieces cover
Start with a measurement, not a promise
Run an audit on your own site and read what the engine finds. If you would rather be walked through it, book a demo: we run it on your site, with your own URLs on screen.
Access opens in waves: we email you when yours is ready.