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.
Scope set by a capacity decision at the end of month one.
SpecificationStarts only if the paid design-partner stage earns it.
SpecificationNothing is sold before it has been measured on a customer’s cameras.
SpecificationBuilt alongside the first EduOps release, not before it.
TopologyA 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.
One deployable, many modules. A product reaches Core only through an interface Core publishes, and no module reads another module’s tables.
Eight primitives, specified once and shared by all three products.
Selected rather than exhaustive: these are the ones a buyer can check us on later. Each is written down as a specified behaviour, and none of them is a shipped feature.
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.
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.
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.
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.
Hash-chained, and writable only forwards. A record of what happened that can be altered afterwards is not a record of what happened.
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.
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.
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.
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.
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.
The first release’s scope depends on a documented capacity decision taken at the end of month one.
Now 07:3426 min left
The window the product is built around
Absence reported
A physics teacher’s absence arrives by WhatsApp and affects four periods. It can also arrive in the app, by phone call, or as planned leave.
Four routes inRanked substitutes, each with its reason
Subject match, free period, fairness rotation, “14 of 22 this week”. The ranking is rules-based, not learned, and an exclusion shows why a candidate lost.
Rules-basedDispatch messages priced first
Messages ৳ 7.20 across 13 parts, from a wallet holding ৳ 2,140.00 — shown before anything is sent, not after the bill.
Wallet shownResolved before the first bell
The wireframe has six of seven periods covered at 07:34, and the seventh states the constraint that blocked it. Delivery is recorded per recipient, so there is a record of who covered what.
RecordedAgriculture
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.
In the shed, with no signal
Captured one-handed
Feed, mortality with a cause code, water and environment readings, weight sampling, medication and photographs. About forty seconds is the target.
No network callValidated on the device
The form does not need a signal to know whether what was entered is valid.
OfflineHeld in a local queue
Capture keeps working with no network at all for at least 72 hours. The queue carries one write shape, so nothing else can drift into it.
One write shapeWhen the network returns
Synced without loss
Batch metrics sit on the device rather than arriving after the cycle ends, with threshold alerts while there is still something to do about them.
Batch ledgerA settlement the farmer can read
A statement the contract farmer can read and dispute line by line, so the argument is about a number both sides can see.
Line by lineSecurity 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.
At the site
Cameras the site already owns
ONVIF or RTSP. Nimikh does not replace a camera and does not sell one.
Existing camerasDetection on a box at the site
A detection is filtered by class and validated over time before anyone is told. In shadow-trial mode it runs without raising an alert.
Edge onlyWhat leaves the site
Events, not video
Only events, metadata and short clips ever leave the site. Continuous video does not.
Events onlyEvidence with a chain of custody
Every export carries a hash and a chain-of-custody record. No role holds a permission to delete evidence.
Hash + custodyEach line carries gates with thresholds written down in advance. A roadmap with no stopping conditions on it is a wish list, so these are published rather than explained later.
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.
It follows on paid design partners rather than on free goodwill, and it starts only if the discovery stage earns it.
Its central claim is a measurement nobody here has taken yet, so it is a measurement before it is a product.
A gate that fails twice kills or re-scopes the line it belongs to. The named kill triggers in the requirements document are these three.
If one of the three describes a morning you recognise, read its specification. If none of them does, we build custom systems as well.
A teacher calls in sick at 07:10 and cover is arranged by phone calls and a paper chart.
Nimikh EduOpsField records are written on paper, re-keyed days later, and settlements are argued rather than read.
Nimikh AgriOpsLosses surface at stock-take, finding the footage takes a day, and a camera can stop recording unnoticed.
Nimikh VisionEdgeWe build custom software as well, and would rather say so than push you at a product that does not fit.
Custom softwareIf 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.