Krama. क्रम. The Sanskrit word for order, sequence, the right thing in the right place at the right time. KramOS is the operating system that brings krama back to medicine - to the ward round, the OPD, the lab, the pharmacy, the case file at 3am. An ancient word, restored through a modern system, built by doctors who never stopped feeling its absence.
Built by a doctor, for doctors
The Operating System
for Medicine.
Built at 3am, not in a boardroom, for the people who carry the bedside. One calm layer for rounds, OPD, pharmacy, labs, imaging, and the whole hospital - so you can get back to the patient.
KramOS - Live ward
Bed 12 · SepsisAntibiotic dose · due nowCritical
Bed 07 · Post-opVitals stable · review AMStable
Bed 19 · ObservationLabs pendingWatch
The night that never ends
It is 3:17 in the morning.
Somewhere in a hospital in India, a young doctor is standing at the foot of Bed 12. Twenty-eight hours into duty. Running on chai, adrenaline, and the kind of tiredness that lives in the bones.
She is trying to remember one thing. Did Bed 12 get her third dose of antibiotics? The answer matters. The patient is septic.
But there is no system to check. A paper file - somewhere. A WhatsApp group with 140 unread messages. And her own memory, running on fumes.
This is not a failure of the doctor.
This is the failure of everything we handed the doctor.
Indian medicine runs on something extraordinary: the sheer will of its doctors. Residents working 36-hour duties. Consultants seeing eighty patients before lunch. Hospital owners holding a dozen broken systems together with goodwill and Excel sheets.
We ask them to learn, document, present, remember everything, and never make a mistake - and we hand them tools built for a different century. Paper. Memory. WhatsApp.
And the cost arrives quietly. A case logged on paper, lost before the exam. A thesis built over two years, on one hard drive that dies the week before submission. A critical lab value sent at 11pm, buried under good-morning forwards by the time rounds begin. A follow-up that should have happened - that simply never does.
The system asks everything of them.
And gives almost nothing back.
Where this story begins
I did not read about these problems in a report. I lived them - in my own hospital, on my own floors. I watched my team fight the same battle every day. Not against disease, but against the absence of a system.
So I started asking around. Friends. Classmates. Relatives - many of them doctors, many running hospitals of their own. Everywhere, the same answer. Same chaos. Same lost data. Same WhatsApp. Same exhaustion. Same software everyone pays for and nobody loves.
That was the moment it became clear. This was not my problem. This was medicine’s problem. And no one was solving it for the right person.
Who we built this for
Most hospital software is built for the people who buy it - administrators, billing departments, boardrooms that want everything tabulated. The doctor comes last. The doctor adapts. The doctor suffers so the spreadsheet looks good.
We refuse to build that.
I am a doctor. I run a hospital. My co-founder is an engineer who listened to every one of these stories until he understood them as deeply as I feel them. We made one promise: build for the doctor first. Always. Not for the CEO. Not for the auditor. Not to make medicine measurable - but to make a doctor’s day survivable, and then beautiful.
We have been there. We have done it. We have faced it at 3am, at audit time, the week before exams. That is exactly why we are the ones who should solve it.
The vision
One Medical OS
Not another app. Not another EMR. A calm layer beneath the entire clinical day - where you enter information once, and it flows everywhere it’s needed, automatically.
Enter once. Everything else flows.
KramOS - Enter once, it flows
Ward round completeNotes entered once at the bedsideSource
Flows to OPDFollow-up auto-scheduledAuto
Flows to PharmacyOrders routed for dispensingAuto
The ecosystem
Products that share one mind.
Each one solves a real part of the clinical day. Together, they’re a single operating system - one record, one truth, no re-typing.
The four-layer ecosystem
Four layers. One data model.
01
02
03
04
One data model. A lifetime of medicine.
Why it’s different
Promises we built into the architecture.
We answer to the doctor, not the boardroom.
Designed at the bedside, not in a boardroom.
Offline-first
Indian hospital internet fails. The work doesn’t.
Privacy-first
DPDP Act compliant, consent at the core.
Indian data residency
Your data stays in Mumbai.
Stronger than paper
Immutable timestamps - medico-legally sound.
Fixed, fair pricing
Never dynamic. Never a surprise.
改善
Kaizen · continuous improvement
Medicine has always worked this way. One patient, one round, one decision at a time. The software that serves it should too.
Kaizen
The philosophy of getting a little better every day.
Rounds
The oldest ritual in medicine - where a team gathers around a patient and thinks together.
KramOS is where those two ideas live.
The promise
To the resident at 3am: we see you. We are giving you back your time, your memory, and your years of work.
To the consultant drowning in patients: we will make documentation invisible, so you can return to the bedside.
To the hospital owner holding it all together: one system that finally fits the people who use it.
We are here to give doctors their time, their sanity, and their patients back.
Medicine deserves software built by people who have stood at the bedside. We have. And we built it.