Products, tools and systems
I can explain without a slide deck.
I group the work by the product or problem I owned—not by how many repositories it happens to use.
SCRIPE
I’m building SCRIPE as one operating system for the business and coaching work around a sports academy, with football as the first deep vertical.
AstraFlow
AstraFlow is an MIT-licensed .NET package family for request dispatch, mapping and the diagnostics/tooling around those flows.
BTD
BTD is my reusable enterprise starting point: .NET backend, Next.js frontend, RBAC, multi-tenancy, CLI tooling and a visual Studio.
SYNFLOX
A central licensing system for software vendors that need products, plans, subscriptions and both online and offline validation in one control point.
Deals
A Flutter coupons and cashback product with the admin dashboard and backend needed to operate stores, categories, offers and user-facing content.
Flutter OTP Kit
A focused Flutter package for the OTP interaction layer: configurable fields, focus behavior, validation hooks and reusable verification UI.
Portfolio Platform
A multi-tenant portfolio publishing platform in development, with a Next.js Studio and an authoritative ASP.NET Core backend.
Transport Terminal
A role-aware enterprise operations frontend for vehicles, drivers, gates, cards, visitors and loading workflows.
Useful work that does not need a flagship badge.
These projects widen the picture: desktop operations, science education, marketing web work and reusable admin patterns.
Desktop invoicing and operations system with invoices, catalogue items, expenses, workers and audit history.
Arabic-first oil-remediation learning and simulation app with theoretical modules, practical calculations and saved experiment results.
Next.js / Web experienceEgypt MarketingAnimated marketing/agency website spanning brand, design, production and development storytelling.
Reusable bilingual admin patterns, service abstractions, RTL/LTR behavior and dense back-office interface work.
Some products are ecosystems, not single repos.
That split matters for engineering, but it should not make the portfolio harder to understand. I show one product story, then the repositories that make it up.