Platform
Livon as a service
Each hospital is a tenant: its own address, its own identity provider, its own databases and its own branches. The platform runs them side by side on one cluster and never lets one see another.
A tenant per hospital
Your hospital gets an address of the form name.livon.tempdomain.me with its own sign-in and its own set of users and roles. Creating it is an operator's action from your request - no hand-built deployment.
Branches
A hospital group's branches are facilities inside its tenant: shared patient data where the group wants it, separation by facility everywhere else, with roles granted per facility.
Data isolation
One database set per tenant, one process set per tenant, one issuer per tenant: every token is checked for its tenant on every request. The isolation suite sends thousands of cross-tenant requests at every release and expects zero leaks.
Backups
Per-tenant logical backups on a schedule with retention per tier, each one verified by a restore test; cluster-wide continuous archiving with full and differential backups for point-in-time recovery; an encrypted repository on a separate node.
High availability
Two application nodes with a floating address, a three-member database cluster with synchronous commit and automatic failover, a replicated document store and S3-compatible object storage for files. Failover drills are part of every release.
Releases
One code line for every tenant. A release is installed on both nodes and moved tenant by tenant, with a health check after each one and a rollback path that stays in place.
Operations
Health checks every five minutes, usage figures and log access per tenant, a second factor for platform operators, and a platform status indicator you can read on this site.
On-premises stays possible
The same packages install a single hospital on its own server. A hosted tenant and an on-premises installation run the same code.
Ready to reserve an address?
The request form asks for the hospital address and the branches you want; nothing is created until an operator approves it.