Safety the office can see
Pit-camera events and shift reports put incidents and near-misses on the record the day they happen — not in a notebook that goes home in someone's pocket.
Granite quarry ontology
The operating systemfor a granite quarry.
MinerOS runs the pit end to end — marking sheets to dispatch, day book to ledger, machines to the people on shift. Built around the way a quarry actually works, not the way software wishes it did.
27Modules, one ledger
EN · TE · HIEnglish, Telugu, Hindi
06:00 / 18:00Day and night shift aware
The line
From bench to balance sheet, one unbroken line.
Stone moves through a quarry in a line — marked, cut, dispatched, paid for, learned from. MinerOS keeps the records on that same line, so nothing falls between two registers.
- 01
Mark
A block is marked at the bench. The marking sheet records pit, dimensions and grade — entered at the face, not back at the office.
- 02
Cut
Sheet cuttings follow every slice. Machinery logs meter the hours, and diesel is weighed against the machine that burned it.
- 03
Dispatch
Loads leave on a dispatch record tied to the customer and to the block they came from. The workflow board moves with the stone.
- 04
Settle
Day book, payments, verification. Every rupee lands in a ledger you can put in front of a customer without apology.
- 05
Learn
The knowledge graph ties it all together. Wear scores warn before a machine fails; anomalies surface before they cost money.
Why it matters
What a quarry stops losing.
Every pit leaks the same way — between two registers, between two shifts, between the machine and the person who logs it. MinerOS closes those gaps. These are the leaks it is built to stop.
Downtime caught before the breakdown
A wear score climbs before a machine stops. Replace the part on a planned day instead of losing a face to a seized bearing on the wrong one.
Diesel and spares that add up
Fuel is weighed against the machine that burned it; every spare is logged against the job it went into. Month-end is the sum of the records, not a guess.
A ledger you can show a customer
Dispatch, day book, payment, verification — one unbroken chain from the block to the rupee. No invoice you'd hesitate to put in front of the person paying it.
Shifts that don't drop the thread
Day hands to night with a written handover and the footage behind it. Nothing important survives only in the memory of whoever just clocked out.
Stone that can't slip out
Every block is on the record from the bench it's cut to the lorry it leaves on — measured, marked, graded, dispatched. None walk off the lease uncounted.
The slow decline, caught early
Agentic comprehension watches the data for drift — production sliding on a new trench, a machine creeping off its baseline — and flags it before a soft month hardens into a lost quarter.
Knowledge that isn't one person's
The whole pit sits in one connected record — blocks, machines, shifts, spares, people. It doesn't walk out the gate when the person who knew it all retires.
Modules
Everything the quarry runs on — streaming past.
Twenty-seven working registers, grouped the way the work is grouped. No add-ons, no marketplace — the whole quarry ships in the box.
DashboardMarking SheetsPitsMachineryMachinery LogsSheet CuttingsDieselDay BookCustomersPaymentsPayment VerifyProfitabilityCost BreakdownEmployeesAttendance
SparesBoardTasksDispatchEquipment StatusShift HandoverAnalyticsReportsKnowledge GraphAI AssistantRolesData Migration
Built for the pit's machines
Every machine on the lease, on the record.
Intelligence
The quarry, thinking.
Records are the floor, not the ceiling. MinerOS watches its own ledgers and tells you what they mean — quietly, and only when it matters.
Ask the quarry a question
The AI assistant reads the live operational graph and answers from your records — production, payments, machine health — not from generalities.
A knowledge graph underneath
Machines, blocks, shifts, spares, payments — one graph, seventeen kinds of operational insight, rebuilt continuously from the day's data.
Wear scores, not breakdowns
Every machine carries a wear score from 0 to 100 — hours run, spare consumption, failure history. Replace the part before the part decides for you.
Shifts that hand over cleanly
Pit cameras post events over signed MQTT. Day hands to night with a written report and the footage to back it — 06:00 and 18:00, IST, every day.
Agentic comprehension
Agentic comprehension on data to track future anomalies like degraded production during new trenches.
How it fits the pit
It meets the quarry where the quarry is.
No pit starts from zero. Tippers already run, registers sit in a drawer, the network drops at the face. MinerOS is built to fit that reality — not to demand a new one before it earns its keep.
- Bring the old books in
- Existing customers, machines and balances import through a guided migration, checked row by row. Start with your history intact, not a blank ledger.
- Works at the face, syncs at the office
- Installable on the phones and tablets the crew already carry. Records are entered where the work happens; the office sees them as soon as the signal returns.
- Cameras over a signed line
- Pit cameras post events over TLS MQTT with HMAC-signed payloads. In production it is fail-closed — footage that can't prove who sent it doesn't make the record.
- Two shells, one source of truth
- A Windows desktop app and this web app are peers on the same backend. The dispatch desk and the boss's phone read the same row, in realtime.
- In the language of the crew
- English, Telugu and Hindi, switched per person — so the operator at the bench and the accountant at the desk each work in their own.
01
02
03
04
05
Platform
One system. Built like a datasheet reads.
System architectureFig. 01
- Shells
- A Windows desktop app and this web app — peers, not ports.Same backend, same sign-in, same permissions. Use either. Use both.
- Backend
- One source of truth with row-level security; realtime to every open screen.An edit on the dispatch desk shows up in the pit office before the phone call does.
- Access
- Role-based permissions, with MFA enforced for finance and admin.Operators see operations. Accountants see money. The boss sees everything.
- Languages
- English, తెలుగు, हिंदी.Switchable per person, not per company.
- Install
- Installable as a PWA on phones, tablets and desktops.The pit crew doesn't carry laptops.
- Edge
- Pit cameras ingest over TLS MQTT with HMAC-signed payloads.Fail-closed in production. Footage that can't prove itself doesn't count.
01
02
03
04
05
06
How it's built to be trusted
Boring where it counts.
An operations platform earns trust by being predictable, not clever. These are the rules MinerOS holds itself to — stated plainly, because the point of a standard is that you can check it.
Standards registerRev. A
- Permissions, not honour systems
- Role-based access decides who sees what. Operators see operations, accountants see money, the boss sees everything — enforced by the system, not by trust.
- A second factor on the money
- Finance and admin sign in with multi-factor authentication. The accounts and the access controls are gated behind more than a password.
- Writes that can't half-happen
- Compound changes — replacing a spare, signing off a handover — run as one atomic operation. A record is either fully written or not written at all.
- Schema changes that leave a trail
- Every database change ships as a tracked, versioned migration with a record of when it ran. The structure of your data has a history you can read.
- Same binary, dev to pit
- The build that runs in production is the build we test. Features that aren't configured stay switched off — no surprise behaviour that only appears on site.
STD-01
STD-02
STD-03
STD-04
STD-05
Straight answers
The questions a quarry actually asks.
The things people ask on the first call, answered here so you don't have to make it. If yours isn't here, it's the next message we'd like to get.
Q-01Do we need to throw out how we work today?
No. MinerOS is shaped around how a quarry already runs — marking sheet at the bench, day book at the office, machines on logs. You bring your existing records in and keep going; the system fits the work, not the other way round.
Q-02What happens when the signal drops at the face?
Records are entered on the device where the work happens. When the connection comes back, they sync to the one shared backend. The pit doesn't stop because the bars did.
Q-03Who can see the money?
Only the roles you allow, and finance and admin must clear multi-factor sign-in first. Operations and accounts are separated by permission, not by goodwill.
Q-04Is this only for English-speaking crews?
No. The whole interface runs in English, Telugu and Hindi, and each person picks their own. The operator and the accountant don't have to share a language to share a system.
Q-05Desktop or web — which do we buy?
Both, at no fork in the data. The Windows app and the web app are peers on the same backend with the same sign-in and the same permissions. Use whichever suits the seat.
Q-06How do we start?
Tell us how your pit runs today. We'll walk it through with you, import what you already have, and stand it up one module at a time — not a switch you flip overnight.
Where to from here
See it run against your own pit.
Not a demo of someone else's quarry — a walkthrough on your machines, your customers, your numbers. We'll show you exactly where your records would land, then leave you to decide.