Engineered by clinicians, for clinicians.

Like many clinicians, I spent years seeing problems in the system that technology could solve. About ten years ago, as a medical student, I finally tried to solve one: a ward management tool that let clinicians hand over and keep a shared, up-to-date list of patients and outstanding jobs.

I could not code, so I had two options: pay a developer, or convince someone to join me. Strapped for cash, I talked someone into it. They built the app, but it had bugs, the design got in the way, and it never quite solved the problem it was meant to. We tried to rework it, and that did not work either. The project failed.

So I learned to code. Over the next few years I built my own products, and being able to prototype quickly and cheaply changed everything. Ideas no longer had to wait for someone else to build them.

Then came AI. I was hesitant at first, but I soon found I could prototype a hundred times faster, and it became easier still to learn, test ideas and grow.

Healthcare is different, though. It slows innovation down to protect the people involved, and rightly so. “Vibe coding” does not work when patient safety comes first. A good healthcare product needs systematic building with a human in the loop, thorough evaluation and testing, and regulatory compliance. Have two out of three, and you do not have something worth shipping.

So I built Ostify. It lets clinicians build freely in a safe sandbox, evaluate what they have made, and meet the regulations that matter, so what comes out is worth piloting. Once an agent is judged safe to publish, you get a link to share with patients, staff or the public.

My hope is simple: to lower the cost of building in healthcare, and to make innovation something every clinician can take part in.

Divyan