I'm Oussama Rahmouni, a senior crawling and anti-bot engineer. I build extraction systems that survive the stacks designed to stop them: TLS fingerprinting, session engineering, mobile API reverse engineering, proxy orchestration. In my current role, that work runs at 10–15M items a day across 23 European markets.

RahmouniDev is my studio, registered in the US as RahmouniDev LLC. It runs as a factory: every product is designed to own its own complexity and operate without babysitting. APEX crawls without manual intervention. Al Bayrouni publishes on its own pipeline. The output changes; the operating standard doesn't.

For clients, the factory builds custom extraction for targets engineered to refuse it: sites behind enterprise WAFs, mobile apps with undocumented APIs, pipelines that have to stay up rather than work once. If a normal team can't get the data, that's the work I take.

Working on something that needs this kind of engineering? Let's talk.Direct engineering with the person who builds it. No middlemen, no handoffs.

Technical_Specialization

Engineering Depth.

Backend_Platform

  • Node.js & TypeScript (strict)
  • NestJS & Event-Driven Architecture
  • WebSockets & Real-Time APIs
  • REST, GraphQL & Custom Protocols
  • PostgreSQL, Redis & MongoDB

Data_Intelligence

  • Large-Scale Web Extraction
  • TLS Fingerprint Shaping — JA3/JA4, uTLS, curl-impersonate
  • Behavioral Anti-Detection Engines
  • CAPTCHA Solving & Token Banking
  • Multi-Market Data Pipelines
  • Mobile API Reverse Engineering

Cloud_&_Infrastructure

  • AWS
  • Docker & Containerized Services
  • Git, GitHub & GitLab CI/CD
  • Linux Server Administration
  • Nginx & Process Management

Security_&_Systems

  • Proxy Networks & Rotation Systems
  • Protocol Engineering (MTProto, WA)
  • Frida & Dynamic App Instrumentation
  • WAF Bypass & TLS Probing

Engineering_Philosophy

How I Build.

Systems should own their own complexity — if you need a diagram to explain the control flow, the code is wrong

Real expertise is knowing which layer a problem belongs to: network, protocol, application, or data

Anti-patterns in the wild are a roadmap — once you can break a system, you understand how to build its replacement

The ungettable data is the most valuable — solve the access problem first, the storage problem is solved

Technical_Projects

Building Systems.

APEX — Crawl Infrastructure Platform

Production crawl platform built on anti-detection primitives — TLS fingerprint shaping, identity & session trust, a browser-solver token bank, and a self-managed residential proxy mesh. Its live vertical is food-delivery intelligence: a reverse-engineered mobile API tracking thousands of venues daily. New verticals are configuration, not new engineering.

Node.jsTypeScriptPostgreSQLProxy RotationTLS Fingerprinting

The detection and transport components behind APEX are open source — whichwaf, ja3lab, impersonate, tokenbank, app2api, driftwatch. The platform's edge is the integration, not the secrecy.

Open Source — The Public Toolbox

Six published tools from the APEX component layer: whichwaf (anti-bot detection), ja3lab (TLS fingerprints), impersonate (browser-perfect HTTP), tokenbank (challenge solver bank), app2api (mobile API extraction), driftwatch (defense-change monitoring). Pinned on GitHub.

TypeScriptNode.jsPythonSQLiteGitHub Actions

Public code is the proof. Every tool is tested, documented, and built from production use — a recruiter or client can inspect the engineering before a single call.

Al Bayrouni — Technical Content Platform

Long-form technical writing from first-hand implementation. Crawl architecture, anti-detection systems, security engineering. MENA region focus. Not tutorials. The technical record of work in progress.

Next.jsNestJSPostgreSQLStripeDocker

Writing forces precision. Every article is a post-mortem or deep dive on something built, broken, and understood — not summarized from documentation.

Consulting — Crawl & Data Infrastructure

Selective client engagements: anti-bot architecture, data pipeline design, Node.js/TypeScript systems. Fixed scope, senior-level only. The work is the same technical depth as APEX — applied to a client's specific data problem.

Node.jsTypeScriptPostgreSQLAWSNestJS

Every engagement starts with the actual problem — not a generic service package. If the problem is getting reliable structured data from systems that resist it, that's the specific thing built here.