Deploy
Your infrastructure, your choice.
Data sovereignty starts with who controls the stack.
Clinical data is only as sovereign as the software and infrastructure it runs on. Because LocumView builds on open, auditable Linux and deploys wherever you decide, jurisdiction over patient data stays with your organization, not with a vendor.
You choose the jurisdiction
Data residency is decided by where you deploy: your data center, your cloud account, or a sovereign provider.
No single-vendor dependency
Open, enterprise-supported distributions mean no proprietary OS license or foreign platform holds the keys.
Auditable end to end
Open source operating systems and code-defined builds let your security team inspect exactly what runs.
Supported operating systems
- Demonstrated
Red Hat Enterprise Linux
The reference build. The live demo runs here today; STIG hardening profiles are being applied next.
- Planned
SUSE Linux Enterprise · openSUSE
European-rooted enterprise Linux and a natural fit for sovereignty-focused deployments. Not built yet; the goal is the same code with equivalent hardening.
- Planned
Debian
Community-governed and vendor-neutral. Intended to build from the same definitions; not built yet, and validation will follow customer need.
Built for the infrastructure you already run.
Most hospitals already have capable virtualization, identity, and network teams. LocumView is designed to run on that existing footprint, or in your AWS environment, without a new platform to learn. These are design goals; today it runs in the build lab.
- Designed to run on existing hospital virtualization and storage
- Planned: deployment to AWS in your own accounts, regions, and network boundary
- Aims to reduce reliance on per-seat Windows desktop licensing
- Designed to fit alongside existing SSO and endpoint management
Infrastructure targets
On-premises virtualization
Demonstrated on KVM/libvirt; designed for the hypervisors and hardware already in your data center.
Kubernetes
Live: the access layer (Guacamole, Keycloak, and the tunnel) runs on k3s. Planned: desktops on Kubernetes with KubeVirt.
Public or sovereign cloud
Planned: the cloud your governance allows, with the same images and controls.
Thin-client ready
Because desktops are delivered through the browser, endpoints stay simple: any modern browser works, including on phones. Managed thin clients such as IGEL OS devices should work the same way but have not been tested yet.
How it ships
Same code, any target.
Define once
Desktop profiles, packages, and hardening live in one repository.
Choose the OS
The target distribution is a build parameter, with its matching hardening profile.
Build and scan
Each image is built in a pipeline and scanned with OpenSCAP before release.
Deploy to target
The signed image runs on-premises, on Kubernetes, or in your chosen cloud.