# ThorOps | Software development, cloud operations & AI Taking on new projects We agree on scope and timing before kickoff Software · Cloud · Security · AI # Build. Run. Protect. Stuck halfway through? We’ll take it from here. Whether it’s a new idea, a slow process or an unfinished product, our senior engineers help you build, launch and run it. Working with teams across the Arab world, in Arabic and English. [Email us](mailto:info@thorops.com) [See our work](#work) NDA on request · No obligation - 4products live or in development - 2 weeksfor a focused proof of concept - 1 team to callbefore launch, and long after it - 100% yourscode, cloud and keys stay in your accounts ## Why we exist Building, hosting and supporting a product often fall to different teams. When something breaks, finding the owner can take longer than finding the cause. We bring build, run and protect together. You have one team responsible for the work we agree to take on. 01 · What we do ## One team, from the first commit to the 2 a.m. call. You talk to the people who write the code, ship it and watch it. No hand-offs between agencies, no finger-pointing when something breaks. ### Build Web and mobile apps, software as a service (SaaS), and internal tools. Start with a focused proof of concept to test the riskiest assumption before committing to a full product. - Web and mobile apps - SaaS platforms - Proofs of concept - AI automation index.html ### Run Your cloud, described in code and kept in your repository. Releases that roll back. Monitoring that wakes us, not you. - commit - build - test - deploy - watch rollback ready ### Protect Secrets out of the code and into a vault. Least-privilege access you can audit. A security review before launch and a patch cadence after it. DB_PASSWORD=hunter2vault://prod/db access=least-privilege review=before-launch عA ### Arabic and English, from the start We design both languages together, including right-to-left layouts, forms and navigation. ### Digital innovation, grounded in your work Tell us what slows your business down. We review the process, identify the bottleneck, and build a practical improvement using software, automation or AI. A senior engineer reviews every change before release. - Agent drafts - Engineer reviews - Then it ships 02:00 02 · After launch ## The call nobody wants. We take it. Launch is a milestone. Reliable operation is the work that follows. - Releases that can be rolled back - Monitoring that wakes us, not you - Backups we restore from, on a schedule - Patches on a steady cadence - Runbooks written down, not kept in someone’s head 03 · Products ## Products we build and run. Our own products keep us close to the work of building and operating software. Explore what is live and what we are developing next. ### 01SaleemLive سليم Health tracking for older adults Blood pressure, blood glucose, medications and lab results in one Arabic-first app. Built for older adults and their caregivers, with a summary to share with a clinician. React · tRPC · TypeScript · PostgreSQL · Flutter [Open Saleem ](https://saleem.thorops.com) ### 02Sijil CloudIn progress Workforce costs for contractors In development: workers, attendance, approvals and payroll costs in one place, with offline workflows and later synchronisation planned. Django · DRF · MySQL · Next.js · Flutter [Ask about it ](#contact) ### 03HisabliIn progress حسابلي Everyday expenses In development: a simple way to record everyday purchases and understand your monthly spending. Web · Android · MySQL [Ask about it ](#contact) ### 04SBDIn progress Taking a small business online One workflow from the first audit to proposal, delivery and handover. We use it on our own client work. Django · DRF · Astro · React · Supabase [Ask about it ](#contact) 04 · Work ## What we help teams deliver. Examples of our delivery approach, without client identities or project-specific details. These describe areas of work, not attributed client results. [Ask for references ](#contact) - Example 01 Product operations ### Keep production running while the product evolves. Our operations work covers monitoring, releases, incident response and documented handover, with responsibilities agreed for each engagement. Clear ownership for day-to-day operations. - Example 02 Cloud delivery ### Make cloud changes repeatable and reviewable. We use versioned infrastructure, delivery pipelines and access controls to support a documented release process. A documented path from review to release. - Example 03 Bilingual digital experiences ### Build for Arabic and English from the first screen. We bring identity, content and website development together, including right-to-left layouts and a practical handover. Both languages considered throughout delivery. Digital innovation ## Turn everyday friction into a better process. Illustrative scenarios for businesses across the Arab world. These are hypothetical examples, not client projects or measured results. A retail business ### Orders scattered across messages A shared order queue could bring requests, status and follow-up into one place. Start by measuring missed orders and time spent checking messages. A contracting business ### Attendance recorded twice A mobile attendance workflow could reduce repeated entry and flag records for review. Test connectivity, approvals and payroll exports before expanding. A service business ### Slow replies to enquiries An assistant could draft answers from approved service information, with a person confirming prices and availability. Compare reply time and booked work during a limited pilot. 05 · How we work ## Clear agreements. Documented work. So you know what is being built, who owns it, and how it will run. - 01 ### NDA first Arrange confidentiality terms before sharing sensitive information. Client names and identifying project details are not published here. - 02 ### Your accounts, your keys We work inside your cloud and code accounts with the least access the job needs. You can see what we touched and revoke it any time. - 03 ### Everything in version control Infrastructure, delivery pipelines and configuration are versioned. We document the steps your team needs to rebuild and operate the system. - 04 ### Weekly demos, not reports You see working software every week. If a week has nothing to show, we tell you why. - 05 ### Scope in writing Milestones, deliverables and price are agreed in writing before work starts. Changes are agreed the same way. - 06 ### Built to hand over Documentation and runbooks from day one, so your team or another partner can take over whenever you choose. 06 · Ways to start ## Start small. Stay if it works. Start with a focused engagement, then decide what comes next. Where most people start ### Two-week proof of concept Fixed price · two weeks We build the riskiest part of your idea, on real data where possible, and give you a straight answer: build it, change direction, or stop. Stopping is a good outcome too. [Start with a proof of concept](#contact) ### Build the first version Scoped per project The core workflow, deployed safely, documented and handed over. Weekly demos along the way. [Scope a first version ](#contact) ### Run and improve Monthly · cancel any time We keep it stable, patched and within budget: releases, monitoring, backups and the occasional 2 a.m. [Talk about ongoing operations ](#contact) ## A note from the founder Ali BakerFounder, ThorOps I spent years on the other side of this: the engineer who gets paged because a contractor shipped something and left. That is the reason ThorOps exists. We are a small team on purpose. You talk to the people who write the code. We say no to work we cannot do well, and we put scope, milestones and price in writing before anything starts. If you are building something in the region and want it to still work in two years, send me a short note. I read every one. 07 · Before you call ## Questions people ask before a call. Will you sign an NDA? Yes. Arrange an NDA with us before sharing confidential material. This site does not publish client names or identifying project details. Can you take over something someone else built? Yes. If your previous team or AI tool got you part of the way, we review what exists, identify the blockers and agree on a practical next step. We keep what works and rebuild only where needed. How fast can we start? We confirm availability and a realistic start date after discovery. A focused proof of concept is scoped for two weeks; a production release needs its own plan. Do we own the code and the infrastructure? Always. It lives in your accounts and repositories from day one, with documentation so your team, or anyone else, can run it. Who do you work with, and how is support arranged? We work with clients across the Arab world. Meeting times, support hours, incident response and escalation are agreed around your team and each engagement. 08 · Contact ## Let’s talk by email. Email us a few lines about your idea, project or process. Email[info@thorops.com](mailto:info@thorops.com) Copy