DerOps builds Model Context Protocol servers, multi-cloud platforms, and compliance-grade infrastructure. Run from Cairo by a senior engineer who ships every line personally.
Production Model Context Protocol servers that let Claude, ChatGPT, and other AI assistants read and write inside the SaaS your team operates in daily.
Linux administration, multi-cloud deployments, email infrastructure, observability, and the boring-critical layer that keeps production running while you sleep.
Multi-tenant Supabase architectures with row-level security, GDPR alignment, audit logging, and role-based access for regulated industries.
Production MCP server connecting Claude AI to Jobber for field-services operations. 9 tools, OAuth 2.1 with Dynamic Client Registration, transport-agnostic core serving Claude Web, Desktop, iOS, and Code from one codebase.
github.com/Drdr1/jobber-mcp →Custom MCP server for a US plumbing operations company. 14 tools across jobs, clients, dispatch, and email retrieval. OAuth 2.1 for Claude iOS access, deployed on dedicated infrastructure. Five-milestone contract from spec to production.
Private case study · NDAUK property management compliance platform on Supabase. 6 schemas, 30+ tables, 70+ row-level security policies across 7 roles. GDPR DSAR procedures, full audit trail, and reporting views aligned to the Renters' Rights Act 2025.
Private case study · NDAProduction WordPress fleet across multiple servers for a UK consultancy. 21 sites, security hardening, automated backups, monitoring with custom thresholds, Cloudflare DNS automation, and weekly written reporting on a monthly retainer.
Private case study · NDAEvery system ships with the runbook your in-house engineer needs to maintain it. Architecture decisions, operational procedures, and recovery steps written down. No tribal knowledge sitting only in my head.
Scope is written, locked, and broken into milestones with escrow. You pay for delivered outcomes, not hours billed in good faith.
Everything ships with documentation your team can read, proper handover, monitoring where appropriate, and a written runbook. The bar is "your engineer could maintain this," not "it worked on my machine."
Every line is written, reviewed, and shipped by Ahmed personally. No handoffs to junior teams. No agency overhead. What you see in the proposal is what builds your project.
The fastest way to get a real answer is to send a written brief. Include what you're trying to do, what's currently in the way, and any constraints I should know about. I'll write back within 24 hours with whether it's a fit, a rough scope, and likely range.
Write to me →