# Whisky 11 — full text Every page of whisky11.com as plain text, generated from the site's HTML. The index is https://whisky11.com/llms.txt. --- Source: https://whisky11.com/ Software & AI engineering · Remote, worldwide # Systems that keep working after I leave I build software and AI systems for companies that need them to run every day — then make sure the people who own them can actually operate them. Remote-first, working with clients across Europe, the US and MENA. Start a project See the work ## What I build 01 · Commerce ### Storefronts that sell Multi-tenant e-commerce with real accounting behind it — orders, inventory, double-entry books, and the reports an owner actually opens on a Sunday morning. 02 · Messaging ### WhatsApp as a channel If you sell into MENA, WhatsApp is the storefront. Ordering, notifications and recovery flows built for it — with the consent, rate limits and stop conditions that keep the number alive. 03 · AI systems ### AI that reads your data Not a wrapper around a public model. Systems grounded in your catalogue, your history and your rules — with a failure mode I can describe in one sentence. Those are the three I am known for. In practice a business needs a specific shape of system, and these are the shapes I have already built and can build again: ### Online stores Bilingual storefronts on a multi-tenant platform, with the payment gateways a market actually uses, delivery zones, returns, and double-entry books behind the orders rather than beside them. ### WhatsApp ordering A cart built inside a chat thread that reaches checkout as a short-lived signed token. Free text, voice notes and product photos all understood — not a numbered menu — with a clean handoff to a human the moment someone asks for one. ### Team & client operations Task boards, client records, meetings and weekly reporting, synced live across everyone's screen and installable on a phone. For teams whose delivery is tracked per client, per week. ### Menus and ordering pages A QR menu the owner edits himself — categories, photos, prices — bilingual, and built for the phone it is actually read on rather than the desktop it was designed on. ### Websites & landing pages Company sites and campaign pages that load fast, read correctly in both directions, and are legible to search engines and answer engines alike. ### Mobile apps & marketplaces iOS and Android, including two-sided marketplaces: listings, live auctions, identity verification, escrow that holds funds until both sides are satisfied, and commission taken at the right moment rather than hopefully. ### ERP & internal systems Procurement, landed cost and currency, warehouses, assembly, labelling, picking, stock counts, accounting, payroll and statutory e-invoicing — for a business whose real system today is a spreadsheet and one person's memory. ### Training & membership portals Gated video and document libraries with paid tiers, students grouped into cohorts, and content that releases on a schedule as a course progresses. ### Digital business cards One link per person — contact, channels, location — bilingual, issued and managed centrally for a whole team. ### Bilingual Arabic/English throughout Not a translation layer bolted on at the end. RTL that holds where it usually breaks: invoices, search, SMS, and mixed Latin-in-Arabic runs that reorder on screen when the bidi isolation is wrong. ## What I've built Systems in production, carrying real money and real customers. Clients stay unnamed until they say otherwise; the details are exact. Moving a live store between platforms Catalogue, customers and order history migrated with the storefront staying up. The import reported 186 failures, and every one traced back to about 14 products whose descriptions contained line breaks — each of those records split into fragments that then failed validation with an error naming the wrong problem. The kind of fault only real merchant data produces, and the reason a migration isn't finished when the script stops. After that, months of work on the storefront being right in Arabic, on a phone. Multi-tenant commerce platform Every merchant's storefront on one codebase, with tenant isolation enforced by row-level security in the database rather than by application code — a query that forgets its filter returns nothing, instead of returning someone else's orders. Orders, inventory, double-entry books and a per-store P&L sit on top of that. Escrow between parties who don't trust each other Funds held until both sides are satisfied, with commission taken at the right moment. Any step that writes to the database and makes an irreversible external call declares its rollback before doing the irreversible part — so a payment that lands while the next step fails gets undone, rather than leaving the ledger saying one thing and the bank another. Ordering inside WhatsApp A cart built in a WhatsApp thread reaches checkout as a short-lived signed token carrying the items and the customer, not a reference to a cart ID — so the storefront never needs to know which messenger the customer arrived from, and the same path serves Telegram and Instagram. Consent, rate limits and stop conditions throughout. Arabic-first storefronts RTL where it usually breaks: invoices, search, SMS, and mixed Latin-in-Arabic runs that reorder on screen when the bidi isolation is wrong. Built Arabic-first and checked on a phone, because that is where nearly all of it gets read. The part that keeps running after handover Self-hosted CI, automated backups whose restores have actually been run, and alerting wired up before launch rather than after the first outage. Every failure becomes a written rule, so the same class of bug doesn't come back under a new ticket number. ## Open source Work you can read, not just claims you have to take on trust. All of it built solo, all of it public. Ghost GCS · ArduPilot ### A ground control station, built solo MAVLink telemetry, live map, mission planning and a headless AI copilot for drones and rovers. If you want to know whether I can build a real-time system against a hardware protocol, the code is right there. Whisky Claude · macOS ### A shipping native app Swift 6 menu-bar companion for Claude Code, with a signed release channel and auto-updates. Small, but it ships — which is a different skill from building. Zero · Voice agent ### Local voice assistant Wake word, speech, tool access and persistent memory, running on your own machine across Windows and macOS. No cloud round-trip for the parts that don't need one. Whisky Wallpaper · macOS ### Animated wallpaper engine 4K video behind your desktop icons, AppKit and AVFoundation talking to the Mac directly. No subscription, no account, no telemetry. ## How I work I don't hand over a repo and leave. The systems I've watched fail didn't fail technically. They were delivered, the one person who understood them moved on, the vendor stopped answering, and eighteen months later the business was afraid to touch the thing it paid for. The software was never the problem. The handover was. Verify, don't assume Principle 01 Nothing gets called done because a dashboard is green. Merged isn't deployed, deployed isn't live — done means someone opened the real page, on a real device. Fix the class, not the case Principle 02 A reported bug is a sample. I find the cause, then every other place that cause exists, and fix them in one pass — so you don't get the same bug back under four ticket numbers. - Backups that have been restored, not just scheduled. - Alerting and log retention wired before launch, not after the first outage. - Documentation updated in the same change as the code, or it isn't shipped. - You keep the keys, the data, and the ability to leave. ## Start a project ### Tell me what breaks today, and who has to live with it. That's usually a more useful first conversation than a feature list. If it's a fit I'll say so quickly; if it isn't, I'll tell you that too. WhatsApp hello@whisky11.com WhatsApp +20 120 776 1882 · Based in Egypt · full overlap with the European day, mornings with US East ## Common questions ### Where is Whisky 11 based, and do you work remotely? Whisky 11 is based in Egypt and works fully remotely — there is no physical office or walk-in location. Clients are across Europe, the United States and MENA, and working hours overlap the full European business day and the US East Coast morning. ### What does Whisky 11 actually build? Multi-tenant e-commerce platforms with real accounting behind them, WhatsApp as a sales channel for MENA markets, and AI systems grounded in a client's own data rather than a wrapper around a public model. In practice that also covers team and client operations tools, QR menus, websites and landing pages, iOS and Android apps including two-sided marketplaces with escrow, ERP and internal systems, training and membership portals, and digital business cards — all bilingual Arabic/English where the right-to-left layout holds up in invoices, search and SMS. ### What does “we don't hand over a repo and leave” mean in practice? The system is built and then run alongside the client until their own people can operate it without us. Backups are restored before launch rather than merely scheduled, alerting and log retention are wired before go-live, and the client keeps the keys, the data and the ability to leave at any point. ### Can I see the code before hiring? Yes. Four projects are public on GitHub, including Ghost GCS — a ground control station for ArduPilot drones with MAVLink telemetry, mission planning and an AI copilot — and Whisky Claude, a shipping native macOS app with a signed release channel. ### How do I start a project? Message +20 120 776 1882 on WhatsApp or email hello@whisky11.com. The most useful opening is what breaks today and who has to live with it, rather than a feature list. If it isn't a fit you'll be told quickly. --- Source: https://whisky11.com/privacy ← Whisky 11 # Privacy This site is a single static page. It sets no cookies and runs one script of its own — the animated header, drawn on your device's graphics chip — and nothing else. Its Content-Security-Policy is script-src 'self', so no inline or third-party script can run, and connect-src 'self', so the page cannot send anything to another server; you can verify both in the response headers. It carries no analytics, no tag manager and no third-party tracker. ### What reaches us Only what you send. If you email hello@whisky11.com or message the WhatsApp number on the home page, we hold that conversation and whatever you chose to put in it, for as long as the work or the enquiry is live. ### Fonts Typefaces load from Google Fonts, so Google receives the request for the font file — the page's IP-level footprint, not your identity. Nothing else is fetched from a third party. ### Server logs The site is served from Cloudflare Workers. Cloudflare keeps the standard request logs that any web server keeps, under its own terms, and Whisky 11 does not add to them. ### Client work Data inside systems we build for a client belongs to that client, is governed by the contract for that engagement, and is never repurposed here. ### Removal Email hello@whisky11.com and ask. Correspondence we hold about you gets deleted; anything a contract or an invoice legally requires us to keep is the only exception, and we will say so rather than quietly retain it. --- Source: https://whisky11.com/terms ← Whisky 11 # Terms Whisky 11 is an independent software and AI engineering practice, founded and run by Ahmad Sharaf Montaser, based in Egypt and working remotely. ### This site Everything here is published in good faith and describes work that has actually shipped. It is information, not an offer, and nothing on it forms a contract by itself. The open-source projects linked from it carry their own licences in their own repositories. ### Engagements Work is agreed in writing before it starts — scope, price, and what "done" means. That written agreement governs the engagement and overrides anything implied by this page. The client keeps the keys, the data, and the ability to leave. ### Payment and cancellation Terms for a given engagement live in its own agreement, because a fixed scope and a retained month are not the same arrangement. Nothing is billed here on this site: no checkout, no subscription, no stored payment method. ### Contact Questions about these terms: hello@whisky11.com. --- Source: https://whisky11.com/legal ← Whisky 11 # Legal The facts about who is behind this site, in one place. ### Who operates this site Whisky 11 is an independent software and AI engineering practice, founded and operated by Ahmad Sharaf Montaser. It is based in Egypt and works fully remotely — there is no physical office or walk-in location. ### How to reach us Email hello@whisky11.com, or message +20 120 776 1882 on WhatsApp. ### Policies Privacy — what this site collects, what it does not, and how to have anything about you removed. Terms — the terms this site is published under, and how engagements actually work. ### Security Report a vulnerability to the contact in security.txt (RFC 9116). Reports are read and answered. ### The founder's writing Ahmad writes about building and shipping AI systems at mypovonai.com.