Your servers. Your data. No vendor in the middle.
For public hospitals, government facilities and privacy-strict institutions, the deciding question is not features — it is where the patient data physically lives. Medveon can be deployed entirely on infrastructure you own, so the answer is simply “here”.
Three deployment shapes
Managed cloud — we host it; fastest to go live.
Your own cloud — the system runs in a cloud account you control, in the region you choose.
Fully on-premises — it runs on hardware inside your institution, capable of operating without an outside link.
The same system in all three cases. Buyers who take the second or third option own their own database and their own data outright.
What is actually enforced
Access is enforced by row-level security in the database rather than only hidden in the interface, so a user sees the ward and tenant they are entitled to. Data is encrypted at rest. Plan entitlements are enforced server-side rather than by the client, and user seats are metered on the server. Sessions clear patient data on sign-out and on idle lock.
What we do not claim
Medveon holds no compliance certification — not HIPAA, not GDPR, not ISO, not SOC 2, and we will not tell you otherwise to win a deal. What on-premises deployment gives you is control of the data’s location and custody, which is often the substance behind a residency requirement. The certification question is separate and remains yours to satisfy. This is general information, not legal advice — verify requirements with your local regulator or a healthcare lawyer.
If your requirement is a certified compliance posture rather than self-hosted control, we are probably the wrong vendor, and we would rather say so now than at procurement.
On-premises or a cloud account you own, in the region you choose.
Enforced in the database, not merely hidden in the interface.
With patient data cleared from the session on sign-out and idle lock.
We state plainly what is enforced and what is not certified.
Ask the hard questions early
Open the live demo, then ask us exactly where your data would sit. We answer straight.
Open the live demo → Chat on WhatsAppFrequently asked questions
Can we run this entirely on our own servers?
Yes. The system can be deployed on hardware inside your institution and is capable of running without an outside link, or in a cloud account you control in the region you choose.
Is Medveon HIPAA or GDPR compliant?
No, and we will not claim to be. Medveon holds no compliance certification. On-premises deployment gives you control over where patient data lives and who custodies it, which is often what a residency requirement is really about, but certification is a separate matter and remains your responsibility. Verify with your regulator or a healthcare lawyer.
How is access actually controlled?
By row-level security in the database, so entitlements are enforced server-side rather than only concealed in the interface. Data is encrypted at rest, plan entitlements are clamped server-side, seats are metered on the server, and patient data is cleared from the session on sign-out and idle lock.
Do we own our data?
Yes. On a self-hosted or own-cloud deployment you own the database and the data in it outright.
Related: HMS for the Gulf & Middle East → · Offline HMS for rural hospitals → · What is an HMS? →