Labour law, tenders and governance are built into the core — not add-ons you buy, and not a localisation project paid for once per customer.
58 releases shipped between 23 August and 3 September 2026 — here is what reaches the person using the system.
A floating button on every screen opens the assistant panel in place. It answers in Arabic and English from the product’s own user guide, its changelog and its field help, and it cites its source — and when it finds nothing it says so rather than inventing an answer.
A patient portal with remote consent signing (link + one-time code), self-booking from a calendar of genuinely free slots rather than a request that may be refused, prescriptions and their lines, and billing wired to inventory and insurance.
One engine gathers the company licence, its documents and employee documents into a countdown with urgency grades, a compliance counter inside the assistant, and a short morning briefing.
An entry in the top bar reachable by anyone with a personnel file. With it, screens that were built but had no visible door are now reachable: departments, job descriptions, cross-entity assignment, sponsorship (inventory and transfer) and the national-support schedule.
A complete guide inside the product, and the assistant reads from it — so its answers follow how the system actually behaves, not general knowledge alone.
A rate limit that turns away a flood without touching the database, with the first rejected knock from each source logged in full · the customer portal isolated to its entity · and the opening-balances importer posting every line to its own company’s ledger, rejecting what does not belong to the entity before the save rather than after.
Every figure on this page was measured from the live codebase on 3 September 2026 (release 9.21.170.8) — and anything not yet built is stated as not yet built.
Every system stops you approving your own entry. Nokhatha goes further: if the preparer and the approver have a declared family relationship — spouses, parent and child, siblings, in-laws — the system refuses and requires an independent third approver, recording the reason on the file.
End-of-service, leave by statute, Hajj leave (21 days under article 76), penalties derived from a schedule rather than typed by hand, social-insurance shares, and the tender cycle on its 30 calendar-day statutory window.
When an inspector or auditor arrives, the common answer is to sit them at an employee's account. In Nokhatha: a read-only secret link, no account and no password, capped at four hours and expiring by itself, scoped to one authority and one entity.
Someone scoped to one company cannot see its sister — in data, in visibility and in approval. It is a measured line whose number is published with every release, not a promise in a slide deck.
Compliance records cannot be deleted in code; they are corrected with a new line, never by erasing the old. Journal entries are revised through a preserved revision, not overwritten.
BOQs, progress claims, site reports and a subcontractor portal · lease contracts, collections and a tenant portal · an approved tender path · permits to work for the oil sector · and a complete delivery module.
412 releases shipped with a public log inside the product, and every item goes through the same cycle: build → full check → live test → deploy → verify.
Read from the product's own permission matrix — not from a marketing list.
An auditor does not buy software; they buy a shorter path to evidence. Nokhatha is designed to produce its own.
A timed read-only session scoped to entity and purpose, with every screen you opened logged by time — your working paper is built from a record, and your position is defensible.
Segregation of duties is enforced in the system rather than described in a policy — and you can evidence its effectiveness from the log instead of relying on inquiry.
Every approval, refusal and kinship escalation is written with its reason — so testing approver independence becomes a query.
Compliance records cannot be erased and entries are revised through preserved revisions — what you audited does not change after you audited it.
And the difference is the firm's margin, or capacity for one more client.
On every client who moves to Nokhatha — recurring income with no delivery cost.
We also open a permanent trial environment for the firm to test on before recommending it to anyone — whoever recommends what they have not tried risks their own name, and we do not ask that of them.
Competitor columns describe what they offer today from public sources; the Nokhatha column describes what is shipped and running — not what is in development.
What actually matters to your business in Kuwait — and who ships it ready.
| Dimension | NokhathaBuilt for Kuwait | SAPEnterprise suites | Oracle NetSuiteEnterprise cloud | ZohoGeneral cloud |
|---|---|---|---|---|
| Built for Kuwaiti labour & social-insurance lawArticles 68 & 76 · PIFSS · official holidays | ✓ | ~ | — | — |
| Your data stays with youSovereign self-hosting, not a foreign cloud | ✓ | ~ | — | — |
| Ready for Kuwaiti regulatorsCITRA · ISO 27001/27701 · data rights | ✓ | ~ | ~ | ~ |
| Native Arabic, right-to-leftNot a translation bolted on afterwards | ✓ | ~ | ~ | ~ |
| Governance and trust in every decisionFour-eyes · duty separation · indelible audit trail | ✓ | ✓ | ✓ | ~ |
| Owned, at a cost you controlNo per-seat subscription climbing every year | ✓ | — | — | ~ |
| Attendance and biometrics, integrated at onceZKTeco directly · no middleware, no add-on | ✓ | ~ | ~ | ~ |
| Follows your business with fast customisationEvolves at your pace, with you | ✓ | ~ | ~ | ~ |
✓ Built in, ready · ~ Possible via an add-on, a partner, or extra cost · — Not available locally
| Dimension | Nokhatha | Global | Odoo | Arabic cloud | Desktop |
|---|---|---|---|---|---|
| Full Arabic RTL interface | ✓ native to the core | ✗ no official Arabic in SAP B1 / BC | ✓ | ✓ | partial |
| Payroll under Kuwaiti labour law | ✓ in the core | ✗ partner add-ons | per-customer build | Saudi-oriented | ✗ |
| WPS file with bank templates | ✓ with duty separation | via add-ons | customisation | some | ✗ |
| Tender cycle (Law 49/2016) | ✓ approved path | ✗ | ✗ | ✗ | ✗ |
| Kinship-aware four-eyes | ✓ one engine | ✗ roles only | ✗ | ✗ | ✗ |
| Timed inspection mode | ✓ shipped | ✗ reader account | ✗ | ✗ | ✗ |
| Strict entity isolation | ✓ with a published number | at higher cost | Custom tier | limited | separate copies |
| Contracting: BOQs and claims | ✓ native | generic modules | assembly + build | ✗ | ✗ |
| Your data in Kuwait — a separate instance | ✓ | external cloud | possible | external cloud | ✓ local |
| Time to first closed month | 4–6 weeks | 3–9 months | 1–3 months | days — narrow scope | days — narrow scope |
Compliance, privacy, Arabic and cost — each in its right place, from day one.
Enter your management structure into the Governance Mirror and press one button — it shows you where duties overlap and approval conflicts, and how Nokhatha closes each gap. Two minutes, nothing to install.
Open the Governance Mirror →The subscription is billed per company (entity), not per user you add — so you never hesitate to give an employee an account because the invoice grows.
For private clinics and health facilities there is a complete sector module that attaches to any plan. A perpetual licence on your own server is also available for those who require the data on their premises. Setup and migration of your existing data are charged once.
Tell us your sector, how many companies and how many employees, and you'll receive a written quote with the right plan and setup cost. We do not send marketing email.
Or reach us directly: