Three products on one platform, built in a fixed order.
Nimikh Core is the substrate: tenancy, identity, messaging, payments behind an adapter, offline capture, audit and export. EduOps, AgriOps and VisionEdge sit on top of it, each specified for an industry where the same operational problems repeat at every organisation. The order they are built in is fixed, and the conditions for moving from one to the next were settled before any code was written.
None of the three is available today. EduOps is in build, AgriOps is at the paid design-partner stage, and VisionEdge is validation only. There are no customers, no pilots and no case studies behind any of the three, and the status is the first thing on each product page.
Nimikh Core, underneath all three
A school, a feed mill and a distribution hub need very different software and almost identical plumbing. Core is that plumbing, specified once. It is not sold separately.
Tenancy and identity
One installation serves many institutions, and the boundary between them is enforced by the database rather than by application code. Sign-in is phone-first with a one-time code, because a phone number is the identifier most staff actually have. Roles are assigned per scope, not per person.
Messaging with a consent ledger
One router across SMS, WhatsApp, in-app and email, with templates, a consent state recorded per recipient per channel, and a spend cap per tenant. Messaging is a cost centre with a ledger attached, not an unmetered send button.
Payments behind an adapter
At least two gateway implementations plus a manual counter method, webhooks verified by signature and made idempotent, settlement files ingested and reconciled three ways with an exceptions queue for whatever does not match. The institution is the merchant of record throughout.
Offline capture
Designated flows keep working with no network and sync afterwards without loss. The queue carries one write shape per flow, deliberately, so nothing else drifts into it.
Append-only audit
Hash-chained, and writable only forwards. A record of what happened that can be altered afterwards is not a record of what happened.
Import and export
Structured bulk import with a dry run before anything is written, and a self-serve full export of every record you gave us and every record we created for you, in open formats. Export is a shipped requirement rather than a sentence in a sales conversation.
Bilingual interface
Bangla and English are the same system, set in the same type scale, with the optical corrections Bengali needs — not English strings translated into a layout that was measured for Latin script.
Break-glass support access
Support access to a tenant’s data is explicit, time-boxed, notified and recorded. There is no standing key held by anyone here.
Core is not finished either. It is built alongside the first EduOps release, which means the platform and the first product become real at the same time, or neither of them does.
The product being built, and the two behind it
They are not three equals in a row. One is being built now. The second starts only if a paid discovery stage earns it, and the third is a measurement before it is a product — so the page is weighted the way the work is.
Nimikh EduOps
Education
Builds a school’s routine, dispatches a substitute teacher when one calls in sick, records attendance offline, and reconciles fees against the payment gateway’s own settlement report.
Building a conflict-free routine is hard, and it hurts twice a year. A teacher calling in sick at 07:10 hurts every weekday. Cover gets arranged by sequential phone calls, marked on a paper chart, announced in a WhatsApp group not everyone reads, and remembered by nobody. By 08:00 a class or two is still unattended, and afterwards there is no record of who covered what — so workload disputes cannot be settled and the substitute is neither credited nor paid.
The first release is in build. Its scope depends on a documented capacity decision taken at the end of month one: with four engineers it ships routine, substitution, attendance and collections together; with two, collections move to a second release and the first ships as routine and register.
Behind it, two products specified to the same depth, neither of them started. Finishing the one in front is not what starts them: each begins only if its own gate is passed, and not otherwise.
- Design-partner stage
Nimikh AgriOps
Agriculture
Captures field data inside a shed with no signal, tracks a production batch from placement to close, and settles contract farmers against records both sides can read.
Specified to the same depth as EduOps and entering the paid design-partner stage. It starts only if that stage earns it — the gate is a measured one, not a date.
- Validation only
Nimikh VisionEdge
Security and video
Runs detection on a box at the site, sends events rather than video, and produces evidence a dispute can actually be settled with.
Validation only. Nothing is sold and no performance figure is published until it has been measured on a customer’s own cameras, at that customer’s site. If the measurement does not earn it, the product does not ship.
Why they are built in this order, and what stops each one
Education is first because three things line up there that do not line up in the other two: the problem is described in detail, the buyer is private and pays for their own software, and it is the work this team is closest to. Agriculture follows, on paid design partners rather than on free goodwill. Video is last, and it is validation only, because its central claim is a measurement nobody here has taken yet.
Each line carries gates with thresholds written down in advance, and a gate that fails twice kills or re-scopes the line it belongs to. That is the part of the plan we would rather publish than explain later — a roadmap with no stopping conditions on it is a wish list.
Which of these is your problem?
If one of the three describes a morning you recognise, tell us what actually happens on it, in your own words. If none of them does, we build custom systems as well, and we would rather say so than push you at a product that does not fit.