The people building Orovion

Pawan started Orovion after watching clinicians trade case photos and drug questions across five different consumer apps, none of which could say who was actually a doctor. The fix he kept coming back to was simple: verify licenses first, then let the network grow on top of that trust.

Before Orovion he spent six years in health technology, shipping tools used in hospitals across India. That experience shaped the product's core rule — attribution before content. Every case, paper and reel on Orovion leads with who wrote it and what their credentials are.

Day to day he works across product and clinical partnerships, and still reads every piece of feedback that comes through the app.

Karan runs the engineering side of Orovion: the feed, real-time chat, video consultations and the reel pipeline. His bar is that the app should feel instant on a hospital corridor's patchy 4G, because that's where clinicians actually use it.

He built the platform around two commitments. Messages and consults are private by architecture, not by policy. And the system degrades gracefully — if a service goes down, the app keeps working with what it has instead of showing a spinner.

Before Orovion he built messaging infrastructure used by millions of daily users, which is why the chat feels closer to a consumer messenger than to hospital software.