Our services
We build and run enterprise software. Most of it replaces something that has stopped coping — a spreadsheet that became a system of record, a platform nobody will touch, or a product that outgrew the shape it was built in.
- 41 projectsWritten up, with the stack on each
- 22 industriesBanking to healthcare to government
- 50+ engineersKochi and Ajman
- Since 2016Several clients the whole time
How we work before we talk about what we build
Off-the-shelf software is right more often than a development firm will tell you. If a product covers eighty per cent of what you need and you can live with the rest, buy it — we have said so to people who arrived ready to commission a build, and we would rather lose that project than deliver a worse answer at ten times the price.
Custom is worth it when the remaining twenty per cent is the part your business competes on, when the integration surface is the real problem, or when you are already paying for a product in workarounds. That is the conversation we would rather start with.
What we build
Enterprise platforms
Systems that run a business function end to end and are expected to last: banking operations, property management, point of sale, HR. These are long engagements where the hard parts are permissions, audit trails, reporting and the migration from whatever came before.
Finex, banking operations → InSite, property management → POS360, offline-first point of sale →
Web applications
Dashboards, portals and internal tools, usually sitting on a database that already exists and a business process that already has opinions. Built so a non-engineer can be taught to operate them, which is less common than it sounds.
Skythena, real estate analytics → GoBilly, subscription billing → SuezOne, scaffolded delivery →
Mobile applications
Cross-platform where the value is one codebase, native where the device integration is the point — GPS, offline operation, push. Most of ours are the field-facing half of a larger system rather than standalone apps.
Drenchworks, field technicians on Salesforce → Enshika, GPS and real-time chat → Mason HR →
Integration and APIs
Often the actual project. Marketplaces, carriers, payment providers and CRMs, each with its own idea of a retry, a webhook and a rate limit. The work is less about calling an API than about what your system does when the other end is slow, wrong or down — which it will be.
EliteShipping, multi-carrier rates and customs → Chargeback Gurus, three alert networks → Eoutsoft, Amazon MWS →
Data engineering
Ingestion, pipelines and warehouses — the work that has to exist before a dashboard means anything. Event streaming where the data arrives continuously, columnar storage where the questions are analytical, and a graph database on the rare occasion the data really is a graph.
RedCap, ClickHouse and Kafka on Kubernetes → Salaqeil Space, regulatory scoring →
AI and decision engines
Language models inside a product, document and language understanding, and business-rules engines that analysts configure without a deployment. Nine of the forty-one.
What we have shipped, and what we decline to build →
Cloud, DevOps and platform
AWS most often, Azure and Google Cloud where a client is already there. Containers and orchestration when the workload justifies them, CI that developers trust enough to actually use, and cost control — which on most inherited systems is the quickest win available.
UI and UX design
Interface design for the systems above rather than as a standalone service. For software people use all day, the measure is how fast a trained user gets through their work, not how it looks in a portfolio.
The less obvious one
Taking over a system someone else built
A good share of our work starts with a codebase we did not write, often without its original authors and sometimes without documentation. We will read it, tell you honestly what shape it is in, and then run it — several of the platforms in our case studies arrived this way and we have maintained them for years.
This is the opposite of the usual response, which is to recommend a rewrite. A rewrite is occasionally right and almost always proposed too early, because reading someone else's code is harder and less enjoyable than replacing it.
How engagements run
- Shape
- Dedicated team, or fixed scope where the scope really is fixed
- First response
- Within one working day, with who would do the work
- Overlap
- GCC, European and North American business hours
- After launch
- The team that built it runs it
We are also available through agency and white-label partnerships if you would rather we never appear in front of your client.
Tell us what you are building
Whether it is a system to build, one to replace, or one that needs rescuing — describe it and we will come back within one working day with who would work on it and how we would start.