عربيinfo@thorops.comWorldwide
Taking on new projects We agree on scope and timing before kickoff
Software · Cloud · Security · AI
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.
NDA on request · No obligation
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
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.
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.
Your cloud, described in code and kept in your repository. Releases that roll back. Monitoring that wakes us, not you.
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.
We design both languages together, including right-to-left layouts, forms and navigation.
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.
02 · After launch
Launch is a milestone. Reliable operation is the work that follows.
03 · Products
Our own products keep us close to the work of building and operating software. Explore what is live and what we are developing next.
سليم
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 SaleemWorkforce 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حسابلي
Everyday expenses
In development: a simple way to record everyday purchases and understand your monthly spending.
Web · Android · MySQL
Ask about itTaking 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 it04 · Work
Examples of our delivery approach, without client identities or project-specific details. These describe areas of work, not attributed client results.
Ask for referencesExample 01
Product operations
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
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
We bring identity, content and website development together, including right-to-left layouts and a practical handover.
Both languages considered throughout delivery.
Digital innovation
Illustrative scenarios for businesses across the Arab world. These are hypothetical examples, not client projects or measured results.
A retail business
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
A mobile attendance workflow could reduce repeated entry and flag records for review. Test connectivity, approvals and payroll exports before expanding.
A service business
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
So you know what is being built, who owns it, and how it will run.
Arrange confidentiality terms before sharing sensitive information. Client names and identifying project details are not published here.
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.
Infrastructure, delivery pipelines and configuration are versioned. We document the steps your team needs to rebuild and operate the system.
You see working software every week. If a week has nothing to show, we tell you why.
Milestones, deliverables and price are agreed in writing before work starts. Changes are agreed the same way.
Documentation and runbooks from day one, so your team or another partner can take over whenever you choose.
06 · Ways to start
Start with a focused engagement, then decide what comes next.
Where most people start
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 conceptScoped per project
The core workflow, deployed safely, documented and handed over. Weekly demos along the way.
Scope a first versionMonthly · cancel any time
We keep it stable, patched and within budget: releases, monitoring, backups and the occasional 2 a.m.
Talk about ongoing operationsAli 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
Yes. Arrange an NDA with us before sharing confidential material. This site does not publish client names or identifying project details.
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.
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.
Always. It lives in your accounts and repositories from day one, with documentation so your team, or anyone else, can run it.
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
Email us a few lines about your idea, project or process.