00 / Night shift · Amman
Demos are easy.Production isn't.
00 / Night shift · Amman
Demos are easy.Production isn't.
01 / The work surface
Agent routing, retrieval, LLM orchestration — sketched on paper, hardened in TypeScript and PHP, shipped with a trace on every request.
02 / The architecture
Web frontend, API core, agents, monitoring — wired by streams carrying real traffic. Open a block to read its manifest.
ON CALLModel routing via OpenRouter, retrieval pipelines, and SEO/AEO generation jobs that run when content ships.
03 / The core
The record behind it: fintech platforms, supply-chain APIs and AI products answering real queries every day — led, built, kept running.
04 / The interface
Everything here exists and runs in production — including this page. The next system on the desk could be yours.
The person behind the work
I’m Bashar Ayyash, known online as Yabasha, an AI Systems Architect based in Amman, Jordan. I focus on regulated industries, AI evaluations, harness design and AI security.
yabasha.dev is my official portfolio, where I share my projects, open-source work and writing about building reliable AI and software systems.
About Bashar Ayyash, known as YabashaSystems online
What I do
Production RAG assistants and tool-using agents grounded in your docs, tickets, and databases — with citations, evals, monitoring, and guardrails. Not demos.
Laravel + Next.js systems with auth, payments, queues, dashboards, and audit trails. Built to stay stable under real traffic, audits, and team handovers.
Explore servicesNative-feel iOS and Android apps with React Native and Expo — offline sync, payment integrations, slow-device performance, and app-store-ready releases.
Mobile service detailsSelected work
Telemetry
20+
Years engineering
50+
Projects shipped
24
Articles written
10K+
AI queries served daily
Banking · MENA
Four years inside a regulated bank building production RAG and agent systems that answer in Arabic and English, with evals, guardrails and monitoring designed in rather than added afterwards.
How we work
2–5 days — clarify the journey, constraints, and risks; define KPIs, SLAs, and acceptance criteria.
3–7 days — choose the approach, map milestones, and lock the first deliverable.
1–2 weeks — an end-to-end slice (UI → API → DB → observability) validates direction early.
2–6+ weeks — weekly increments: features, edge cases, performance, stakeholder feedback.
1–2 weeks + ongoing — testing, security review, monitoring, rollout plan, handover docs.
From the blog
Practical AI + full-stack insights for MENA builders. No spam.
Questions
Open channel
Get a senior engineer who owns delivery end-to-end — from architecture to production hardening.