Running in real production · Live since May 2026
RECORDED.
An incident that is never logged is never measured — and the report built on it lies with confidence.
Idrak manages maintenance and operations incidents. It makes the record happen where the work happens — not at the end of the day, and not at the end of the month.
Designed and built in Saudi Arabia · Full Arabic and English
It is not chaos — it is something worse
Maintenance systems rarely collapse outright. What actually happens is that they get filled in late and approximately, producing reports that look correct and are not — and those reports drive purchasing, staffing and performance decisions.
The report arrives by phone
A call or a message, with no number, no timestamp and no named owner. What is not recorded did not happen.
The paper is lost or delayed
Written on a note or in a chat group, then transferred to the log days later — if at all.
The report is filled from memory
At month end the table gets filled approximately. The numbers exist; the accuracy does not.
And spare parts vanish
Issued without a record, so nobody knows what was actually consumed or when to reorder.
A full cycle, from intake to closure
Report raised
From any device, with or without an account, including photos, description and location — and it gets a reference number immediately.
Routed and assigned
Categorised, sent to the right department, then assigned to a specific technician by operational priority.
Executed and documented
The technician logs the work, issues materials and checks out equipment — all from inside the incident screen itself.
Closed and measured
Closing the incident updates reports automatically — with numbers recorded the moment the work happened.
What Idrak does
Incident management
A full cycle with reference numbers, priorities, statuses and response targets, plus a work log per incident.
Inventory and spare parts
Item catalogue, per-department stock and reorder thresholds — and issuing happens from inside the incident.
Equipment custody
Check-out and return with documented condition, and a panel showing each technician what they hold now.
Work permits
Issue, track and link to incidents, with attachments and scoped permissions.
Exportable reports
PDF and Excel in Arabic and English — reading from live data, not from memory.
Instant notifications
Delivered to mobile in the recipient’s own language, so nobody waits to discover they have a task.
Works offline
A progressive web app that installs on phone and desktop and works in low-coverage sites.
Precise roles and permissions
Super admin · department manager · technician · reporter — with grant and revoke down to a single person.
- Operations and maintenance contractors
- Utilities and industrial facilities
- In-house maintenance departments
- Large complexes and campuses
Built to enterprise standards, not demo standards
The difference between a system that gets shown and a system that gets adopted is what happens when it is audited.
Complete tenant isolation
Each organisation’s data is isolated inside the database itself, not in the UI, and the isolation is tested automatically before every release.
Two-factor auth on administrative accounts
Mandatory, not optional — and users cannot disable it for themselves.
Immutable audit log
Every sensitive event is written to a log that cannot be edited or deleted — what happened stays as it happened.
Aligned with ECC controls
A compliance matrix built on the Essential Cybersecurity Controls, with an automated guard that blocks claiming an inactive control.
Request a demo
I will walk through the system on your data or on a trial environment — a live demo, not slides.
na.frgahl@gmail.com · Available on a subscription model for organisations and companies.