Laravel apps from zero
From first schema to launch: clear domain boundaries, clean migrations, tests that protect what you built.
Hi, I'm Beshoy Fady
Backend Engineer / Laravel & Next.js platforms
I build and run production platforms, end to end.
Backend engineer building production platforms with Laravel and Next.js, from APIs and dashboards to public-facing products.
I am a backend engineer who runs what he builds. Not a contractor who hands over a repo and disappears.
I stay with a product through launch and ongoing operation: from the first schema to incidents, maintenance and financial workflows that need to reconcile. The projects here are live, and I remain involved in their engineering.
Backend first, product-minded, and comfortable owning the frontend when it matters.
From first schema to launch: clear domain boundaries, clean migrations, tests that protect what you built.
REST contracts, versioning, queues, events, and service boundaries enforced by tooling — not good intentions.
Server-rendered, RTL-ready multilingual interfaces wired straight into the API.
N+1 hunts, real indexes, layered caching, and a before/after number for every change.
Stripe, Paymob, idempotent webhooks and reconciliation that never loses a cent.
Docker, CI/CD, monitoring and alerting — or a monthly retainer that keeps it all alive.
A creator platform, the Arabic-first Tatbeqy portal and a bilingual agency website, each built around its own product and brand identity.
A creator publishing and monetization platform with separate admin, creator, writer and agent workspaces, backed by a shared API for independently deployed marketing and content sites.
An Arabic-first portal for apps, games, articles and reviews, consuming platform content through the API with SSR and localized SEO.
Dranovo’s official agency website, built around its approved indigo identity, bilingual service and work pages, and project enquiry forms.
For the engineers reading this: here is the whole surface, and how deep I actually go on each part.
Where most of my day goes
A before/after number for every change
I own it when it matters
What keeps it standing
DEPTHshipped it and operated it for yearsproductive, but I would ask for review
Four stages, every one of them visible to you while it happens.
A week of hard questions: what breaks, who it hurts, and which number has to move.
Built the platform and production sites: backend, dashboards, SEO, deployments and monitoring.
Visit my GitHub profile
github.com/beshoyfady →A platform is not a repo. It is boundaries you can enforce, contracts you can trust, and a deploy you are not afraid of. That is the part I care about.
How I turned a Laravel monolith into modules nobody can break by accident.
How a clear API boundary keeps a content frontend separate from the platform backend.
The pattern I have used in every payment integration since 2021.
Two paragraphs is enough. You get an honest read on scope, risk and whether I am the right person — within one working day.
Tell me the problem in two paragraphs. You get an honest read on scope, risk and whether I am the right person — within a day.