Not resold, not white-labelled, not delivered and walked away from. We build these, we run these, and we are the ones who get called when one of them stops. Where a platform does not fit an engagement we build from scratch instead, and we say so up front.
Eight deployments, in five countries, in production.
Smart Parking went live in Motijheel, Dhaka, with Dhaka South City Corporation.
Guru ERP went live in Riyadh, Saudi Arabia, on the production floor of a plastics manufacturer. It covers production planning, inventory, procurement, finance and HR across a single facility.
The same system went live in Dubai, United Arab Emirates, at a trading company, configured differently: sales, procurement, HR, accounts and UAE VAT. One codebase, two industries, two tax regimes.
Our surgical decision support system went live in Boston, Massachusetts, with an orthopaedic practice. It reads DICOM studies and supports preoperative planning and intraoperative guidance. The surgeon decides. The system does not.
Guru ERP went live in Bangladesh, and the sector and scope are not published.
Guru ERP went live in Australia, and the sector and scope are not published.
Guru POS went live in Bangladesh, and the sector and scope are not published.
Guru POS went live in Australia, and the sector and scope are not published.
Dhaka South City Corporation is named with their written permission. The other seven deployments are described here but not identified, and the four confirmed at country level carry no city or sector yet.
It reads the study. The surgeon still makes the call.
Computer vision over DICOM studies, supporting preoperative planning and intraoperative guidance. It runs with an orthopaedic practice in Boston.
The constraint shaped the product. It complements the surgeon and never makes the decision, and everything it surfaces traces back to the image it came from.
Built around
One source of truth for the floor and the boardroom.
Production, inventory, procurement, finance and HR in one system. It runs on a plastics production floor in Riyadh and at a trading company in Dubai: one codebase, two industries, two tax regimes.
It configures to the way the plant already works. No plant is asked to change its process to suit the software.
Built for
Running, on generated data, at demo.devtechguru.cloud. Sign in as demo.admin / GuruDemo2026!. Generated sample data on a tenant that resets overnight. Change anything.
One platform. From the front desk to the back office.
Sales, inventory, staff and customer data in one place, on the same codebase as Guru ERP. The POS opens from the ERP dashboard rather than from a second sign-in.
It has to be usable by frontline staff on their first shift and controlled by management from the back office. Both, or it is not finished.
Built for
Running, on generated data, at demo.devtechguru.cloud. Sign in as demo.admin / GuruDemo2026!. Generated sample data on a tenant that resets overnight. Change anything.
The resident sees the same record the operator does.
Visitor movement, resident services, billing and operational communication across multi-tower estates, on one platform.
The constraint is who gets to see it. Billing and service tracking are visible to the resident, not only to the operator, which is the difference between a management tool and a service.
Built for
Every space accounted for.
Occupancy, vehicle movement, access and billing, digitised end to end. It is live in Motijheel, Dhaka, with Dhaka South City Corporation.
It had to work with the access control and payment hardware already on site. A parking system that needs the barrier replaced first is not a parking system.
Built for
Built for operations that cannot stop.
Yard, gate and equipment in one operational view: position, movement, throughput and exceptions, in real time.
A container terminal has no maintenance window. Ships arrive, gates move, equipment works, and the software has to be correct while all of that is happening.
Built for
Run your salon, staff, services and revenue in one place.
Customers, staff, services, billing, inventory, suppliers and the accounts in one platform, for salons and spas that have been running them in separate tools.
The front desk and the back office read the same record, so a bill raised at the desk is in the revenue figure and the stock count without anything being keyed in twice.
Built for
Software is judged in year three, not week one. Anything ships if the deadline is loud enough; what matters is whether it is still serving the business when the people who built it have moved on.
Running our own systems is how we find that out at our own expense rather than yours. A decision that looks clever at launch and costs three years of maintenance is a decision we have already paid for somewhere, and the client work inherits what that taught us.
Start with the problem. Tell us what is slowing the business down, what you want to build, or where the current system is failing. We will tell you the shortest path forward, including when that path is not us.
Start your build